Hi, thanks for the reply.
> A nit: we've tried to keep a convention of using lower case names for XML > elements that don't correspond to runtime objects, so <l:BoxLayoutData> should > probably be <l:boxLayoutData>. OK, I will do the required changes to keep the same convention. > If you want to get this out the door in the meantime, I'm afraid you'll have > to copy and paste UiBinderGenerator and UiBinderWriter, and provide some > gwt.xml magic to let your generator run instead of ours for GWT.create calls > on UiBinder.class. I tried to rename UiBinderGenerator and UiBinderWriter but there is a problem with the ElementParser.parse(XMLElement elem, String fieldName, JClassType type, UiBinderWriter writer) it requires a UiBinderWriter. Extending UiBinderWriter is also not possible since all register methods are private. > Another alternative is to do some classpath cheating. Patch UiBinderWriter > to register your parsers, and put your version in the Mosaic jar. If your > users put your jar in the classpath before gwt's, you should be good to go. Maybe I keep this for simplicity. This is what I do so far. Can I post a patch for GWT-2.1 as a temporary solution, that allows registration of custom handlers, until you provide a final API for UiBinder generator? Thanks, George.
-- http://groups.google.com/group/Google-Web-Toolkit-Contributors
