While I have not yet tried UIBinder on a problem in my environment, I did try GWT Designer. Very quickly I went back to coding my UI by hand.
My interface is largely shaped by the results of calls to a database via a clearly defined API. That means I make a lot of GWT RPC calls and act on the results, results that can vary widely. GWT Designer does not (or at least 2 years ago did not) support RPC calls. Designer's recommendation was to write local routines to simulate the call. I found that approach unsatisfactory--it was both slow, and prone to error. After all what better way to try out real world data than by pointing at a real-world system? By the time UIBinder was introduced I was too far along to go back and retro fit it. Now that my app is in release, I'm ready to take another look at UIBinder, especially in relation to new GWT 2.1 stuff like cell widgets. On Dec 21, 8:55 am, Matthew Hill <[email protected]> wrote: > The true question he is probably asking is should he use a WYSIWYG tool or > write the interface by hand. > > My advice would be to try both. The latter will give you more flexibility. -- 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.
