We used GWT-Ext and tossed it in favor of Ext-GWT (often referred to as GXT).
I've said this before in this forum so I'll just be brief here as you can search the forum for more details. - It's been said MANY times so you know it's true: It wouldn't be accurate to say the documentation is poor. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data "loaders", etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
