As soon as we have done that, we can't make changes to UiBinderWriter and all the other classes the parsers actually talk to, nor can we make sweeping changes to the code they generate.
If the problem is retrofitting widgets you don't own, would a non-annotation alternative to UiChild get the job done? Perhaps a config file, perhaps a builder of some kind? On Thu, Jun 9, 2011 at 8:16 PM, <jus...@jhickman.com> wrote: > Unfortunately @UiChild doesn't handle the flexibility I need, especially > in cases where you are wanting to write parsers for a 3rd party widget > library and do not have the ability to modify the source to include > annotations. > > Is there any way of convincing you to make it more extendable? Even > without providing an "official" mechanism for registering > ElementParsers, doing small things such as the following would do > wonders: > > * In UiBinderGenerator, extract the instantiation of the UiBinderWriter > into a protected method so that developers can subclass the > UiBinderGenerator and construct their own subclass of UiBinderWriter > > * In UiBinderWriter, make addElementParser() protected rather than > private. > > > > > http://gwt-code-reviews.**appspot.com/1454804/<http://gwt-code-reviews.appspot.com/1454804/> > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
