Ability to "wire" a set of related many entities in the data binding declaration.
For example, an Account entity. An Account has a set of related many AccountAddress entities. The data-binding framework should be able to "map" these AccountAddress entities to a set of nested form control "groups" represented in say a TabbedWidget. Moreover, the ability to add/remove such "child" entities is assumed. This is a common use-case that deserves first class support as opposed to only providing a "monolithic" mapping strategy. I think a good data-binding modeling strategy is in the gwittr framework: http://code.google.com/p/gwittir/wiki/Binding my 2 cents, Jon On Dec 16, 9:01 am, Bruce Johnson <[email protected]> wrote: > Working on a draft one. > > What do folks here think is important? > > > > On Wed, Dec 16, 2009 at 7:42 AM, tfreitas <[email protected]> wrote: > > What about roadmap? > > > -- > >http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
