You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by D&J Gredler <dj...@gmail.com> on 2006/10/02 23:03:53 UTC

[announce] BeanForm 0.5

Hi all,

The latest release of BeanForm, the single-line POJO editor component, is
now available for download. Below is a list of changes since the last
version. There are two incompatible changes that all current users should be
aware of -- they're at the very end.

Happy hacking,

Daniel Gredler



Changes:

 - Add "exclude" parameter to the BeanForm component.
 - Dynamic binding overrides for input fields via informal parameters on the
BeanForm (very cool).
 - Add Italian translation. Thanks to Edoardo Campagnano.
 - More efficient dynamic validator list building process (~70% form rewind
time savings).
 - Don't use deprecated translator binding.
 - Fix bug 1554067: input override via use of carefully-named components
breaks when using BeanForm inside a custom component. Thanks to Edoardo
Campagnano.
 - Fix bug 1560627: input override can't be used when you have 2+ BeanForms.
Thanks to Edoardo Campagnano.
 - Fix bug 1565487: indexed JavaBean properties cause NPEs in
BeanProperty#getTypeName(). Thanks to Jon McCarty.
 - Fix bug 1565478: write-only JavaBean properties cause NPEs in
BeanProperty#getValue(). Thanks to Jon McCarty.

Incompatible Changes:

 - If you are overriding inputs via the use of carefully-named components,
the new naming formula is
"[beanform-component-id]_[property-name]_BeanFieldBlock" and
"[beanform-component-id]_[property-name]_BeanField". Adding the BeanForm's
id to the naming convention allows users with more than one BeanForm on
their page to use this override method.
 - If you are using "[property-name]PSM" informal parameters to get dropdown
boxes for your properties, the new naming convention is
"[property-name]_model". This change was made to make the convention
consistent with the new dynamic binding override functionality
("[property-name]_[binding-name]").

----------------------------
Homepage: http://beanform.sourceforge.net/
Component Reference: http://beanform.sourceforge.net/component-reference.html

Change History: http://beanform.sourceforge.net/changes-report.html
----------------------------

Re: [announce] BeanForm 0.5

Posted by D&J Gredler <dj...@gmail.com>.
Walter -

Button binding override has been checked into CVS and will be included in
the next version (0.7).

Daniel


On 11/14/06, D&J Gredler <dj...@gmail.com> wrote:
>
> Hi Walter,
>
> BeanForm uses message catalogs for the button labels, and as far as I can
> tell from some quick experimentation you cannot override these messages in
> your own application (surprising, actually). I've been getting a few
> button-related enhancement requests lately, so that may be the focus of the
> next release. If you have needs and suggestions, please post feature
> requests to the SF project page [1] and I'll see what I can do. In the
> meantime, yes, you will need to wrap the BeanForm in a Form :-)
>
> Take care,
>
> Daniel
>
> [1] http://sourceforge.net/tracker/?group_id=171323&atid=857541
>
>
> On 11/14/06, Walter Kelly <wa...@usitc.gov> wrote:
> >
> > Hi Daniel,
> >
> > We have just started to experiment with using the BeanForm on our
> > current
> > project and so far so good.  Is there any way the change the labels for
> > the form
> > generated buttons, like the save and delete?  I've tried overriding the
> > bindings, similiar to way it's suggested for the input fields but I have
> > been
> > meet with no success.  Also, I would like to be able to do it without
> > wrapping
> > the BeanForm in another form, unless that's the suggested way.
> >
> > Thanks,
> > Walter
> >
>
>

Re: [announce] BeanForm 0.5

Posted by D&J Gredler <dj...@gmail.com>.
Hi Walter,

BeanForm uses message catalogs for the button labels, and as far as I can
tell from some quick experimentation you cannot override these messages in
your own application (surprising, actually). I've been getting a few
button-related enhancement requests lately, so that may be the focus of the
next release. If you have needs and suggestions, please post feature
requests to the SF project page [1] and I'll see what I can do. In the
meantime, yes, you will need to wrap the BeanForm in a Form :-)

Take care,

Daniel

[1] http://sourceforge.net/tracker/?group_id=171323&atid=857541


On 11/14/06, Walter Kelly <wa...@usitc.gov> wrote:
>
> Hi Daniel,
>
> We have just started to experiment with using the BeanForm on our current
> project and so far so good.  Is there any way the change the labels for
> the form
> generated buttons, like the save and delete?  I've tried overriding the
> bindings, similiar to way it's suggested for the input fields but I have
> been
> meet with no success.  Also, I would like to be able to do it without
> wrapping
> the BeanForm in another form, unless that's the suggested way.
>
> Thanks,
> Walter
>

Re: [announce] BeanForm 0.5

Posted by Walter Kelly <wa...@usitc.gov>.
Hi Daniel,

We have just started to experiment with using the BeanForm on our current
project and so far so good.  Is there any way the change the labels for the form
generated buttons, like the save and delete?  I've tried overriding the
bindings, similiar to way it's suggested for the input fields but I have been
meet with no success.  Also, I would like to be able to do it without wrapping
the BeanForm in another form, unless that's the suggested way.

Thanks,
Walter





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: [announce] BeanForm 0.5

Posted by D&J Gredler <dj...@gmail.com>.
Ah, I think you're confusing the page property names with the parameter
names. The convention is in the naming of the informal parameters (like
"owner_model" and "manufacturer_model"). You can name your page properties
however you like (in this case "ownerPSM" and "manufacturerPSM"). I'll try
to make the wording clearer.

