Learning the Venkman JavaScript debugger

Right on the mark - as the author points out “most people who program Javascript are not programmers” so there’s some general debugger concepts introduced, as well as a deeper dive into Venkman’s capabilities and limitations.

Accessibility - why can't we all just get along?

This is the transcript from the SXSW panel of the same name earlier this year. Panelists Glenda Sims, James Craig, Derek Featherstone and Ian Lloyd discuss accessibility in web design. Its a verbatim transcription but there’s some great points woven into the banter.

The Umlauf Sculpture site (our entry into AIR Austin 2004) gets a couple of mentions - in the visual descriptions we added and the use of Flash.

Thanks, James, for the effort in getting this online - I know it didn’t come easy.

wg:Breaking onload limits

Interesting post and comments on the window.onload problem. Everyone seems to be moving in the same direction right now and (re)discovering the same problems. I’ve build a dependancyManager for a current project that I can use to fire custom “ready” or “loaded” events, by registering functions along with one or more criteria or tests that need to be true before that function is called. It keeps a timer running as long as there are un-met criteria.

I’ll see about posting some code, but meantime drop me a line if you’re interested.


A long train of thought (naps, forty winks, wombles) wound me up at the official wombles site, where I briefly wallowed in nostalgia.

It has been speculated that the wombles were inspired by the art students at Wimbledon School of Art, just down the hill from Wimbledon Common - who were (and are) great scavengers. The same art school just happens to be my alma mater, so I’ll stake my claim to this lineage and pronounce myself part womble.

AJAX Apps -- Cleaner Connections, Less Bandwidth? Maybe Not.

Port80 software and a blog post on AJAX Apps – Cleaner Connections, Less Bandwidth? Maybe Not… re-raises some interesting points on the relative server load increase an ajax application might cause vs. the traditional page-by-page web app. Intuitively you might think that the net amount of data transfer would go down as less redundant data is re-sent for each page. But as this post points out, the use of polling via ajax has the potential to actually greatly increase server load.

Of course this is apples to oranges. Polling itself isn’t new with ajax - it might have been done previously with an iframe and a meta-refresh or a javascript reload. What is new is the relative ease with which increasing sophistication of web apps can be attain using ajax. If the application is doing more work, and the user is getting more value, we shouldn’t begrudge the bandwidth used in getting there.

is the DOM ready yet?

This post ( Order of Events @ dean.edwards.name) addresses the need for a better solution than window.onload for DOM scripting. window.onload only fires after all the content on a page (including images) has loaded.. which is frequently significantly after the page has appeared in the browser. Mozilla/Firefox apparenly have the little known “DOMContentLoaded” event. Very handy. Windows IE has the readyState (or, better, the also little known ondocumentready event. Take this and brothercake’s domFunction and there’s a cross-browser solution in there awaiting the motivated developer.