Whist reading through the articles at A List Apart I came across this one on Making Compact Forms More Accessible, which explains how to go to a whole lot of trouble to create labels for username and password fields in a compact login form. The effect is good, but the reams of CSS and JavaScript needed to accomplish it are a little bloated, I think.
Up until recently, for a very long time, I’d kind of lost my mojo with web development.
Five years ago I was regularly reading the blogs of all the industry names, and hankering after the new evolution of each browser for the baby-step closer to consistent standards support it might bring. Out of my own pocket I’d buy books on PHP or CSS, as well as subscribing to publications like PHP Architect to keep me abreast of open source projects and new techniques.
Then, a couple of years back (I’m not quite sure when) I just simply lost my enthusiasm for it, gave up reading the blogs, cancelled my PHP Architect subscription, and stopped giving a toss whether I was using the latest trendy CSS hack to achieve some ridiculous positional trick dreamed up by a pillar of the web development community. Whatever passion I initially had for web development was gone.
Over the last few weeks I’ve been checking out various JavaScript frameworks for use in a site I’m building at work. There are a number of frameworks out there, from Prototype, which I previously used to do some AJAX stuff on WipEoutZone, to JQuery, the wonderfully named MooTools, and Yahoo!’s own Yahoo! User Interface Library.
Most of them aim to provide shorthand ways of accessing DOM elements and handy methods that take the pain out of getting a JavaScript app up and running. Well, that’s the plan, anyway. Some do certain things better than others – MooTools is tops for fancy effects, while Prototype is good for grunt work. YUI seems a bit limited in its scope, although the documentation is pretty good and has a good number of working examples. JQuery looks to offer a more compact way of getting results that take more work with Prototype, although it’s the one I’ve looked at the least.
Despite the fact I’ve used it before and gotten some simple things working with it pretty swiftly, Prototype has excruciatingly sparse documentation, which makes getting a working example of almost anything a pain in the ass. Even worse is that the online documentation isn’t searchable – seriously, what the hell use is online documentation that isn’t searchable? Even if you do find what you’re looking for there is rarely any sample code to give you something to go on, so attempting most things is a bit of a shot in the dark.
It looks like I’m going to have to take a good look at JQuery when the dust settles with what I’m doing right now. The funny thing is that in the end it probably wont come down to me choosing the “best” framework (heck, maybe they’re all the same under the hood) – it’ll come down to using which one has the best documentation.