- September 2010
- August 2010
- July 2010
- June 2010
- April 2010
- March 2010
- February 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- December 2005
- November 2005
- October 2005
This: Yahoo! User Interface Library has to be the beginning of the future of UIs on the web. Back in the old days when I used to program with the MFC, the two things I loved about Microsoft’s ubiquity were that I had a choice of ready-to-use controls/widgets/components at my fingertips that I could easily stick into my application to give it complex behaviour and the fact that if I chose to thus stick, everyone knew how to use it. Java came along (ignoring the disastrous AWT) and sort of made it work (again). Mostly the behaviour was what you expected, but then sometimes. Ah, sometimes. The early days of the web were OK – it was just tables after all. But then the fatal promise of Javascript and DHTML loomed. Suddenly it was roll-your-own time again. And it still is. Years and years later.
I can’t begin to describe how tired I am as a user of struggling with yet another calendar widget on yet another budget travel site. Is it going to pop up with a month view? Will it show me the current date? Will it insert the date if I click it? Or is it just advisory, showing me which days of the week my 1 euro flight is really available on (none).
It’s not that I blame the poor UI developers. The first time you get lumbered with working on a webapp with complex client-side behaviour, you discover that nobody is out there to help you. Or rather everyone is… You want to add a tree control? MFC/Java/.NET apps?, TCL/TK? – no problem. Webapp – take a look at Webmonkey, they have something interesting. It sort of works. Then there’s a bunch of developers with really neat open source controls – how about them? Or how about ASP.NET, Struts, Tapestry…? Hang on, I just wanted a tree I could click and now I have to use a whole framework? (Yes I realize that MFC required a whole OS, but somehow that didn’t feel as bad as a framework. The OS was just kind of there hanging around doing nothing after all.) I’m back in UI pre-history, so what will I do? Take something that sort of works and adapt it so it does. YAWPUS. Yet another widget for the poor users to struggle with.
What I would dearly love to see is industry heavyweights getting together, feeling the love, knocking out some standard components that are so great that UI developers will flock to use them, thus taking the weight off my brain when all I want to do is buy cheap tickets. So as Nat on O’Reilly Radar said “Kudos to Yahoo!”.
No Comments »
No comments yet.
RSS feed for comments on this post. TrackBack URL