I just published a new longer article (40 pages) trying to explain the differences between DHTML and DOM scripting. The article explains what DHTML, the DOM and DOM scripting is and shows how to create a web page with dynamic elements like tabs, a slide show and a big product shot in both ways.

• Check From DHTML to DOM scripting now

The DHTML explanation is annotated with explanations why some of the techniques are a bad idea and the DOM scripting version explains why some of the assets are good ideas. As a summary:

DHTML issues:

1. Script dependence – Users without JavaScript get stuck or get elements that only work with JavaScript but don’t do anything for them.
2. Mixing presentation and functionality – If you want to change the look of the effect you need to hack around the JavaScript.
3. Assuming functionality without testing for it – what it says
4. Keeping maintenance JavaScript based – Maintainers are expected to change the script when they want to change the effect, and search through the whole script.
5. Mixing HTML and JavaScript – what it says
6. Blaming the user – Users get messages like “you cannot use this as your browser doesn’t support it, update your browser” instead of just not getting the functionality if it is not 100% necessary.
7. Taking over the document – one onload to rule them all

DOM scripting assets:

1. Progressive Enhancement – check if things are available, then apply those dependent on them
2. Ease of maintenance – keep the maintenance as easy as possible via dynamic CSS classes and properties at the beginning of the script
3. Separation of Presentation and Behaviour – add dynamic classes instead of changing the style collection
4. Separation of Structure and Behaviour – use dynamic event handlers and generated elements instead of onclick and NOSCRIPT
5. Using modern event handling – more than one onload please
6. Avoiding clashes with other scripts – avoid global variables and encapsulate functions as methods in an object

Of course, you can disagree :-)

I finally got the go-ahead to look for a replacement for me in the company I am still working for. I am leaving here on the 14th of April, and will join Yahoo on the 24th.

So, if you are:

• A very web standards and quality orientated Interaction Architect
• A good team leader
• Experienced in various development Frameworks (.NET,Spring,PHP)
• Fully up to speed on Accessibility regulations and development practices
• Experienced in conducting Usability Testing
• Interested to work in the South West of London / England

Drop me a line and your CV at the new yes.i.want.to.be.chris@googlemail.com email.

I will treat your CV with confidentiality and cannot promise anything. However, I do think I can find a better bunch of CVs here than our HR department can get through agencies :-)

I was just mildly shocked that my book is already on Amazon.com while I am still writing chapter 6 of 9!

So I guess it is time to cut down on the posting here and other things like bathing, eating and sleeping to ensure I get it ready in time to beat the next Harry Potter in the sales ranks (or something like that).

Allow me to be a bit narcistic for a moment – don’t worry it does not involve a podcast of me talking about web design stuff:

I just wanted to announce that I am quitting my current job on the 14th of April and from the 24th of April (2 days before my birthday) onwards I will work for Yahoo UK as a web developer.

I am quite happy to join a company that dabbles in the same market sizes I worked in the last few years but really does subscribe to ideals like web standards and User Centric Design. To illustrate my dedication to this cause it might be of interest that I took a slight paycut and will not have the fancy “Lead Developer” title any longer. I think having fun and getting satisfaction out of what you do is more important anyways.

Evolt.org, has announced a redesign contest. Quoting Martin Burns:

Hi folks
Ever looked at the evolt site and thought “I could do better than that”?
Ever thought “All very nice, but it’s a bit 1999”?
Ever thought “It’s not using half the potential that Drupal (plus
modules) gives it”?
Ever thought “Wish we could be as gorgeous as $insertsitehere”?
Well, now’s your chance. Evolt.org is proud to announce a grand
Design Contest, to
redesign www.evolt.org. If your entry wins, it becomes the new design – simple, eh?
Background, rules and so on at the 2006 WEO Design Contest
but the key things are:
1) The site’s staying in Drupal
2) Ease of implementation is as important as beauty of design
3) Entries in by end April

Give us a hand and have a go!