cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: CForms: widget states added
Date Wed, 03 Nov 2004 11:58:08 GMT
On 03.11.2004 11:51, Sylvain Wallez wrote:

>>>> Does it fix this one?
>>>> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27598
>>>
>>> Mmmh... not sure, although you can prevent a widget from reading its 
>>> value from the request by setting it's state do "disabled". This bug 
>>> is more likely to be fixed by having widgets only changing their 
>>> values *if* the corresponding request parameter is present, as 
>>> proposed by Tim in the "[lazy vote] cforms request processing thread".
>>
>> I don't think so. The bug was about an analogy to @direction="load" in 
>> binding. Having a widget with output styling does not prevent it from 
>> reading from request though there will not be request parameter of it.
> 
> That's exactly what the request processing thread is all about: don't 
> change a widget's value if the corresponding request parameter doesn't 
> exist. That's exactly the case of output styling.

When re-reading my written comment above I see I was not clear enough. 
It must read:

Having a widget with output styling does not prevent it from reading 
from request though there will not be request parameter of it by 
default. This means you can hack the URL to change the value but you 
should not be able to change the value of the widget at all as it is set 
to 'do not read the value from request' (the analogy to binding's 
@direction='load').

>> So I'm about to close the bug if the widget states work - what I 
>> assume ;-)
> 
> I would wait for this do-not-reset-value-if-parameter-is-not-present 
> thing to be implemented.

Also after my clarification?

Joerg

Mime
View raw message