Down With DHTML - Call To Arms
Sure I can rub two sticks together to make a fire - but I don't make a habit out of it - when I have the tools readily available to make it an easier job (matches, lighters, flame throwers).
A little JavaScript and an HTML DOM can be made to create fascinating interactives, but why the hell are we still rubbing sticks together when we could advance distributed application interface development 1000 fold if we just got off our collective butts and did something about it. As an organized movement.
There is just so much about the current web applications model that pains me, especially around what it takes to do something cool and powerful with web and desktop application UI. (I'll defer my complaints to another day).
I've been keeping my own personal list of dream UI toolkit features for the past two years. Lo and behold, folks are starting to come around - but when will the W3C come around? How long will it take for us to standardize and agree upon a new and improved "grammar" for articulating web interface? Ah well, a man can dream. On to the list...
2 Comments:
Just wanted to add one important piece of information.
One of overall goals and motivators for building an interface toolkit with the features outlined is to reduce significantly if not eliminate, the need in most cases for procedural code.
To build a compelling UI, I want to drag and drop, design, sketch, choreograph dynamics and events, connect elements to data, and guide the user - all while not having to write script or code.
Interesting list! I'd be curious to see how you think various UI technologies stack up against this (DHTML, XUL, XAML, Flash, MXML, Boxely, et al).
The other question would be what "grammars" DHTML butchers/makes difficult... i.e. is this about DEVELOPERS or USERS?
Post a Comment
<< Home