gwt-dnd works very well - you probably shouldn't use the fact that dnd is provided by a 3rd party library as an argument not to use GWT. I've not used REST, so don't know if the same would apply there, but it may.
Good reasons for using GWT include: - it's in java, so you get all the java tools (good IDEs, debugging, refactoring etc) - debugging in java in your target browser is worth quite a lot - it generates highly optimised javascript I believe that with SmartGWT you lose the code splitting ability for the javascript parts of their library. I don't know how viable the hybrid approach you've mentioned is - check whether their widgets are compatible with vanilla gwt widgets. Paul marius.andreiana 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-r3ZqfMbuIl0R52OnFcWBCOKTPm1wDCzSQgvU&hl=en > > 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.
