UiBinder etc.

[wen]

I've been thinking about the same thing for a long time. It's great
that you've put it in action for GXT.

For our internal app using servlet and plain js, I've done something
similar to very good success. It'd be cool if I can contribute to your
effort so we can all move it forward quickly.

On a very high level note, have you though about uiBinder and whether
it can be used as the intermediate for the purpose of this framework.
It may make sense to do,

annotated POJO --> uiBinder XML --> form configuration --> GXT form

I'm not very fluent with GWT 2.0. However uiBinder seems to strive for
the similar goal, though not as far, as this framework.

The other question is about the POJO annotation. In my app, I used:
http://code.google.com/p/floxs/source/browse/trunk/HnD/src/org/sucri/floxs/model/Accesor.java

for the getter and setter. Instead of on the variables directly.

Thanks

[David Durham]

On Wed, Nov 11, 2009 at 10:49 AM, wen <wyu....@gmail.com> wrote:
>
> I've been thinking about the same thing for a long time. It's great
> that you've put it in action for GXT.

Thanks. I sincerely appreciate your feedback.

> For our internal app using servlet and plain js, I've done something
> similar to very good success. It'd be cool if I can contribute to your
> effort so we can all move it forward quickly.

There's a list of the proposed features here:
http://code.google.com/p/gxtforms/wiki/NextReleaseFeatures

The wiki page is a bit light on details. Perhaps I should cut and
paste detailed discussions from this group onto it.

> On a very high level note, have you though about uiBinder and whether
> it can be used as the intermediate for the purpose of this framework.
> It may make sense to do,
>
> annotated POJO --> uiBinder XML --> form configuration --> GXT form

Excellent idea. I'd have to change the name from gxtforms to
something else.. gwtforms perhaps, with gxt being just one of the
options. Thanks.

> I'm not very fluent with GWT 2.0. However uiBinder seems to strive for
> the similar goal, though not as far, as this framework.

I'm not fluent with it either .. perhaps this is a particularly good
place for you to contribute. The backend processing pretty straight
forward. It's all in the 'server..' packages. We can talk about this
more if you have some ideas.

> The other question is about the POJO annotation. In my app, I used:
> http://code.google.com/p/floxs/source/browse/trunk/HnD/src/org/sucri/floxs/model/Accesor.java
>
> for the getter and setter. Instead of on the variables directly.

I like annotating the fields because, for instance, groovy doesn't
even require that you write getters and setters. Getters and setters,
in my opinion, are just are just silly formality in Java that will
hopefully go away (in the sense that they should be optional for the
case of you need something other than simple assignment).

-Dave