mariyan, The SmartGWT LGPL server side code can be as little or much depending on how the developer codes it. Pro / EE handle the server side persistence so there's minimal code to writ. With LGPL, the SmartGWT datasource protocol simply passes the relevant information for various operations like fetch, update, delete and insert. Thats it! From there on, the developer needs to act on this information to service the operation request.
A fetch operation for example will pass the startRow, endRow and the applications server side code needs to return data as XML, JSON or GWT-RPC beans in response to this request. Similarly an insert or update operation passes the data of the new record to the server. There's nothing inherent to SmartGWT that requires "more server side" code. Infact its a very simple protocol that imposes no extra overhead or server side requirements whether you're using the Restful DataSource, or the GWT-RPC Datasource. Have a look at this sample : http://www.smartclient.com/smartgwt/showcase/#featured_restfulds Hopefully this clarifies things. If you need some more information, there is plenty of information in the Javadocs and also feel free to post on the SmartGWT forum. Sanjiv On Tue, Feb 16, 2010 at 7:08 AM, mariyan nenchev <[email protected]>wrote: > Personally - yes. It is to much code for basic stuff. Don't understand me > wrong, if i look smart gwt only as client side framework, it is very good > and rich, but most users(developers) have trouble integrating it with other > frameworks, technologies and so on...You see how many users write every day > in the smartclient's forum and all have problems with server integration. > May be they are not experienced, may be it is unnessesery complicated or may > be smart gwt is like that, because smart gwt pro/ee are better. Every thing > is just bussines, and so it should be. I am just saying my personal opinion. > > Regards. > > On Tue, Feb 16, 2010 at 1:47 PM, Sanjiv Jivan <[email protected]>wrote: > >> What are you talking about? Care to elaborate instead of writing a one >> liner with a smiley which makes no sense. >> >> "until they get in touch with server side code :) (not talking about >> ee/pro)" >> >> Are you having trouble writing server side code? >> >> Sanjiv >> >> On Tue, Feb 16, 2010 at 4:38 AM, mariyan nenchev < >> [email protected]> wrote: >> >>> Very nice features... until they get in touch with server side code :) >>> (not talking about ee/pro). >>> >>> >>> On Tue, Feb 16, 2010 at 1:30 AM, ckendrick >>> <[email protected]>wrote: >>> >>>> Um, so, it was pointed out to me that I missed some major ones. Even >>>> some I wrote personally :) >>>> >>>> Drag Reorder of columns >>>> >>>> http://www.smartclient.com/smartgwt/showcase/#grid_appearance_columnorder >>>> >>>> The CubeGrid (multi-dimensional data model support) >>>> http://www.smartclient.com/index.jsp#basicCube >>>> http://www.smartclient.com/index.jsp#analytics >>>> >>>> A whole range of autoFit behaviors (not just this sample, the whole >>>> folder) >>>> http://www.smartclient.com/smartgwt/showcase/#grid_autofit_filter >>>> >>>> Also, the fact that all of these features also apply to TreeGrids (eg >>>> frozen columns and full-row editing). >>>> >>>> Also, SmartGWT's data connector architecture and it's ability to >>>> support multiple caches on the same large data set, with independent >>>> search criteria, sort direction, etc. This is needed for dozens of >>>> use cases involving large data sets, such as moving records from one >>>> category to another by drag and drop. GXT's "Store" is extremely >>>> primitive by comparison and a lot of manual effort is required to >>>> achieve something like this: >>>> http://www.smartclient.com/smartgwtee/showcase/#row_drag_save >>>> >>>> I have probably missed another 9 major grid features, and this only >>>> covers feature advantages related to grids, however this and my >>>> previous post are probably the best answer to the original question: >>>> what are the technical advantages. >>>> >>>> On Feb 15, 12:02 pm, ckendrick <[email protected]> wrote: >>>> > Carl, >>>> > >>>> > On skins, you don't sound as though you've looked at the Showcase >>>> > since 2.0, when we made a series of improvements which now has most >>>> > users commenting that our skins are sharper than GXTs. >>>> > >>>> > On grids, this is the first time I've ever seen someone claim the GXT >>>> > grids are better, I really don't think you took more than a cursory >>>> > look at the samples. Here are some of the largest features missing >>>> > from GXT's grids (there are many many more): >>>> > >>>> > Adaptive Filtering >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#grid_adaptive_filter_fe. >>>> .. >>>> > >>>> > Databound Dragging >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#grid_db_dragging_featur. >>>> .. >>>> > >>>> > Custom nested components (embed anything) >>>> > http://www.smartclient.com/smartgwt/showcase/#featured_nested_grid >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#grid_nested_form_new_ca. >>>> .. >>>> > >>>> > Pluggable data models (build a master-detail component for any data >>>> > model) >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#featured_master_detail >>>> > >>>> > Frozen columns with editing, drag and drop and all other features >>>> > still supported >>>> > http://www.smartclient.com/smartgwt/showcase/#grid_frozen_editing >>>> > >>>> > Multi-level sort >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#grid_multisort_new_cate. >>>> .. >>>> > >>>> > Automatic cache synchronization on update >>>> > >>>> http://www.smartclient.com/smartgwtee/javadoc/com/smartgwt/client/dat. >>>> .. >>>> > >>>> > Multi-level filtering >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#grid_nested_filter_builder >>>> > >>>> > Multiple rows of headers >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#grid_appearance_header_. >>>> .. >>>> > >>>> > User-specified formula and summary columns >>>> > >>>> http://www.smartclient.com/smartgwt/showcase/#grid_appearance_formula. >>>> .. >>>> > >>>> > Also, once again, these features work *together*. There are many >>>> > combinations of GXT features that don't (eg Live Grid and most major >>>> > grid features), and if you go with some hack from the forums to enable >>>> > one of the missing features, you'll find even less compatibility with >>>> > other features (and no support). >>>> > >>>> > Just didn't want anyone to think the grids are even close to >>>> > comparable. The features above are all part of the free LGPL edition >>>> > by the way. >>>> > >>>> > On Feb 14, 7:00 pm, Carl Pritchett <[email protected]> wrote: >>>> > >>>> > > We have used GXT from 1.2 to 2.1.1 on a mid-sized project. >>>> > >>>> > > Pros >>>> > > - I think the look and feel is sharp and responsive (much nicer >>>> thatSmartGWTIMHO - but look at the showcases and judge for youself). >>>> > > - Grids are the best I've seen (sorrySmartGWT) but no lockable >>>> > > columns (which Smart does have) - we had to write our own (I've >>>> > > posted them on the forums) >>>> > > - It's all java and it's trivial to debug / overrride features >>>> > > - Good community in the forums >>>> > > - Bugs get fixed if you are persistent enough >>>> > >>>> > > Cons >>>> > > - Quirky bugs and behaviour changes in each version - need to check >>>> > > for regression when taking an upgrade. >>>> > > - Only first point release if available if you don't have a support >>>> > > contract (even if you buy the product) and there can be a long wait >>>> > > (for your business / customers) between versions. >>>> > > - Mostly trivial examples in showcase that aren't like an app you >>>> will >>>> > > build (though to be fair same can be said for most GWT frameworks) >>>> > > - Not much doco / java doc, which can make complex apps / layouts >>>> > > difficult to get right - some unexpected behaviours >>>> > >>>> > >>>> >>>> -- >>>> 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]<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]<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]<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.
