>The latter will give you more flexibility I'm curious about this. In the Java case, GWT Designer's parser can reverse engineer most hand-written code and its code generator can be configured to match most coding styles. It is general quite forgiving about manual refactoring and has nice support for UI factories, nested composites, etc. Since the tool was designed to allow you to work back and forth between the source and the design view (and always keep the two in sync), I am wondering what flexibility is lost by using it (even if you just use it to visualize and tweak what you have written by hand). We are always interested in ideas for improving the tool, so suggestions for making it more flexible are welcome.
In the cas of UiBinder which is much more constrained versus coding in Java, our hope is that anything you could code by hand in the UiBinder, you could also build using GWT Designer. Any areas where this is not the case represent an opportunity for improvement on our end. We first introduced basic support for UiBinder in September (right after the tool was acquired by Google). Our latest v8.1.1 release from last week (in conjunction with GWT 2.1.1) has improved our UiBinder support considerably. -Eric -- 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.
