Re: extend UiBinder engine

On Monday, June 2, 2014 8:29:14 PM UTC+2, Steve C wrote:

Yeah, that would be useful.

I'm kind of curious about the part: "I'd like to see something a bit more advanced where you don't need to declare the @UiFields".  I may be misinterpreting that, since I don't see how you could use the Java class without the fields.  Or you just talking about assuming the presence of the annotation, since the Java field names have to match the ui:field attributes in the xml anyway?

What I meant is that the factory you give to UiBinder would work the same as a @UiFactory in your class: no need for a @UiField/ui:field; if you have a <foo:MyWidget/> in your ui.xml, whether it has a ui:field or not, it'll be created by the factory. My proposal was just to be able to move @UiFactory methods into a class that could be shared by several UiBinder instances; i.e. exactly what you asked for ;-)

I should have answered: "you're right, it's not possible, but I proposed the exact same thing in issue 6151" ;-)

 

On Monday, June 2, 2014 12:21:33 PM UTC-4, Thomas Broyer wrote:

On Monday, June 2, 2014 3:32:41 PM UTC+2, Steve C wrote:

It would be nice if the UiFactory methods could somehow be separated out into their own class for reuse, but I don't think that's possible.

Cf. the discussion in https://code.google.com/p/google-web-toolkit/issues/detail?id=6151 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.