What is your future plan for GxtForms?

[Erol KOCAMAN]

What is your future plan for GxtForms?

Do you have any milestone? If so, can you share with us?

[David Durham]

No milestones planned. I have a page with features for the next release.

http://code.google.com/p/gxtforms/wiki/NextReleaseFeatures

The last 2 features on the list (but not the others) are implemented
and committed to svn.

-Dave

[gwtfanb0y]

Great that you don't have canceled this project, i am following it and
I'm curious about the next release.

[David Durham]

On Fri, Nov 27, 2009 at 11:55 AM, gwtfanb0y
<siegfri...@googlemail.com> wrote:
> Great that you don't have canceled this project, i am following it and
> I'm curious about the next release.

No plans to cancel, but I don't use GWT on a day to day basis any
more, so this is just a fun project for me. If anyone is interested
in stepping in with design and implementation ideas, please let me
know.

-Dave

[Erol KOCAMAN]

Hi,

I am developing GxtForms to entegrate relations between forms. For
example FormA has a relation on FormB with id. When you view FormA, a
combobox will be displayed. And you can select any FormB that are
created before. With this feature, GxtForms can be used to create
complex forms that have relations each other.

I am extending your GXTFormBuilder, FormServiceImpl, FormBeanImpl and
FormBeanImplAdapter classes.

On Nov 27, 8:04 pm, David Durham <david.durham...@gmail.com> wrote:
> On Fri, Nov 27, 2009 at 11:55 AM, gwtfanb0y
>

[David Durham]

On Mon, Nov 30, 2009 at 5:05 AM, Erol KOCAMAN <kocam...@gmail.com> wrote:
> I am developing GxtForms to entegrate relations between forms. For
> example FormA has a relation on FormB with id. When you view FormA, a
> combobox will be displayed. And you can select any FormB that are
> created before. With this feature, GxtForms can be used to create
> complex forms that have relations each other.

Ah yes. This is a problem I'm still thinking about. I need to dig
into this more and start working through some implementations, but
this is a very common task that this library should support.

Related to this problem is nested beans. So if you have, for
instance, a Person with an Address, where you want the user to fill in
firstname, lastname, ... and city, state, zip. A Person class could
look like:

Person {
String firstname;
String lastname;
Address home;
}

And you want a form from that with databinding. I plan to add this
for the 0.2 release.

This is also related to field sets. I'll go into more about this in
another email, but I think the issue you bring up is related to this
one and I'll discuss it more.

> I am extending your GXTFormBuilder, FormServiceImpl, FormBeanImpl and
> FormBeanImplAdapter classes.

It would be interesting to see what changes you made. Can you post an
svn diff file as a file attachment?

I did design these classes with extension in mind, but a better design
would take advantage of more composition-- components you could plugin
to fill different roles for creation of form configurations. You
probably already know this, what gets passed to the client is a
FormConfiguration which is generated from annotations, but it need not
be from annotations at all (could be form creation rules or components
or something .. just thinking out loud here). Annotations are fairly
convenient for working with models. I should put together a little
graphic of the form config process and post it on the wiki somewhere.

Thanks,

-Dave