On 25 Feb 2004, at 12:32, Reinhard Poetz wrote:
>
>
>> -----Original Message-----
>> From: Antonio Gallardo [mailto:agallardo@agssa.net]
>> Sent: Wednesday, February 25, 2004 1:28 PM
>> To: dev@cocoon.apache.org
>> Subject: Re: disabling widgets
>>
>>
>> Jeremy Quinn dijo:
>>> Hi All
>>>
>>> I have a booleanfield widget, that needs to be disabled
>> under certain
>>> conditions.
>>>
>>> pseudo-code :
>>>
>>> if ( album.scenarios.size() > 0 ) {
>>> disable ( album.publishable );
>>> }
>>>
>>> ie. the album.publishable value needs to be in the form, but should
>>> not be alterable by the user.
>>>
>>> Is there a way of doing this in Cocoon Forms ?
>>
>> Another approach (not tested by me, but maybe works) is using
>> the JXTemplateGenerator. There is a <jx:if> tag that can be
>> use to show/hide controls in the rendered page.
>
> IIRC Sylvain extendet the showform function so that you can pass the
> objects to the view layer. You could either use Antonio's suggestion or
> you add a parameter to the widget styling.
So what you are saying is this? :
1. add appropriate JX-Template conditional statement to my
booleanfield widget
which will add @readonly="readonly" to the wi:styling if the
condition is met
2. pass the required BizData to the showform method as required by the
conditional above
3. use JX-Generator instead of the FileGenerator in my Woody pipeline
to pre-process
my Woody-Template before it goes to the Woody Transformer
> My question: Is this the way we recommend or do we want to have widgets
> an interface which can be used in order change presentation state?
It is with much joy that I find @readonly is ignored by both Mozilla
and Safari (hoo-bloody-ray!! )
So while the standards are not implemented on the browsers, going to a
lot of effort to add this to Woody will be a waste of time IMHO,
because you would need to hack the widget tags in an
application-specific way.
regards Jeremy
|