Events in JavaScript are still very shady to me. I see the way they work, and I only slightly understand the way browsers execute them. A great deal of this chapter on events covered cross-browser problems (especially involving Internet Explorer) and was confusing in explaining the core details of event listeners. I can't firmly say I understand them. In order to troubleshoot those I have been able to implement, I have taken the code archive and stepped through each action to see where the next part of the script would be executed. It's been quite a rollercoaster ride through spelling mistakes and logical errors on my part, but it's helped me see how some parts work. It takes a lot of work to get the functionality as intended when working with an already-existing page, but the efforts seem to play out in the end. I can see the importance of being able to use events now, and I hope I can implement the idea in further projects throughout my expanding web development hobby or career.
Events are important to the extent of user interaction on a web page. It is important to let users be able to interact with a page for a better user experience while visiting. At the same time, however, just as with design and form, the function or behavior of the page must be separated from the content of the page. In this way we keep accessibility alive and our code can be reused in other cases for the same processes in the future that we need on particular pages we create now.
Monday, November 23, 2009
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment