How would the declarative UiBinder jeopardize browser independence? Personally, I like UiBinder overall. There are few cases where I find it a pain, but overall for any screen which has multiple elements I have found it significantly cuts the amount of code required. It also has the benefit of making the Java class file significantly shorter making it easier to find the logic and not focus ignoring all the "wiring" of elements. This provides for much better separation in my opinion which simplifies code maintenance.
Since I know it will come up. Here are the major downsides as I see it for UiBinder: -- UiBinder requires two files which have to be maintained in sync. -- UiBinder hides to much on occasion. This can produce very ugly HTML. You really have to learn how UiBinder generates the result (same issue with GWT, but adds another layer on top in my opinion). -- UiBinder is not friendly in terms of using a ClientResourceBundle for CSS. (I use addStyleName a lot). So I end up adding most style names via Java code. Tim On Oct 16, 2013, at 2:19 PM, Tim McClure <[email protected]> wrote: > What is the most used approach in GWT- the native approach where all web code > is generated through GWT or the declarative approach where HTML/CSS templates > are used and integrated through UIBinder? It seems the declarative approach > was introduced for separation of concerns and allowing graphic designers the > ability to contribute to GWT systems. However could it be argued that the > declarative approach jeopardizes the browser independence guaranteed by GWT. > We are new to GWT and we are trying to determine which direction we should > take - what is the most recommended design pattern? > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
