This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: This is when you want a client application
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Spotted in Blogging Roller - in a discussion of what's needed to make a rich web interface, it seemed clear (to me, at least) that what you need when it gets to the point he's talking about is a client app:
Now, I'm working on a Java-based web application with very complex forms. Some of the forms have multiple tree choosers, dynamic select boxes, popup windows with dual-lists, and popups that cause the page that launched them to reload. There is just no avoiding JavaScript and our requirements are pushing us towards complex solutions like inner-browsing to reduce the number of trips to the server for page reloads.
That's what the guys at Brettspielwelt did for their interface into the various board games they support - they have a web based UI, but also a downloadable client. Most of the regular gamers there use the client. IMHO, when a UI gets complex, it shouldn't live in a browser anymore....