Probably by now you're thinking, "Hasn't everything been discussed and explained so far?"
But, the present situation is not as bright as described above. New technologies do contain new traps, and DOM support on both platforms is different and contains quite a few bugs and inconsistencies.
This column will concentrate on the new client-side technologies available and will discuss ways to take advantage of them. We'll talk about the big picture of our solutions and applications and dive into the details only when necessary, to point out bugs, for example.
So where do we begin? How about with one of the most annoying tasks in today's Web client programming: the validation of forms.
Pretty boring, you say. Well, it could be, but this time it's not. I picked this as our starting point, since it's a well-known topic -- doing it the old-fashioned way, at least.
I won't be explaining how to access an element and its values, or how to connect an event to an event-handling function for the thousandth time. Instead, I'll create a solution which completely hides all scripting tasks behind a set of new attributes, called the Forms Extension Framework (ForX).
These attributes describe the elements rather than defining how to do something. Most people find this easier to learn and remember, as this is a more natural way to work with elements, especially for non-programmers.
So, before we dive into ForX head first, let's talk about forms a bit in the accompanying article, Working With Forms: An Introduction.
Copyright © 2009 O'Reilly Media, Inc.