>> although i tend to agree with you, can you give an example? i think we
> must be carefull not to overlap the meaning of relevant with that of
> readonly. at least there is the problem of how to render these two
> states differently so that the user can distinguish them. - any idea here?
Hmmm..readonly might be what I'm looking for.
Part of my problem is that I want to flag a control as readonly (or not
revelant) based on the current value of some arbitrary instance node. I
don't want to tag an actual instance/model item with readonly.
I have some situations where I have multiple select1's that bind to the
instance element, and only need to disable one of the select1's based on the
value of a different field.
For example, I have three select1's showing as radio buttons that let the
user choose what type of output they want: fax/email/print. But if the user
has not entered an email addy in a separate email field, I want to disable
the radio button for email selection since it doesn't make sense.
XForms does not seem to have a way to do this, barring structuring your
instance XML document in an ugly manner with multiple elements, one for each
selection. I use something like <deliveryMethod>email</deliveryMethod> in my
model and each select1 binds to the <deliveryMethod> element. Works great
with Chiba.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
|
