@media 2006 thoughts:
I really enjoyed @media 2006, I had a really hard time deciding which talks to go to. I did find some of the content a little light weight, but there were a couple of sessions which I got a lot from.
The general themes of the conference where well captured in the final panel. Although the Web Standards battle continues most leading designers\developers are now moving on. Looking forward the panel thought that open data, Microformats and mashups where going to make the biggest impact.
It was hard to miss the strength of the Microformats message. I agree with Jeremy Keith's recent post Microformats are at a tipping point. The web standards movement has championed the importance of semantic structure to a whole generation of designers\developers. Microformats seem like the next logical step, their simplicity is beguiling. Real world examples are starting to blossom with Technorati Search, Yahoo! (cc) search and Tails extension for Firefox.
Jeff Veen did a fantastic talk about designing web applications around participation, trust and improving the user experience. He quite cleverly side-stepped the whole Web 2.0 hype debate by just concentrating his talk on the benefits of good information and interaction design. The points that most stood out where:
- Treat users as peers
- Let users control their own data
- Actions should be without cost, build undo’s and back steps
- Build a architecture of participation
- Your site is just one piece of a bigger picture
- Let the user experience build the navigational architecture
With the introduction of richer user experience and interaction, DOM Scripting was a major part of the conference. Nate Koechley gave a interesting insight into the development of three Yahoo products, contrasting the different approaches taken.
Yahoo are about to release a new version of their home page. It will contain a lot of interactive elements and on-demand loading of content. In the future this redesign could be seen as a turning point for the uptake of AJAX/DOM Scripting, much as the CSS redesign of Wired is now considered a defining moment for Web Standards. This is not because of the quality of the design, but more that such a large commercial site is backing the technology.
Jeremy Keith's talk on using DOM Scripting to plug the holes in CSS was great. Although I completely agree with the use of unobtrusive JavaScript, I do wish that those evangelising DOM Scripting would spend some time addressing the onload issue.
Most of the speakers and panellists believed that there would be little technical development in HTML layout until CSS3 apart from the introduction of IE7. Andy Clarke’s talk tryed to direct designers to look out from the web for inspiration and make web design less self-referential.
It was great to meet lots of people at the socials Chris Heilmann, James Edwards, Ian Lloyd Dan Cederholm and many more. Had some great discussions and a few too many beers.
Useful links
Slides
- Jeffrey Veen talk "Designing the Next Generation of Web Apps" talk
- Tantek Celik talk "Microformats: Evolving the Web"
- Jeremy Keith talk "Using DOM Scripting to Plug the Holes in CSS1"
- Hot Topics Panel
- Nate Koechley Y! v. Y!
- Dan Cederholm: Bullet Proof Web Design
- Jeffrey Veen: Designing the Next Generation of Web Apps
- The New Accessibility Guidelines: WCAG 2.0
- Chris Wilson: IE7 and beyond
- Jeremy Keith: Using DOM scripting to Plug the holes in CSS
- Eric Meyer Keynote
Comments
1
Matthew Pennell
You mean this onload issue:
http://dean.edwards.name/weblog/2006/06/again/
?
Posted 19 June 2006 14:17
2
Glenn Jones
@ Matthew as you probably already know, there are a number of scripts that deal with the windows.onload issue. I personally like brothercakes
domFunction, but there are many more.
At the moment many who are promoting unobtrusive JavaScript and progressive enhancements as the way forward just don’t talk about this issue. If you ever try out any of the page hijacking techniques you will at some time come across this problem.
I am probably more interested in this subject than most people because of the high number of adverts carried by our client’s sites. Sometimes it can take many tens of seconds before the window.onload is fired.
All I was trying to say was that it would be nice to hear someone like Jeremy talk about this issue and the different approaches to solving it.
Posted 19 June 2006 19:26
Comment Guidelines
All comments are moderated. Please keep comments relevant. Abusive, inappropriate and anonymous posts may be edited and/or removed.