Looks quite good – they use a lot of jQuery in the demos

It’s nothing “stable” and I wouldn’t use it in a live production app, but it’s a “proof of concept” though

.t

Check it out!

I’m guessing this relates to the recent Basics 3 of 3 podcast (I did two this week, bit confusing after 100+ days off ne).

I think I agree with you. In all the code examples, I use $() myself, convention yanked straight from prototype.js. I’d only use clickme.onclick if clickme was a JS variable, that’s probably what I meant on the podcast, which just goes to show why code snippets don’t make for very good podcast content .

<button id=”clickme”>Click me!</button>

Anyways, I have a slight beef with your description of adding onclick handlers to objects.

Say we have some html:
click me!

and some javascript: (using your method of adding click handlers)
window.onload = function() {
clickme.onclick = function() {
alert(”I was clicked!”);
}
}

now, this works in most browsers, but it’s not W3C compliant. Firefox will yell at you if you do this. The ‘proper’ way to do this is to add your event handler like this:

document.getElementById(’clickme’).onclick = function() {
alert(”I was clicked”);
}

now, typing document.getElementById() every time is a big pain Which is why I choose to use prototype.js (http://prototype.conio.net) to abstract a lot of the browser differences. prototype.js includes an alias to document.getElementById (with a couple of extra features) you can call via $()

so …. the above code would now look like:
$(’clickme’).onclick = function() {
alert(”I was clicked!”);
}

but then… I would also take this a little farther, and use behaviour.js (http://bennolan.com/behaviour) .. but that’s of course, a personal preference

Thanks and keep up the great work with the podcast!