If you place widgets in your UI binder template then the system will
instantiate the appropriate
widgets even if you don't refer later to them in your code. The system
still needs to create them
as they are required to render the HTML page and implement
interactions with the user.
As a rule, I
With UiBinder, I thought that GWT compiler would prevent instantiation
of widget with no ui:field attribute by directly inserting the html
code of the widget.
In other words, I thought that:
g:VerticalPanel
g:HorizontalPanelg:LabelLine 1/g:Label/g:HorizontalPanel
I don't know if you're right about thinking that there's still situation
where an HTMLPanel or layout panel, without uifield is the best way to go,
but I do know that we should use as often as possible html code instead of
widget for the very reason you exposed.
BUT I'm still wondering if once
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)?
Its best to minimize usage of widgets when you can; there is always a cost
associated with them. Specifically,
Thanks for your help.
I guess, even after java - javascript compilation, the first example
will still instantiate a javascript object for each widget, right?
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,
