I've been studying both SmartGWT and EXT-GWT (GXT) lately thinking about similar issues (which is the "right" one to use and under which circumstances). What I've found so far suggests a few major differences:
SmartGWT seems to be a thin GWT wrapper around JS libraries as compared to GXT's "pure" GWT java SmartGWT seems to specialize in writing less code: DataSources and certainly their server side wizards (need to pay for those) allow you to build applications quickly with less code generation. This is both a strength and a weakness IMHO, it works fabulously when it does work but it can be difficult to debug if you have problems. It can also be difficult to add new features to existing widgets or hook into the widgets because they seem to defer directly to the Smartclient JS libraries. GXT requires you to write more glue code (especially in moving data around and inserting values) than SmartGWT but it is easier modify widgets and functionality by overriding methods. GXT is GPL, SmartGWT is LGPL SmartGWT supports selenium Neither one has a ton of MVP classes out of the box IMHO SmartGWT is a little less intuitive to a GWT coder, there will be a learning curve because it remains more similar to the SC ajax library than to GWT. GXT has a similar but smaller learning curve because the Store/bean/service pattern is pretty familiar to most GWT coders Personally I'd like to know which one is going to be the industry standard. Google seems to be ( I have heard this though it may be incorrect) throwing its weight behind SmartGWT which makes me wonder if GWT is going to somehow absorb SmartGWT. If that's true I hope they get rid of the thin wrapper approach. Ignoring for the moment the industry standard question, I'd recommend using SmartGWT to minimze code generation if you're not doing anything especially odd and GXT if you think you may need to alter the underlying code. For example, SmartGWT only seems to allow ListGrid grouping with result sets entirely on the client side, if your result set is several thousand in total this isn't so good, especially if you're groups may only be 10 or 20 items each. We're trying to decide the right way to handle this. I don't know if I answered your question but I hope something here was helpful GL On Nov 15, 6:50 am, nino ekambi <[email protected]> wrote: > For what i know GXT is planing with version 3 to support more GWT > feartures > For the other libraries, no idea. > > 2010/11/15 Stefan Bachert <[email protected]> > > > Hi, > > > to which degree does framework which are on the top of GWT, follows > > GWT and support new features? > > > - smartGWT > > ? MVP > > ? Cell Widgets > > ? RequestFactory > > > - GXT > > ? MVP > > ? Cell Widgets > > ? RequestFactory > > > - mosaic > > ? MVP > > ? Cell Widgets > > ? RequestFactory > > > .. more ? > > > Stefan Bachert > >http://gwtworld.de > > > -- > > 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%[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.