On 10/5/06, Patrick Moore <tr...@gmail.com> wrote:
>
> In section 5. (http://beanform.sourceforge.net/component-reference.html) I
> see references to 'PSM' for the property selection model.. but I think I
> may
> have just misread your release note.
>
> On 10/4/06, D&J Gredler <dj...@gmail.com> wrote:
> >
> > I'm afraid I don't see the old notation anywhere... what example are you
> > looking at?
> >
> >
> >
>
>

Re: [announce] BeanForm 0.5

Posted by Patrick Moore <tr...@gmail.com>.
In section 5. (http://beanform.sourceforge.net/component-reference.html) I
see references to 'PSM' for the property selection model.. but I think I may
have just misread your release note.

On 10/4/06, D&J Gredler <dj...@gmail.com> wrote:
>
> I'm afraid I don't see the old notation anywhere... what example are you
> looking at?
>
>
>

Re: [announce] BeanForm 0.5

Posted by D&J Gredler <dj...@gmail.com>.
I'm afraid I don't see the old notation anywhere... what example are you
looking at?

On 10/4/06, Patrick Moore <tr...@gmail.com> wrote:
>
> Thanks ... I am going to try this.. btw .. your on-line doc still uses the
> old notation
>
> On 10/2/06, D&J Gredler <dj...@gmail.com> wrote:
> >
> > Hi all,
> >
> > The latest release of BeanForm, the single-line POJO editor component,
> is
> > now available for download. Below is a list of changes since the last
> > version. There are two incompatible changes that all current users
> should
> > be
> > aware of -- they're at the very end.
> >
> > Happy hacking,
> >
> > Daniel Gredler
> >
> >
> >
> > Changes:
> >
> > - Add "exclude" parameter to the BeanForm component.
> > - Dynamic binding overrides for input fields via informal parameters on
> > the
> > BeanForm (very cool).
> > - Add Italian translation. Thanks to Edoardo Campagnano.
> > - More efficient dynamic validator list building process (~70% form
> rewind
> > time savings).
> > - Don't use deprecated translator binding.
> > - Fix bug 1554067: input override via use of carefully-named components
> > breaks when using BeanForm inside a custom component. Thanks to Edoardo
> > Campagnano.
> > - Fix bug 1560627: input override can't be used when you have 2+
> > BeanForms.
> > Thanks to Edoardo Campagnano.
> > - Fix bug 1565487: indexed JavaBean properties cause NPEs in
> > BeanProperty#getTypeName(). Thanks to Jon McCarty.
> > - Fix bug 1565478: write-only JavaBean properties cause NPEs in
> > BeanProperty#getValue(). Thanks to Jon McCarty.
> >
> > Incompatible Changes:
> >
> > - If you are overriding inputs via the use of carefully-named
> components,
> > the new naming formula is
> > "[beanform-component-id]_[property-name]_BeanFieldBlock" and
> > "[beanform-component-id]_[property-name]_BeanField". Adding the
> BeanForm's
> > id to the naming convention allows users with more than one BeanForm on
> > their page to use this override method.
> > - If you are using "[property-name]PSM" informal parameters to get
> > dropdown
> > boxes for your properties, the new naming convention is
> > "[property-name]_model". This change was made to make the convention
> > consistent with the new dynamic binding override functionality
> > ("[property-name]_[binding-name]").
> >
> > ----------------------------
> > Homepage: http://beanform.sourceforge.net/
> > Component Reference:
> > http://beanform.sourceforge.net/component-reference.html
> >
> > Change History: http://beanform.sourceforge.net/changes-report.html
> > ----------------------------
> >
> >
>
>

Re: [announce] BeanForm 0.5

Posted by Patrick Moore <tr...@gmail.com>.
Thanks ... I am going to try this.. btw .. your on-line doc still uses the
old notation

On 10/2/06, D&J Gredler <dj...@gmail.com> wrote:
>
> Hi all,
>
> The latest release of BeanForm, the single-line POJO editor component, is
> now available for download. Below is a list of changes since the last
> version. There are two incompatible changes that all current users should
> be
> aware of -- they're at the very end.
>
> Happy hacking,
>
> Daniel Gredler
>
>
>
> Changes:
>
> - Add "exclude" parameter to the BeanForm component.
> - Dynamic binding overrides for input fields via informal parameters on
> the
> BeanForm (very cool).
> - Add Italian translation. Thanks to Edoardo Campagnano.
> - More efficient dynamic validator list building process (~70% form rewind
> time savings).
> - Don't use deprecated translator binding.
> - Fix bug 1554067: input override via use of carefully-named components
> breaks when using BeanForm inside a custom component. Thanks to Edoardo
> Campagnano.
> - Fix bug 1560627: input override can't be used when you have 2+
> BeanForms.
> Thanks to Edoardo Campagnano.
> - Fix bug 1565487: indexed JavaBean properties cause NPEs in
> BeanProperty#getTypeName(). Thanks to Jon McCarty.
> - Fix bug 1565478: write-only JavaBean properties cause NPEs in
> BeanProperty#getValue(). Thanks to Jon McCarty.
>
> Incompatible Changes:
>
> - If you are overriding inputs via the use of carefully-named components,
> the new naming formula is
> "[beanform-component-id]_[property-name]_BeanFieldBlock" and
> "[beanform-component-id]_[property-name]_BeanField". Adding the BeanForm's
> id to the naming convention allows users with more than one BeanForm on
> their page to use this override method.
> - If you are using "[property-name]PSM" informal parameters to get
> dropdown
> boxes for your properties, the new naming convention is
> "[property-name]_model". This change was made to make the convention
> consistent with the new dynamic binding override functionality
> ("[property-name]_[binding-name]").
>
> ----------------------------
> Homepage: http://beanform.sourceforge.net/
> Component Reference:
> http://beanform.sourceforge.net/component-reference.html
>
> Change History: http://beanform.sourceforge.net/changes-report.html
> ----------------------------
>
>