On 01/21/2011 11:28 AM, Ed wrote: > > Hi Jeff, > > Good question. > > We are looking for a look and feel that GWT provides, also it keeps us > from developing js libraries that are custom for delivering the > presentation layer which GWT does very well. > > We are migrating from html template's to a more modern architecture > to give our users a new face. I guese we could of used jQuery to ajax > things up.
So there are two selection criteria: AJAX and widgets? > > I think we are wondering if it would be best to stick to plain ol GWT > or use something like GWTEXT or some of the other widget libraries. If you search the list archives, you'll find plenty of opinions on that criterion. > > The ext libs provide alot of widget functionality, but there has to be > some compatibility issues lurking around the corner. Ibid. > > We have a working interface now using a combination of GWT and html > loaded into an iFrame, which is a worker area for user entry into the db. > > While we have concentrated on a staged implementation migrating the UI > first then we can concentrate on the backend. Agreed. I think you'll also find the MVP path a useful upgrade. I ported an app to GWT from Perl. Splitting out the view implementation proved a worthwhile refactoring. You should also investigate Gin. It will prove quite helpful when it comes time to mock certain behavior before it's ported/rewritten. > > Your comment is appreciated, surprising but welcome. When we > investigated migration plans and an update to the legacy system we got > stuck on GWT. It sounds like you've already made the decision to move to GWT. You should also consider the development benefits that GWT provides (leverage Java to provide a development/testing platform). This means installing Eclipse and the Google Plugin for Eclipse. IMNSHO, you should discard the JS prohibition. It will only prove an impediment. Although there is an argument to be made for graceful degradation in the absence of JS, it looks as though your app will not work as intended in the absence of JS. On that note, you should consider the effect this decision will have on your customers who don't/won't upgrade their browsers. You may be in for some annoying surprises when you discover that your app doesn't function as intended in your Important Customer's IE6 browser. Cheers, jec -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
