Tech Stuff - W3C DOM

We are not big fans of Javascript or any other client side scripting for that matter. We originally used them like everyone else for page local effects. We now use CSS almost exclusively for this purpose. CSS does have serious limitations if you want super-snazzy pages but we generally don't - as may be obvious from our site. Nevertheless, we use Javascript especially for client side applications like our calculators (wireless and audio) and Regular Expression tester.

In the context of Javascript - and all future client side scripting that we can see - the W3C DOM is vital. It promises to eliminate all that cross-browser nonsense and turn it into a historical artifact, rather than the major pre-occupation which it still is today (2009) in spite of (currently) 6 years of W3C DOM availablity. The W3C DOM is big and complex which - coupled with the lingering browser incompatibilities and proprietary DOMs - probably explains the rise of the Javascript libraries. The smallest of which we can find weighs in at around 80K and the biggest at well over 200K for a page with 10K of end user data. Perhaps just a tad overkill. Or, perhaps plain stupid.

Very much a work in progress like much of the stuff on this site.

Problems, comments, suggestions, corrections (including broken links) or something to add? Please take the time from a busy life to 'mail us' (at top of screen), the webmaster (below) or info-support at zytrax. You will have a warm inner glow for the rest of the day.