Brainstorm: UIBinder + model binding + validation

[Maarten Volders]

Hi boys and girls,

I really like the new UIBinder, but perhaps we can take it one step
further? Why not try to bind the model directly to the ui fields and
visa versa? That way we would eliminate a bunch of boilerplate code.
There have been several attempts binding models to ui elements (before
uibinder) but it seems extending uibinder seems to make sense. Some
quick thoughts:

- bind model to UIBinder
- get / set data solved by generators
- add validation annotations to the model which are triggered by the
framework

Some questions about UIBinder:

- do we always need to declare the @UiField? Let's say we have a
typical crud app, we could also just annotate the model.Having the
uifield declared and also the model fields seems often code
duplication, I like the DDD approach a bit more.
- really like the layout part of uibinder, have been on too many
projects where we really need ui designers, but I would still prefer
to talk the same language (DDD) otherwise ui designers talk about
field names they know on the screen and devs talk about the model
field names. Have this seen happening way too often :-)

What you guys think?

Maarten