Hi,
one of the advantages of UiBinder is, that it's "building DOM
structures by cramming big strings of HTML into innerHTML attributes
than by a bunch of API calls" (http://code.google.com/webtoolkit/doc/
latest/DevGuideUiBinder.html#Overview).
First of all, I want to admit that I don't yet fully understand, at
which point this is done: Is the HTML string produced at compile time
(as far as possible), or only at runtime?
Now my question: I have several nested UiBinder composites, and I'd
prefer to build them in Dependency Injection style [*]. Does this
approach have a negative impact on the performance advantage of
UiBinder?
Thanks
Chris
[*] Here's some simplified code:
public class Outer extends Composite {
...
@UiField(provided=true)
Inner inner;
public Outer(Inner inner) {
this.inner = inner;
initWidget(uiBinder.createAndBindUi(this));
}
}
--
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.
