Hi Nina,
Did you get an your questions answered? If so, could you share them?
I'm working through migration of old GWT code to use UiBinder, and had
related issues. UiBinder has eliminated hundreds of lines of my old
code, and the app loads faster overall since the UI is much thinner
(horray!).
My interpretation of the style of GWT architecture leads me to believe
that there should only be one UiConstructor annotation, and that it
should be on the constructor that accepts all possible arguments.
This jives with the error message you received.
The binding clearly works based on Java argument names, but are there
other ways to bind?
How can I use a Widget in a constructor within a UiBinder template?
Thus far I've only been able to set primitives and Strings in a
@UiConstructor annotated class within a ui.xml. I'd like to see an
example of setting a Widget.
For example, how can I do this:
@UiConstructor
public ImageHyperlink(final Image img, String targetHistoryToken) {//
etc}
then:
<my:ImageHyperlink ui:field='aHyperlink'
targetHistoryToken='nextstate'
img='prettyImage' />
I'm having trouble getting the prettyImage to work. Is this the right
way to do this?
thanks,
Jason
--
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.