Re: [announce] BeanForm 0.4
Hi Daniel, Have you thought about a "view" mode recently? Instead of adding more parameters, how about checking if save and delete have been specified - if they haven't, then make all the properties output-only? To me, the ability to get a bean displayed without fuss is as valuable to me as being able to edit it. Geoff On 14/09/2006, at 12:16 PM, D&J Gredler wrote: I think the "exclude" parameter sounds like a good idea, it would probably be very useful for prototyping or admin screens where you're more worried about your time than property display order. The edit vs view toggle I'm not so sure about, mainly because I want to make sure the component stays relatively lean and the API doesn't get too cluttered. For example, a user recently requested a way to make all read-only properties use an Insert component, rather than the current behavior of disabling the input component they receive. In the end, rather than add a new parameter to BeanForm, I decided to make it easier to override the input component used for specific properties, and to make the Insert component one of the options. It's a little harder for his specific needs, as he has to list his bean properties and assign Insert components to the read-only properties, but it's a generic solution that's "easy enough" for him and doesn't force other people to learn another corner case when they're first grokking the BeanForm API. Of course, I may be underestimating the usefulness of this feature, in which case it's not a "corner case" at all :-) My gut reaction is that the generic solution described above is also "good enough" for edit vs view toggling. You would have to list the properties to display, but you could say: properties="literal:name=Insert,description=Insert,comment=Insert,date Created=Insert" ... /> In the same vein I can see the title feature being useful, but I would want to make it optional, which means Yet Another Parameter (YAP?). Of course, a more generic solution would be to allow the user to dynamically contribute bindings to some or all of the property input components. Now *that* would float my boat. But how? Anyway, those are my [longish] thoughts. Feel free to disagree. Daniel PS - Martin, would you have time to send me a patch implementing the "exclude" parameter? ;-) If not, I'll probably look at it eventually. On 9/14/06, andyhot <[EMAIL PROTECTED]> wrote: Martin Strand wrote: > Thanks. > I just added a few minor things, nothing big: > - "exclude" parameter to exclude properties rather than specifying > which ones should be included > - toggle between "edit" mode and "view" mode (view mode = no form > components) Both look useful. Perhaps they could get included? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
Apache license, version 2
On 9/14/06, Mark Stang <[EMAIL PROTECTED]> wrote:
BTW, what is the license for this component?
thanks,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: Martin Strand [mailto:[EMAIL PROTECTED]
Sent: Wed 9/13/2006 5:06 PM
To: Tapestry users
Subject: Re: [announce] BeanForm 0.4
Nice work! :)
I was actually just working on my own beanform when I came across yours
about two weeks ago. Now I use yours instead, I just subclassed it to add
a few app specific features.
Do you have a public svn repo somewhere?
Martin
On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I have just released the latest version of BeanForm, a single-line POJO
> editor component:
>
> span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
> delete="listener:delete"
>
> The above line of code gets you a form that:
>
> * calls your page's save() method when submitted for save
> * calls your page's delete() method when submitted for delete
> * gives you a TextField for each of the bean's string and numerical
> properties
> * gives you a Checkbox for each of the bean's boolean properties
> * gives you a DatePicker for each of the bean's date properties
> * automatically disables fields for read-only properties
>
> If you are using Java Persistence API (EJB3) annotations and/or
Hibernate
> Validator annotations, the BeanForm component also:
>
> * infers validation strings for annotated properties
> * uses TextAreas instead of TextFields for annotated string
> properties
> whose maximum length is over 255 characters
>
> Some other important features:
>
> * EJB3 and Hibernate Validator support is optional and enabled
> automatically at runtime only when appropriate
> * you can use a BeanForm inside a Form component, in which case the
> BeanForm will not emit a second form tag
> * you can explicitly specify which properties to display, as well as
> their validation strings
> * when specifying properties explicitly, they may be recursive ("
> person.address.city.name", for example)
> * you can override the input components used to edit properties
> * support for canceling and refreshing forms
> * support for localization
>
> Starting with version 0.4, BeanForm should work with both Tapestry 4.0
> and
> Tapestry 4.1.
> I should also note that starting with version 0.4, BeanForm requires the
> tapestry-prop library, available at
>
http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
> .
>
> Give it a whirl and let me know if you have any problems, comments or
> suggestions.
>
> Take care,
>
> Daniel Gredler
>
>
> Homepage: http://beanform.sourceforge.net/
> Component Reference:
> http://beanform.sourceforge.net/component-reference.html
> Change History: http://beanform.sourceforge.net/changes-report.html
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
Sorry, no.
It was semi-interesting trying to achieve compatibility with both 4.0 and
4.1... Maintaining compatibility with all 3 versions would probably be nigh
impossible.
Of course, nothing stops you from forking a Tap3 version :-)
On 9/14/06, Mark Stang <[EMAIL PROTECTED]> wrote:
I don't suppose there is a version for 3.x?
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Wed 9/13/2006 8:10 PM
To: Tapestry users
Subject: Re: [announce] BeanForm 0.4
Oops...I've fixed that now. BeanForm should show up linked in directly
from
the main site whenever the apache servers sync up.
On 9/13/06, Martin Strand <[EMAIL PROTECTED]> wrote:
>
> Nice work! :)
> I was actually just working on my own beanform when I came across yours
> about two weeks ago. Now I use yours instead, I just subclassed it to
add
> a few app specific features.
> Do you have a public svn repo somewhere?
>
> Martin
>
> On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
> wrote:
>
> > Hi all,
> >
> > I have just released the latest version of BeanForm, a single-line
POJO
> > editor component:
> >
> > span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
> > delete="listener:delete"
> >
> > The above line of code gets you a form that:
> >
> > * calls your page's save() method when submitted for save
> > * calls your page's delete() method when submitted for delete
> > * gives you a TextField for each of the bean's string and
numerical
> > properties
> > * gives you a Checkbox for each of the bean's boolean properties
> > * gives you a DatePicker for each of the bean's date properties
> > * automatically disables fields for read-only properties
> >
> > If you are using Java Persistence API (EJB3) annotations and/or
> Hibernate
> > Validator annotations, the BeanForm component also:
> >
> > * infers validation strings for annotated properties
> > * uses TextAreas instead of TextFields for annotated string
> > properties
> > whose maximum length is over 255 characters
> >
> > Some other important features:
> >
> > * EJB3 and Hibernate Validator support is optional and enabled
> > automatically at runtime only when appropriate
> > * you can use a BeanForm inside a Form component, in which case
the
> > BeanForm will not emit a second form tag
> > * you can explicitly specify which properties to display, as well
as
> > their validation strings
> > * when specifying properties explicitly, they may be recursive ("
> > person.address.city.name", for example)
> > * you can override the input components used to edit properties
> > * support for canceling and refreshing forms
> > * support for localization
> >
> > Starting with version 0.4, BeanForm should work with both Tapestry 4.0
> > and
> > Tapestry 4.1.
> > I should also note that starting with version 0.4, BeanForm requires
the
> > tapestry-prop library, available at
> >
>
http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
> > .
> >
> > Give it a whirl and let me know if you have any problems, comments or
> > suggestions.
> >
> > Take care,
> >
> > Daniel Gredler
> >
> >
> > Homepage: http://beanform.sourceforge.net/
> > Component Reference:
> > http://beanform.sourceforge.net/component-reference.html
> > Change History: http://beanform.sourceforge.net/changes-report.html
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: [announce] BeanForm 0.4
I think the current functionality is correct. If it's in a form it works and if not it supplies it's own form. This makes is much easier to put up a quick page to edit an object then go back later and make things pretty. If this functionality is difficult to implement I think it would be OK to have a form parameter that defaults to true. If you set it to false then you have to provide your own form. BTW: I think beanform and table are my most used tapestry components. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [announce] BeanForm 0.4
BTW, what is the license for this component?
thanks,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: Martin Strand [mailto:[EMAIL PROTECTED]
Sent: Wed 9/13/2006 5:06 PM
To: Tapestry users
Subject: Re: [announce] BeanForm 0.4
Nice work! :)
I was actually just working on my own beanform when I came across yours
about two weeks ago. Now I use yours instead, I just subclassed it to add
a few app specific features.
Do you have a public svn repo somewhere?
Martin
On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I have just released the latest version of BeanForm, a single-line POJO
> editor component:
>
> span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
> delete="listener:delete"
>
> The above line of code gets you a form that:
>
> * calls your page's save() method when submitted for save
> * calls your page's delete() method when submitted for delete
> * gives you a TextField for each of the bean's string and numerical
> properties
> * gives you a Checkbox for each of the bean's boolean properties
> * gives you a DatePicker for each of the bean's date properties
> * automatically disables fields for read-only properties
>
> If you are using Java Persistence API (EJB3) annotations and/or Hibernate
> Validator annotations, the BeanForm component also:
>
> * infers validation strings for annotated properties
> * uses TextAreas instead of TextFields for annotated string
> properties
> whose maximum length is over 255 characters
>
> Some other important features:
>
> * EJB3 and Hibernate Validator support is optional and enabled
> automatically at runtime only when appropriate
> * you can use a BeanForm inside a Form component, in which case the
> BeanForm will not emit a second form tag
> * you can explicitly specify which properties to display, as well as
> their validation strings
> * when specifying properties explicitly, they may be recursive ("
> person.address.city.name", for example)
> * you can override the input components used to edit properties
> * support for canceling and refreshing forms
> * support for localization
>
> Starting with version 0.4, BeanForm should work with both Tapestry 4.0
> and
> Tapestry 4.1.
> I should also note that starting with version 0.4, BeanForm requires the
> tapestry-prop library, available at
> http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
> .
>
> Give it a whirl and let me know if you have any problems, comments or
> suggestions.
>
> Take care,
>
> Daniel Gredler
>
>
> Homepage: http://beanform.sourceforge.net/
> Component Reference:
> http://beanform.sourceforge.net/component-reference.html
> Change History: http://beanform.sourceforge.net/changes-report.html
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [announce] BeanForm 0.4
I don't suppose there is a version for 3.x?
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-Original Message-
From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: Wed 9/13/2006 8:10 PM
To: Tapestry users
Subject: Re: [announce] BeanForm 0.4
Oops...I've fixed that now. BeanForm should show up linked in directly from
the main site whenever the apache servers sync up.
On 9/13/06, Martin Strand <[EMAIL PROTECTED]> wrote:
>
> Nice work! :)
> I was actually just working on my own beanform when I came across yours
> about two weeks ago. Now I use yours instead, I just subclassed it to add
> a few app specific features.
> Do you have a public svn repo somewhere?
>
> Martin
>
> On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
> wrote:
>
> > Hi all,
> >
> > I have just released the latest version of BeanForm, a single-line POJO
> > editor component:
> >
> > span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
> > delete="listener:delete"
> >
> > The above line of code gets you a form that:
> >
> > * calls your page's save() method when submitted for save
> > * calls your page's delete() method when submitted for delete
> > * gives you a TextField for each of the bean's string and numerical
> > properties
> > * gives you a Checkbox for each of the bean's boolean properties
> > * gives you a DatePicker for each of the bean's date properties
> > * automatically disables fields for read-only properties
> >
> > If you are using Java Persistence API (EJB3) annotations and/or
> Hibernate
> > Validator annotations, the BeanForm component also:
> >
> > * infers validation strings for annotated properties
> > * uses TextAreas instead of TextFields for annotated string
> > properties
> > whose maximum length is over 255 characters
> >
> > Some other important features:
> >
> > * EJB3 and Hibernate Validator support is optional and enabled
> > automatically at runtime only when appropriate
> > * you can use a BeanForm inside a Form component, in which case the
> > BeanForm will not emit a second form tag
> > * you can explicitly specify which properties to display, as well as
> > their validation strings
> > * when specifying properties explicitly, they may be recursive ("
> > person.address.city.name", for example)
> > * you can override the input components used to edit properties
> > * support for canceling and refreshing forms
> > * support for localization
> >
> > Starting with version 0.4, BeanForm should work with both Tapestry 4.0
> > and
> > Tapestry 4.1.
> > I should also note that starting with version 0.4, BeanForm requires the
> > tapestry-prop library, available at
> >
> http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
> > .
> >
> > Give it a whirl and let me know if you have any problems, comments or
> > suggestions.
> >
> > Take care,
> >
> > Daniel Gredler
> >
> >
> > Homepage: http://beanform.sourceforge.net/
> > Component Reference:
> > http://beanform.sourceforge.net/component-reference.html
> > Change History: http://beanform.sourceforge.net/changes-report.html
> >
> >
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: [announce] BeanForm 0.4
I've been toying with the idea of removing the Form functionality (it certainly would simplify some stuff!). If I remember correctly, one of Jesse's initial reactions was also that it should just require the user to wrap it in an external Form component. Does anyone else have an opinion on this? Please speak up! On 9/14/06, Martin Strand <[EMAIL PROTECTED]> wrote: Yeah, I think it's a good idea to keep the BeanForm as simple as possible and let people with specific needs (me) subclass it to add new features. I also think you should remove the Form parameters and leave it to the user to enclose the component with a Form. Or at least break out the editor part into a "BeanEditor" component. The BeanForm would then include a BeanEditor and a few buttons and people who want to use it in an existing form would just use the BeanEditor directly instead. Martin On Thu, 14 Sep 2006 04:16:05 +0200, D&J Gredler <[EMAIL PROTECTED]> wrote: > I think the "exclude" parameter sounds like a good idea, it would probably > be very useful for prototyping or admin screens where you're more worried > about your time than property display order. > > The edit vs view toggle I'm not so sure about, mainly because I want to make > sure the component stays relatively lean and the API doesn't get too > cluttered. For example, a user recently requested a way to make all > read-only properties use an Insert component, rather than the current > behavior of disabling the input component they receive. In the end, rather > than add a new parameter to BeanForm, I decided to make it easier to > override the input component used for specific properties, and to make the > Insert component one of the options. It's a little harder for his specific > needs, as he has to list his bean properties and assign Insert components to > the read-only properties, but it's a generic solution that's "easy enough" > for him and doesn't force other people to learn another corner case when > they're first grokking the BeanForm API. Of course, I may be underestimating > the usefulness of this feature, in which case it's not a "corner case" at > all :-) > > My gut reaction is that the generic solution described above is also "good > enough" for edit vs view toggling. You would have to list the properties to > display, but you could say: > > properties="literal:name=Insert,description=Insert,comment=Insert,dateCreated=Insert" > ... /> > > In the same vein I can see the title feature being useful, but I would want > to make it optional, which means Yet Another Parameter (YAP?). Of course, a > more generic solution would be to allow the user to dynamically contribute > bindings to some or all of the property input components. Now *that* would > float my boat. But how? > > Anyway, those are my [longish] thoughts. Feel free to disagree. > > Daniel > > > PS - Martin, would you have time to send me a patch implementing the > "exclude" parameter? ;-) If not, I'll probably look at it eventually. > > > On 9/14/06, andyhot <[EMAIL PROTECTED]> wrote: >> >> Martin Strand wrote: >> > Thanks. >> > I just added a few minor things, nothing big: >> > - "exclude" parameter to exclude properties rather than specifying >> > which ones should be included >> > - toggle between "edit" mode and "view" mode (view mode = no form >> > components) >> Both look useful. Perhaps they could get included? >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
Yeah, I think it's a good idea to keep the BeanForm as simple as possible and let people with specific needs (me) subclass it to add new features. I also think you should remove the Form parameters and leave it to the user to enclose the component with a Form. Or at least break out the editor part into a "BeanEditor" component. The BeanForm would then include a BeanEditor and a few buttons and people who want to use it in an existing form would just use the BeanEditor directly instead. Martin On Thu, 14 Sep 2006 04:16:05 +0200, D&J Gredler <[EMAIL PROTECTED]> wrote: > I think the "exclude" parameter sounds like a good idea, it would probably > be very useful for prototyping or admin screens where you're more worried > about your time than property display order. > > The edit vs view toggle I'm not so sure about, mainly because I want to make > sure the component stays relatively lean and the API doesn't get too > cluttered. For example, a user recently requested a way to make all > read-only properties use an Insert component, rather than the current > behavior of disabling the input component they receive. In the end, rather > than add a new parameter to BeanForm, I decided to make it easier to > override the input component used for specific properties, and to make the > Insert component one of the options. It's a little harder for his specific > needs, as he has to list his bean properties and assign Insert components to > the read-only properties, but it's a generic solution that's "easy enough" > for him and doesn't force other people to learn another corner case when > they're first grokking the BeanForm API. Of course, I may be underestimating > the usefulness of this feature, in which case it's not a "corner case" at > all :-) > > My gut reaction is that the generic solution described above is also "good > enough" for edit vs view toggling. You would have to list the properties to > display, but you could say: > > properties="literal:name=Insert,description=Insert,comment=Insert,dateCreated=Insert" > ... /> > > In the same vein I can see the title feature being useful, but I would want > to make it optional, which means Yet Another Parameter (YAP?). Of course, a > more generic solution would be to allow the user to dynamically contribute > bindings to some or all of the property input components. Now *that* would > float my boat. But how? > > Anyway, those are my [longish] thoughts. Feel free to disagree. > > Daniel > > > PS - Martin, would you have time to send me a patch implementing the > "exclude" parameter? ;-) If not, I'll probably look at it eventually. > > > On 9/14/06, andyhot <[EMAIL PROTECTED]> wrote: >> >> Martin Strand wrote: >> > Thanks. >> > I just added a few minor things, nothing big: >> > - "exclude" parameter to exclude properties rather than specifying >> > which ones should be included >> > - toggle between "edit" mode and "view" mode (view mode = no form >> > components) >> Both look useful. Perhaps they could get included? >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
I think the "exclude" parameter sounds like a good idea, it would probably be very useful for prototyping or admin screens where you're more worried about your time than property display order. The edit vs view toggle I'm not so sure about, mainly because I want to make sure the component stays relatively lean and the API doesn't get too cluttered. For example, a user recently requested a way to make all read-only properties use an Insert component, rather than the current behavior of disabling the input component they receive. In the end, rather than add a new parameter to BeanForm, I decided to make it easier to override the input component used for specific properties, and to make the Insert component one of the options. It's a little harder for his specific needs, as he has to list his bean properties and assign Insert components to the read-only properties, but it's a generic solution that's "easy enough" for him and doesn't force other people to learn another corner case when they're first grokking the BeanForm API. Of course, I may be underestimating the usefulness of this feature, in which case it's not a "corner case" at all :-) My gut reaction is that the generic solution described above is also "good enough" for edit vs view toggling. You would have to list the properties to display, but you could say: In the same vein I can see the title feature being useful, but I would want to make it optional, which means Yet Another Parameter (YAP?). Of course, a more generic solution would be to allow the user to dynamically contribute bindings to some or all of the property input components. Now *that* would float my boat. But how? Anyway, those are my [longish] thoughts. Feel free to disagree. Daniel PS - Martin, would you have time to send me a patch implementing the "exclude" parameter? ;-) If not, I'll probably look at it eventually. On 9/14/06, andyhot <[EMAIL PROTECTED]> wrote: Martin Strand wrote: > Thanks. > I just added a few minor things, nothing big: > - "exclude" parameter to exclude properties rather than specifying > which ones should be included > - toggle between "edit" mode and "view" mode (view mode = no form > components) Both look useful. Perhaps they could get included? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
Oops...I've fixed that now. BeanForm should show up linked in directly from
the main site whenever the apache servers sync up.
On 9/13/06, Martin Strand <[EMAIL PROTECTED]> wrote:
Nice work! :)
I was actually just working on my own beanform when I came across yours
about two weeks ago. Now I use yours instead, I just subclassed it to add
a few app specific features.
Do you have a public svn repo somewhere?
Martin
On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I have just released the latest version of BeanForm, a single-line POJO
> editor component:
>
> span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
> delete="listener:delete"
>
> The above line of code gets you a form that:
>
> * calls your page's save() method when submitted for save
> * calls your page's delete() method when submitted for delete
> * gives you a TextField for each of the bean's string and numerical
> properties
> * gives you a Checkbox for each of the bean's boolean properties
> * gives you a DatePicker for each of the bean's date properties
> * automatically disables fields for read-only properties
>
> If you are using Java Persistence API (EJB3) annotations and/or
Hibernate
> Validator annotations, the BeanForm component also:
>
> * infers validation strings for annotated properties
> * uses TextAreas instead of TextFields for annotated string
> properties
> whose maximum length is over 255 characters
>
> Some other important features:
>
> * EJB3 and Hibernate Validator support is optional and enabled
> automatically at runtime only when appropriate
> * you can use a BeanForm inside a Form component, in which case the
> BeanForm will not emit a second form tag
> * you can explicitly specify which properties to display, as well as
> their validation strings
> * when specifying properties explicitly, they may be recursive ("
> person.address.city.name", for example)
> * you can override the input components used to edit properties
> * support for canceling and refreshing forms
> * support for localization
>
> Starting with version 0.4, BeanForm should work with both Tapestry 4.0
> and
> Tapestry 4.1.
> I should also note that starting with version 0.4, BeanForm requires the
> tapestry-prop library, available at
>
http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
> .
>
> Give it a whirl and let me know if you have any problems, comments or
> suggestions.
>
> Take care,
>
> Daniel Gredler
>
>
> Homepage: http://beanform.sourceforge.net/
> Component Reference:
> http://beanform.sourceforge.net/component-reference.html
> Change History: http://beanform.sourceforge.net/changes-report.html
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: [announce] BeanForm 0.4
Martin Strand wrote: > Thanks. > I just added a few minor things, nothing big: > - "exclude" parameter to exclude properties rather than specifying > which ones should be included > - toggle between "edit" mode and "view" mode (view mode = no form > components) Both look useful. Perhaps they could get included? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
Thanks.
I just added a few minor things, nothing big:
- "exclude" parameter to exclude properties rather than specifying which
ones should be included
- toggle between "edit" mode and "view" mode (view mode = no form
components)
- a few extra editor components and clever defaults specific to my app
One thing I thought of, it would be neat to be able to bind the "title"
attribute for all form components to "message:{propertyName}.title".
Martin
On Thu, 14 Sep 2006 01:29:14 +0200, D&J Gredler <[EMAIL PROTECTED]>
wrote:
The project is hosted on sourceforge, so I'm using their CVS (see
http://sourceforge.net/cvs/?group_id=171323, or browse it online at
http://beanform.cvs.sourceforge.net/beanform/).
What features have you added? Anything that could be useful to others?
Daniel
On 9/14/06, Martin Strand <[EMAIL PROTECTED]> wrote:
Nice work! :)
I was actually just working on my own beanform when I came across yours
about two weeks ago. Now I use yours instead, I just subclassed it to
add
a few app specific features.
Do you have a public svn repo somewhere?
Martin
On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I have just released the latest version of BeanForm, a single-line
POJO
> editor component:
>
> span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
> delete="listener:delete"
>
> The above line of code gets you a form that:
>
> * calls your page's save() method when submitted for save
> * calls your page's delete() method when submitted for delete
> * gives you a TextField for each of the bean's string and
numerical
> properties
> * gives you a Checkbox for each of the bean's boolean properties
> * gives you a DatePicker for each of the bean's date properties
> * automatically disables fields for read-only properties
>
> If you are using Java Persistence API (EJB3) annotations and/or
Hibernate
> Validator annotations, the BeanForm component also:
>
> * infers validation strings for annotated properties
> * uses TextAreas instead of TextFields for annotated string
> properties
> whose maximum length is over 255 characters
>
> Some other important features:
>
> * EJB3 and Hibernate Validator support is optional and enabled
> automatically at runtime only when appropriate
> * you can use a BeanForm inside a Form component, in which case
the
> BeanForm will not emit a second form tag
> * you can explicitly specify which properties to display, as well
as
> their validation strings
> * when specifying properties explicitly, they may be recursive ("
> person.address.city.name", for example)
> * you can override the input components used to edit properties
> * support for canceling and refreshing forms
> * support for localization
>
> Starting with version 0.4, BeanForm should work with both Tapestry 4.0
> and
> Tapestry 4.1.
> I should also note that starting with version 0.4, BeanForm requires
the
> tapestry-prop library, available at
>
http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
> .
>
> Give it a whirl and let me know if you have any problems, comments or
> suggestions.
>
> Take care,
>
> Daniel Gredler
>
>
> Homepage: http://beanform.sourceforge.net/
> Component Reference:
> http://beanform.sourceforge.net/component-reference.html
> Change History: http://beanform.sourceforge.net/changes-report.html
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
The project is hosted on sourceforge, so I'm using their CVS (see
http://sourceforge.net/cvs/?group_id=171323, or browse it online at
http://beanform.cvs.sourceforge.net/beanform/).
What features have you added? Anything that could be useful to others?
Daniel
On 9/14/06, Martin Strand <[EMAIL PROTECTED]> wrote:
Nice work! :)
I was actually just working on my own beanform when I came across yours
about two weeks ago. Now I use yours instead, I just subclassed it to add
a few app specific features.
Do you have a public svn repo somewhere?
Martin
On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I have just released the latest version of BeanForm, a single-line POJO
> editor component:
>
> span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
> delete="listener:delete"
>
> The above line of code gets you a form that:
>
> * calls your page's save() method when submitted for save
> * calls your page's delete() method when submitted for delete
> * gives you a TextField for each of the bean's string and numerical
> properties
> * gives you a Checkbox for each of the bean's boolean properties
> * gives you a DatePicker for each of the bean's date properties
> * automatically disables fields for read-only properties
>
> If you are using Java Persistence API (EJB3) annotations and/or
Hibernate
> Validator annotations, the BeanForm component also:
>
> * infers validation strings for annotated properties
> * uses TextAreas instead of TextFields for annotated string
> properties
> whose maximum length is over 255 characters
>
> Some other important features:
>
> * EJB3 and Hibernate Validator support is optional and enabled
> automatically at runtime only when appropriate
> * you can use a BeanForm inside a Form component, in which case the
> BeanForm will not emit a second form tag
> * you can explicitly specify which properties to display, as well as
> their validation strings
> * when specifying properties explicitly, they may be recursive ("
> person.address.city.name", for example)
> * you can override the input components used to edit properties
> * support for canceling and refreshing forms
> * support for localization
>
> Starting with version 0.4, BeanForm should work with both Tapestry 4.0
> and
> Tapestry 4.1.
> I should also note that starting with version 0.4, BeanForm requires the
> tapestry-prop library, available at
>
http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
> .
>
> Give it a whirl and let me know if you have any problems, comments or
> suggestions.
>
> Take care,
>
> Daniel Gredler
>
>
> Homepage: http://beanform.sourceforge.net/
> Component Reference:
> http://beanform.sourceforge.net/component-reference.html
> Change History: http://beanform.sourceforge.net/changes-report.html
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [announce] BeanForm 0.4
Nice work! :)
I was actually just working on my own beanform when I came across yours
about two weeks ago. Now I use yours instead, I just subclassed it to add
a few app specific features.
Do you have a public svn repo somewhere?
Martin
On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]>
wrote:
Hi all,
I have just released the latest version of BeanForm, a single-line POJO
editor component:
span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
delete="listener:delete"
The above line of code gets you a form that:
* calls your page's save() method when submitted for save
* calls your page's delete() method when submitted for delete
* gives you a TextField for each of the bean's string and numerical
properties
* gives you a Checkbox for each of the bean's boolean properties
* gives you a DatePicker for each of the bean's date properties
* automatically disables fields for read-only properties
If you are using Java Persistence API (EJB3) annotations and/or Hibernate
Validator annotations, the BeanForm component also:
* infers validation strings for annotated properties
* uses TextAreas instead of TextFields for annotated string
properties
whose maximum length is over 255 characters
Some other important features:
* EJB3 and Hibernate Validator support is optional and enabled
automatically at runtime only when appropriate
* you can use a BeanForm inside a Form component, in which case the
BeanForm will not emit a second form tag
* you can explicitly specify which properties to display, as well as
their validation strings
* when specifying properties explicitly, they may be recursive ("
person.address.city.name", for example)
* you can override the input components used to edit properties
* support for canceling and refreshing forms
* support for localization
Starting with version 0.4, BeanForm should work with both Tapestry 4.0
and
Tapestry 4.1.
I should also note that starting with version 0.4, BeanForm requires the
tapestry-prop library, available at
http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
.
Give it a whirl and let me know if you have any problems, comments or
suggestions.
Take care,
Daniel Gredler
Homepage: http://beanform.sourceforge.net/
Component Reference:
http://beanform.sourceforge.net/component-reference.html
Change History: http://beanform.sourceforge.net/changes-report.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[announce] BeanForm 0.4
Hi all,
I have just released the latest version of BeanForm, a single-line POJO
editor component:
span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save"
delete="listener:delete"
The above line of code gets you a form that:
* calls your page's save() method when submitted for save
* calls your page's delete() method when submitted for delete
* gives you a TextField for each of the bean's string and numerical
properties
* gives you a Checkbox for each of the bean's boolean properties
* gives you a DatePicker for each of the bean's date properties
* automatically disables fields for read-only properties
If you are using Java Persistence API (EJB3) annotations and/or Hibernate
Validator annotations, the BeanForm component also:
* infers validation strings for annotated properties
* uses TextAreas instead of TextFields for annotated string properties
whose maximum length is over 255 characters
Some other important features:
* EJB3 and Hibernate Validator support is optional and enabled
automatically at runtime only when appropriate
* you can use a BeanForm inside a Form component, in which case the
BeanForm will not emit a second form tag
* you can explicitly specify which properties to display, as well as
their validation strings
* when specifying properties explicitly, they may be recursive ("
person.address.city.name", for example)
* you can override the input components used to edit properties
* support for canceling and refreshing forms
* support for localization
Starting with version 0.4, BeanForm should work with both Tapestry 4.0 and
Tapestry 4.1.
I should also note that starting with version 0.4, BeanForm requires the
tapestry-prop library, available at
http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/
.
Give it a whirl and let me know if you have any problems, comments or
suggestions.
Take care,
Daniel Gredler
Homepage: http://beanform.sourceforge.net/
Component Reference:
http://beanform.sourceforge.net/component-reference.html
Change History: http://beanform.sourceforge.net/changes-report.html
