Let's discuss about the Grails Form Builder Plugin Architecture

[limcheekin]

Hi,

We welcome you to join this discussion!

Please go to link below for detail of initial Grails Form Builder
Plugin Architecture:
https://docs.google.com/document/edit?id=1RcSV2xVm4MXA85GUk7_7x8W_GpA9-g3J9AJUDAgKCUE&hl=en&authkey=CJbw0MUM

Your feedback is very important to us and very much appreciated.
Please tell us what is in your mind!

Thanks.

Regards,
Chee Kin

[Juri Kuehn]

Looks great, looking forward to it!

On Oct 13, 5:22 am, limcheekin <limchee...@vobject.com> wrote:
> Hi,
>
> We welcome you to join this discussion!
>
> Please go to link below for detail of initial Grails Form Builder

> Plugin Architecture:https://docs.google.com/document/edit?id=1RcSV2xVm4MXA85GUk7_7x8W_GpA...

[virtualeyes]

Chee,

excellent idea. Question, how will you handle select lists and multi
option checkbox/radio button elements. The JQuery/TinyMCE formbuilder
seems to take manually entered input to populate option values. For
end users this may make sense, but for developers, not so much, no?
Won't we want to programmatically populate these elements, not to
mention style, position, apply JS attributes, etc.?

Basically, the utility as I see it is in the dynamic domain model +
tagging domain properties with formfield attributes and storing in DB
for later form creation.

The Jquery formbuilder looks excellent, don't get me wrong, just
wondering if it might get in the way or restrict Grails developers on
the coding end.

Will be fun to find out ;--)

On Oct 13, 5:22 am, limcheekin <limchee...@vobject.com> wrote:

> Hi,
>
> We welcome you to join this discussion!
>
> Please go to link below for detail of initial Grails Form Builder

> Plugin Architecture:https://docs.google.com/document/edit?id=1RcSV2xVm4MXA85GUk7_7x8W_GpA...

[Chee Kin Lim]

Hi there,

Thanks for writing.

Multiple options will be created based on manual user input or pull from database, but I think not to the extend support programmatically population. Bear in mind that the form builder plugin is mainly for user instead of developer. Well, the code will be released as Apache license, developers can customized the plugin for their project-specific requirements.

I am actively looking for developers to work out the plugin together, would you be interested?

Fyi, the project will be hosted at http://code.google.com/p/grails-form-builder-plugin/

Wish to hear from you soon!

Regards,
Chee Kin

[virtualeyes]

Chee, Hi.

GSPs basically make me ill, I refuse to type <g:input blah blah> when
this code can be auto-generated (and manipulated pre-generation unlike
scaffolding), thus leaving the programmer to focus on programming, not
wasting time manually typing out domain properties as formfields.

Your idea is very good, great interface, but the implementation is not
what I'm looking for. If we define a select list called "country", we
should be able to dynamically populate that list on form generation
via grails. We should also be able to relate the country select list
to multiple domains. Finally, a given formfield should have
permissions attached to it, so an "expired" boolean radio button flag
would display to an administrator, but not a site subscriber, for
example.

In the end, I'd like to see a developer's form builder. The gold here
is in the dynamic domain model, IMO. With that, we get around compile-
time frustration and can add an admin GUI to map domain properties to
formfield attribs with drag & drop, huge time saver.

On Oct 19, 4:14 am, Chee Kin Lim <limchee...@vobject.com> wrote:
> Hi there,
>
> Thanks for writing.
>
> Multiple options will be created based on manual user input or pull from
> database, but I think not to the extend support programmatically population.
> Bear in mind that the form builder plugin is mainly for user instead of
> developer. Well, the code will be released as Apache license, developers can
> customized the plugin for their project-specific requirements.
>
> I am actively looking for developers to work out the plugin together, would
> you be interested?
>

> Fyi, the project will be hosted athttp://code.google.com/p/grails-form-builder-plugin/

[Chee Kin Lim]

Hi there,

I think we are talking to the same idea. I am developer too! The domain properties will be mapped to the form field using the form builder. Hm..., I should said the form builder will define the domain properties and constraints. IMO, permission control is not in the scope of form builder plugin.

By the way, I just release an interesting Dynamic Domain Class Plugin 0.1 at http://code.google.com/p/grails-dynamic-domain-class-plugin/.

Any idea how to solve the known issue?

Please advice.

Regards,
Chee Kin

[virtualeyes]

Chee,

right, I know you are a developer ;--)

Agreed, permissions are not in the scope of proposed formbuilder.

I have no idea where that dynamic domain error is coming from, but is
a problem obviously, I am running Tomcat like many others. Given that
Beckwith came up with the dynamic domain grails add-on, he probably
knows better than anyone else.

On Oct 19, 1:34 pm, Chee Kin Lim <limchee...@vobject.com> wrote:
> Hi there,
>

> I think we are talking to the same idea. I am developer too! The domain
> properties will be mapped to the form field using the form builder. Hm..., I
> should said the form builder will define the domain properties and
> constraints. IMO, permission control is not in the scope of form builder
> plugin.
>

> By the way, I just release an interesting Dynamic Domain Class Plugin 0.1 athttp://code.google.com/p/grails-dynamic-domain-class-plugin/.

[Chee Kin Lim]

Hi there,

Updated architecture document of the plugin for your reference at http://code.google.com/p/grails-form-builder-plugin/wiki/Architecture

What do you think about it? 

Regards,

Chee Kin