Re: CForms: widget states added
Bart Molenkamp 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.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Re: CForms: widget states added
On 03.11.2004 09:06, 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. So I'm about to close the bug if the widget states work - what I assume ;-) Joerg
Re: CForms: widget states added
Joerg Heinicke wrote:
On 03.11.2004 09:06, 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.
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.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Re: CForms: widget states added
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
Re: CForms: widget states added
Joerg Heinicke wrote:
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').
Ah, ok. So then instead of using type=output, the widget's state
should be set to disabled. That way, the value will never be read.
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?
I leave this to your judgment ;-)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
RE: CForms: widget states added
Does it fix this one?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27598
Bart.
-Original Message-
From: Sylvain Wallez [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 02, 2004 11:12 AM
To: [EMAIL PROTECTED]
Subject: CForms: widget states added
Hi all,
I finally added widget states to CForms. All widgets can have a
state
attribute withe the values active (the default), disabled or
invisible, which are defined in a new WidgetState class.
In disable state, values are displayed, but are not read from the
request. In invisible state, nothing is displayed (not even labels)
and
values are of course not read from the request. The stylesheets have
been updated so that disabled widgets are displayed using disabled
html
inputs (eh!).
Tim, this new widget state feature conflicts with your
getProcessingRequests() stuff in 2.2, and I think your swan
experiment could be updated to use widget states.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
