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.
