I have developed a large app using GWT-Ext, unfortunately the developers of GWT-Ext then dumped it and switched to Smart-GWT. I can see their reasons for doing this (Ext-JS library version they used had some shortcomings) but it has left me a few problems. As a result of this I started evaluating how best to migrate away from GWT-Ext. This involved looking at the alternatives.
My preferred option was to go for a pure GWT approach mainly because you no longer have to worry about working around problems in a wrapped JavaScript library - debugging these type of issues is not easy. Unfortunately the current pure GWT widgets just aren't good enough, so I have had to postpone any migration for the moment. Anyway to get back to the point I think that although the hybrid approach may be tempting in the short term, you will just be storing up long term support problems. The other option that I haven't fully explored yet is the GXT (Ext- GWT) approach, this is a pure GWT version of the Ext-JS library. The only issue I have with this approach is that it requires a commercial licence. As to your REST question, I make extensive use of this now from plain GWT and have no issues with it at all - in fact I've now started using it instead of GWT-RPC simply because it means that our other clients can then easily make use of the various services our server provides. Rob On Aug 10, 10:03 am, Paul Robinson <[email protected]> wrote: > 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-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.
