Re: extend UiBinder engine

Hi Thomas,

Yes it's funny you wrote that the proposed solution isn't convenient as an answer to my proposal :-p

Then I don't get why you answered "no" for me patching GWT uiBinder even though you were saying:

"So let's move to PatchesWelcome as a signal that we're not opposed to enhancing UiBinder but it's not in the roadmap. What do you think?"

I didn't have the need to do that until now, but when this came I independently concluded to the same solution. Now when I tried, I figured out I cannot have an "outer" factory because GWT.create() needs to have a ClassName.class as a parameter, it cannot take a Class<T> clazz parameter since it cannot bind it to the real implementation on GWT compile (because the value would be a runtime value). So I had to keep the generator write the code GWT.create( TheWidget.class ), and I'm passing after that creation and some inits (xml specified css and handlers) to my own central init for all widgets. A subscription mechanism allows to subscribe for different kinds of patterns (widget class, widget context, and special widgets that implement an interface for a smarter @UiFactory fonctionality since the method receives an environement (connected user rules, application state, etc..) parameter and initializes against those values

--
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.