tag:blogger.com,1999:blog-8553235869310113140.post1949595682753961132..comments2008-09-28T16:38:54.967+13:00PhiRatEnoreply@blogger.comBlogger1125tag:blogger.com,1999:blog-8553235869310113140.post-16551758629323262962008-09-27T05:41:00.000+12:002008-09-27T05:41:00.000+12:00Last time I worked with Dojo, it seemed to have a bunch of interesting concepts that were a little too heavyweight when you needed something simple, and a little too light when you needed something more fully-featured. It also suffered from having evolved from a bunch of projects all kludged together into one framework. Eventually we ended up moving to <A HREF="http://extjs.com/" REL="nofollow">Ext</A> for our framework - if you haven't looked already, you may wish to check it out.<BR/><BR/>Another thing to take into account, I think, is a greater focus on user task-centred design within the interface (as opposed to the data-driven approach you see in a lot of older apps). If we're going to be moving to a more dynamic design for web applications, we need the user affordances that go with even-driven UI. We need to show the user what is and isn't saved data, and allow the ability to undo and revert some or all of the data (rollback isn't only an important requirement for scalable database administration).<BR/><BR/>Granted, the way a lot of those things are used in practice may be domain-specific (such is the nature of bespoke human-centred design), but having a framework that makes those things relatively easy to pick up and run with is highly desirable.Dr. Curiosityhttp://www.blogger.com/profile/04988381354102936562noreply@blogger.com