Ok, then we'll need to be pretty clear about that in the documentation, because it's a pretty serious landmine (i.e., in that existing projects could easily have some widgets that couldn't be directly used with UiBinder without hackery). As an example, I'm going to have to add some parsers for LayoutPanel, et al, because they have somewhat unusual construction semantics.
On Tue, Aug 4, 2009 at 3:31 PM, Ray Ryan <rj...@google.com> wrote: > I was thinking 2.1, actually. > > > On Tue, Aug 4, 2009 at 12:31 PM, <j...@google.com> wrote: > >> On 2009/08/04 18:50:55, Ray Ryan wrote: >> >>> On 2009/08/04 17:44:38, Ray Ryan wrote: >>> > >>> >> >> A question for the group: the stuff under rebind and parsers should >>> >> not be >> >>> considered public API, it's just not ready for that. Is javadoc to >>> >> that effect >> >>> enough of a deterrent? (Although I suppose the fact that you can't >>> >> actually make >> >>> your own parsers and such *do* anything yet will make the issue moot.) >>> >> >> I would assume that if you can't usefully write your own yet, then it's >> pretty safe to keep evolving the API. I assume that there's a >> 2.0-time-frame task to make a public API for parsers? >> >> >> http://gwt-code-reviews.appspot.com/51831 >> > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
