On Dec 1, 9:48 am, mariyan nenchev <[email protected]> wrote: > Yes, it has nothing to do with MVP. If your team is small and none of them > are designers i don't see a reason to use uibinder.
We're a small team (4 full-time devs, only 2 of them working on client code; none of us is designer) and we do use UiBinder for nearly 2 months (2.0 MS1) and find it very useful, and productivity gain! For best performances (we're targeting IE6, as it's our client's "company standard", unfortunately), we started doing some screens using HTMLPanel. UiBinder binder makes the code: - easier to read (Eclipse is not good at formatting String concatenations, much better at formatting XML) - faster to write and less error-prone (now that we have auto- completion and validation for GWT widgets in the Eclipse plugin) - easier to understand, because the Java code for the view is simpler Compared to our "legacy" app (UiBinder is used in a new app, to work side-by-side with a year-and-half-old GWT app still using widgets the GWT-1.7-way, without MVP, DI, etc.), the code is much "cleaner" with UiBinder. My only fear is that we hit the 31-stylesheets limit of IE, which might come quite quickly when using CssResource (both "explicitly", and "automagically" through UiBinder) -- 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.
