uibinder separate layout out of your ui. pre uibinder we would use inner class to create hierarchy like structure for layout right inside java! That kind of code would look bit messy and unstructured to some one who is not familiar with the style of programming. As a developer, I would like to keep complete control with me and avoid more moving parts, especially non debug-able xml code!
But in a way your java code looks much cleaner with uibinder. Since uibinder is responsible only for laying out your components, it nicely separates itself from the corresponding java class. Once you get used to it, you start liking it. When uibinder was introduced, I was hesitant myself but now I have adopted it. In fact I am craving for better support of some panels and widgets. Gwt programming is such that in most cases(unless you go out of the way) you end of creating not more than one or 2 pages of ui.xml files. hence uibinder files are very readable and usable! Infact my question is, why xml? why not yaml or json? Rakesh Wagh On Jun 20, 6:23 pm, spierce7 <spier...@gmail.com> wrote: > Does using the UI Binder provide any benefits? I watched some of the I/ > O conference, and it seemed like they made reference that the UI > Binder using the browsers native rendering engine (or something like > that), and it being a lot faster, but they didn't really specify > whether that was the layout panels, or using the ui binder. > > What are the benefits to using the UIBinder, and where can I learn to > use it? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
