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
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 featur
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] B
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 hav
: [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
ounce] 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
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?
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 pa
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 r
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 us
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
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
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 P
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 <[EMAI
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
15 matches
Mail list logo
