I have used both libraries. I would say, stay away from SmartGWT. It's a wrapper on the SmartClient javascript library, which means the API is an almost direct transliteration from Javascript. As Joshua Bloch will tell you, direct transliteration of APIs is bad. A lot of times, the API methods don't do what their name say and can cause some surprises...the deal breaker for us was it didn't integrate with native GWT widgets well. The problem I had at the time was it customized GWT widgets disappear from a SmartGWT container when it's resized and so on.
I have no ties with Ext whatsoever, but we're using GXT now because it's built on top of GWT (not a wrapper of some JS library). Customization is much easier and whenever a problem arises, you can always trace down to the very bottom because they're all written in Java. The same cannot be said about SmartGWT. Having said that, GXT has quite a few quirks as well. Seems they've been abusing generics and the event system is terrible to work with. If you have the time and resource, I'd say writing in pure GWT is the way to go. Those are my subjective opinion. I've no intention of trolling. On Feb 2, 12:28 pm, mariyan nenchev <[email protected]> wrote: > Thanks i look at it, but i prefer to use pure gwt&incubator. Advanced > components also seems good. > On Tue, Feb 2, 2010 at 7:19 PM, David Durham <[email protected]>wrote: > > > > > On Thu, Jan 28, 2010 at 6:16 PM, ahhughes <[email protected]> wrote: > > > For future reference.... > > > > At the time of writing the following are available: > > > GWT v2.0 > > > and..... > > > SmartGWT v2.0 (http://code.google.com/p/smartgwt/under Apache > > > License) > > > Ext GWT v2.1.0 (http://www.extjs.com/products/gxt/under weird LGPL > > > License) > > > > I don't want to discuss Ext GWT's weird license. It's weird, there's > > > no updates... e.t.c. e.t.c. The question is, if why would you purchase > > > it over SmartGWT? I am looking for technical reasons such as features, > > > performance, jsni wrap vs pure compiled gwt, or especially full GWT > > > 2.0 compatibility e.t.c. > > > > Help would be great as there are so many re-packed versions of these > > > things floating around as well as the fact a lot of information is out > > > of date (and so will this thread be in the not so distant future). > > > I like a GXT and wrote a form generation library for it that you might > > consider. > > > http://gxtforms.googlecode.com/ > > > There's an appengine demo linked to from the project pages. > > > The basic is idea to annotate Model classes and get forms with > > data-binding fairly easily. For the next release, I'm working to make > > the field types and rendering more easily extensible. If anyone is > > interested in contributing to this project, please let me know. > > > -Dave > > > -- > > 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]<google-web-toolkit%2bunsubs[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
