You can't stat about 'uninformed choice', quick doesn't mean dirty Enough of us to quickly test and evaluate a new framework and SmartGWT does'nt meat our requirement. We are moving from java to GWT with our own framework and it was really more easy to do it with GXT. We have no needs to have javascript knowledge when adapting / modifiying core GXT, SmartGWT use a lot more javascript. Even creating new widgets could be made easily with GWT, with SmartGWT we must have good javascript skill to achieve the same task. Same arguments about Hibernate and CRUD, we can't dig enough under the hood with SmartGWT. Another good point for GXT is the instanciation Windows builder Pro support. I don't want to say that SmartGWT is bad nor good, It does not meet our criteria, point.
-- 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.
