With ref to your question: "So am I right to think that I should never use widget inside UiBinder xml except if I have the attribute ui:field (in other words, except if I need it in the Java code)?"
I don't think this can be true for me. In fact, I am glad that GWT compiler instantiates all the widgets in the ui.xml template even for widgets where the java code does not have a @UiField declaration. The reason is, I would have a hierarchy of widgets defined in ui.xml template and I would want the whole hierarchy generated but what if I only need to manipulate three of the widgets? Being a lazy programmer, I only annotate those three widgets with @UiField, because @UiField annotation helps me get a reference handle on those widgets. I really don't want to spend time annotating widgets that I don't wish to manipulate in my java code. But I should still want those unnamed widgets generated - otherwise, my whole ui structure would collapse. -- 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.
