Sorry, I don't understand.
You are *using* the Tree widget right? so you can use @UiFactory in your
"owner class".
@UiField Tree tree; // UiBinder will create the Tree using the @UiFactory
and then inject it here
@UiFactory
Tree createTree() { return new Tree(myResources); }
If you want to pass the Resources from the UiBinder template, then:
@UiFactory
Tree createTree(Tree.Resource resources) { return new Tree(resources); }
and:
<g:Tree resources="{myResources}" />
The arguments are matched by name, just like with a @UiConstructor.
You want to use Tree in a UiBinder template, right? so you already have a
@UiField in your "owner class", right? so why couldn't you turn it into
@UiField(provided=true) and initialize its value yourself?
@UiField(provided=true) Tree tree = new Tree(myResources);
Really, the doc is quite clear, with examples of each different option
(simply replace CricketScore with Tree and ignore the @UiConstructor
option):
http://code.google.com/webtoolkit/doc/latest/DevGuideUiBinder.html#Using_a_widget
It's just missing an example of @UiFactory with arguments, maybe that was
what you were looking for?
--
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-toolkit@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.
