I completely disagree with Stefan, GWT-RPC is no more secure than REST. For both to be secure by the broad definition of the term you simply need to make them run over SSL. The only perceived security you get via GWT-RPC is by obscurity, which is not security at all.
As far as SmartGWT goes, I will warn you that I think the problems and performance hits you will run into are not worth the UI that you gain. Plus you must consider the licensing, which is required in order to use their data binding. GXT(ExtGWT) is actually nice, but their layout is expensive as well as their licensing. I commonly use REST and GWT in perfect harmony and it is very easy. Assuming you have the ability to output JSON instead of XML you can just use overlay types and get very efficient parsing. If you must use XML, it is like using any other DOM parser. I agree that built-in dnd support would be very nice, but GWT-DND isn't bad. I personally don't know what TileGrid is, but out of the box GWT isn't intended to be a widget library, but there are plenty of them out there. Google is trying to add a lot more widget support which is evident by the data presentation widgets, but their original intent was to create a flexible and efficient cross compiler, not make a pretty UI library. On Aug 11, 10:48 am, "marius.andreiana" <[email protected]> wrote: > From this point of view it makes sense. Will have a look at ExtGWT & > Vaadin. > > On Aug 11, 12:14 pm, cokol <[email protected]> wrote: > > > hi, > > > goods thoughts you had, but dont treat GWT as a framework, Google > > doesnt do it either :-) Its "just" a toolkit or better yet, a JS > > compiler with some tooling around. And being just a toolkit is more > > powerful than create yet another throw-away ajax framework! There're > > plenty wonderful ajax frameworks around so why should GWT be just > > another one?! > > > so its best choice for you to get on fast productivity with GWT - but > > from the beginning consider using a real framework BASED on GWT, i.e. > > SmartGWT or ExtGWT or I also would suggest to look at Vaadin... > > > for me personally I would prefer ExtGWT rather than SmartGWT because > > smart is not written purely in Java but is just a wrap on existing > > smartClient technology, which has some drawbacks. > > > regards > > > On 10 Aug., 10:27, "marius.andreiana" <[email protected]> > > wrote: > > > > Hi, > > > > We're working on a large project, which has the back-end is written in > > > a non-Java technology, with REST APIs. We're looking for a framework > > > to replace the current UI. > > > > I did a brief analysis of using > > > GWT:https://docs.google.com/document/edit?id=16rQknO-r3ZqfMbuIl0R52OnFcWB... > > > > I'm looking to get this group's feedback before I present my findings > > > to the team. What do you think? > > > > Thanks, > > > Marius -- 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.
