This is a good advice when you have much time and the expertise to develop nice looking widgets.
But in reality this is not the case. >From my point of view a small team is not able to develop something which is as good as ExtGwt (aka GXT). (E.g. a powerful grid component) We took GXT to develop our app. In general we had no huge problems to solve until now (at least in context with GXT) Regards, Martin On Oct 28, 1:55 pm, "Arthur Kalmenson" <[EMAIL PROTECTED]> wrote: > I would say go with neither. If you look at the group, you'll find > that there are endless problems with these libraries. They're shoddy, > poorly put together, slow and nowhere near the level of quality that > you come to expect from GWT. The library is made by Javascript > developers who have little to no Java knowledge. If you want a well > test, well designed toolkit, stick with vanilla GWT and make widgets > yourself. > > Regards, > -- > Arthur Kalmenson > > On Mon, Oct 27, 2008 at 11:50 AM, Suri <[EMAIL PROTECTED]> wrote: > > > Not sure if there is a thread ever discussed on this. If so, I'd > > appreciate help in locating it. Tried a search and it decided to > > exclude the gwt part and search only for ext which isn't much help. > > Anyway, for all the people using either of these, I figure it might be > > good to get some feedback on the drawbacks and strengths of each and > > have something helpful for everyone like me trying to decide which is > > a good fit. Any ideas? Sorry if I seem abstract, I just thought the > > more general the better. > > > Thanks > > Suri --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
