I agree with Al. We need to provide an abstraction layer to allow developers to integrate their favorite AJAX library with the existing screen widget technology. This may mean the widget is rendered in the browser rather than the server as many of the MVC operations move to the client in AJAX tool kits, but it would be nice to have a standard way to represent those UI's in a generic syntax that works across technologies.
Brett On Wed, Jun 3, 2009 at 9:31 AM, Al Byers <[email protected]> wrote: > Before we choose a UI library, it might be better to determine what sort of > advanced screens and features we are shooting for (eg. trees, master/detail, > heirarchical menus, etc.) so that we can enhance the widget architecture to > handle them. Then the widget component can act as a common definition > language for front-end systems built on different libraries. > > When it comes to front-ends, I think we should try to separate them from the > rest of OFBiz, as people get very religious about them. I have spent almost > a year and a half with Dojo and liken it to the amount of time it took to > become familiar with OFBiz (which is going on 8 years). I doubt that I would > switch because OFBiz decided to go with one library on another. > > -Al >
