displayValueOnly attribute

[Martin Marinschek <ma...@gmail.com>]

Hi there,

I have implemented the functionality we were discussing about on the
list - all input extended components now have a displayValueOnly
attribute for changing their behaviour to read-only.

Try it out - it will not break any existing code, as the components
stay the same and the renderer classes do fall back to the normal
rendering behaviour if the displayValueOnly attribute is not set.

regards,

Martin

Re: displayValueOnly attribute

[Martin Marinschek <ma...@gmail.com>]

The behaviour has been tweaked to also work for enclosing panelGroups
and panelGrids as well - so you only need to set the attributes once,
and they will be inherited to all child components.

Additionally, the set of extended components has been widened by all
components which were necessary for the displayValueOnly change, so
"forceId" and the user-role attributes should now work on a larger set
of components as well.

regards,

Martin

On 5/16/05, Martin Marinschek <ma...@gmail.com> wrote:
> Hi there,
> 
> I have implemented the functionality we were discussing about on the
> list - all input extended components now have a displayValueOnly
> attribute for changing their behaviour to read-only.
> 
> Try it out - it will not break any existing code, as the components
> stay the same and the renderer classes do fall back to the normal
> rendering behaviour if the displayValueOnly attribute is not set.
> 
> regards,
> 
> Martin
>