Probably what they mean to say is that the SmartGWT library will not get any more efficient when you recompile your app that uses it under future GWT releases. This is because it is comprised of hand written (I assume) Javascript and is not like the native GWT widgets like say, com.google.gwt.user.client.ui.Flextable, which may be better from release to release in terms of the generated Javascript. Unless the SmartGWT people make a new release of their underlying SmartClient library, their com.smartgwt.client.widgets.grid.ListGrid isn't going to be any faster. Nor will any tweaks be applied by the compiler to make accommodation for browser quirks within the ListGrid javascript. It seems to me though that the SmartGWT people have done a pretty good job taking care of that already. This is a quality issue that you'll have to be the final judge of, and it falls on SmartGWT's shoulders, not GWT proper.
This does not mean that using the SmartGWT library code will stop you from benefiting from those features elsewhere. I mean, there's plenty of non-widget code that will be optimized and I have a feeling that code splitting can still serve a function in the parts of your app that don't rely on SmartGWT. Sadly, one of the downsides to SmartGWT is its size. But hey, you wanted a cool looking, full featured widget library, right? You'll have to comprimise by expecting a larger download, more script evaluation, more memory consumption, etc. SmartGWT has served me well in one of my work related projects. Realize it is it's own animal. Mixing the GWT widgets with SmartGWT's is not meant to be seamless, and I can't recommend doing it. This means that what you've learned to do to create interfaces with GWT's widgets doesn't directly transfer to SmartGWT. It has it's own set of layouts and forms and rules you need to follow. They cover a lot of bases though, and in my case, grid functionality was so important that it outweighed any other feature. GWT's grids don't hold a candle to SmartGWT's. I found it well worth the time to use, even though I did not use the Datasource features to populate grids. If anybody can point me to a really robust grid class that handles tens of thousands of records and does drag and drop, nice image cells, let me know. My users are very happy so far with the interface that SmartGWT let me create. I will say that I probably wouldn't use the library for a typical internet app, because it is quite fat. Loading the SmartGWT showcase on my girlfriend's old P4 with 256MB of RAM, for instance, was not pretty. For enterprise apps on an intranet where I know my user configurations are sufficient, no problem. On Jan 12, 7:56 am, Stine Søndergaard <stinespl...@gmail.com> wrote: > Hello again :) It would be fantastic if you could maybe attach a few more > words to this: > > "SmartGWT is a javascript wrapper - which > means you don't get the advantages of the compiler, browser specific > code compiles, code elimination, and runAsync (code splitting)." > > ... I am not sure I understand it ~:/ *Sigh* > > Thanks a loooot, > Stine :)
-- 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-tool...@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.
