That's what I figured :)
On Tuesday, June 3, 2014 4:22:57 AM UTC-4, Thomas Broyer wrote:
I've been contemplating other avenues of UI generation, like HTMLPanel. I've tried using a JSP to generate a block of HTML dynamically, usually including looping, and retrieve that using RequestBuilder, and putting that into an HTMLPanel. The only difficult part is managing the id's of various elements. And of course, having half the code in src, and the other half under war - but I could use a generator class under src to get around that.
It seems that a dynamic version of UiBinder or UiRenderer would be possible, since GWT has client runtime XML processing capabilities. And the set of available tags could be expanded to include some analogs to the
JSP core tags, like c:forEach. The Java class would have to be created in advance, so either there would need to be fields for all possible widgets, with nulls legal, or the widgets could be entries in a map instead of class properties. Widgets resulting from a loop would be in an array or List. Maybe someday in my copious free time, I'll play around with that.
-- On Tuesday, June 3, 2014 4:22:57 AM UTC-4, Thomas Broyer wrote:
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" ;-)
I've been contemplating other avenues of UI generation, like HTMLPanel. I've tried using a JSP to generate a block of HTML dynamically, usually including looping, and retrieve that using RequestBuilder, and putting that into an HTMLPanel. The only difficult part is managing the id's of various elements. And of course, having half the code in src, and the other half under war - but I could use a generator class under src to get around that.
It seems that a dynamic version of UiBinder or UiRenderer would be possible, since GWT has client runtime XML processing capabilities. And the set of available tags could be expanded to include some analogs to the
JSP core tags, like c:forEach. The Java class would have to be created in advance, so either there would need to be fields for all possible widgets, with nulls legal, or the widgets could be entries in a map instead of class properties. Widgets resulting from a loop would be in an array or List. Maybe someday in my copious free time, I'll play around with that.
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.
No comments:
Post a Comment