logo       

Related Msgs: audio.musicbrai...    enbd.general/20...    ietf.idr/2002-0...    java.ant-contri...    gnu.make.genera...    qplus.devel/200...    video.freevo.cv...    os.netbsd.ports...    yellowdog.gener...    xfree86.cvs/200...    search.nutch.us...    freedesktop.xse...    programming.swi...    capabilities.ge...    telephony.pbx.a...    mail.sylpheed.c...    db.firebase.por...    boot-loaders.u-...    recreation.radi...    netbsd.bugs/200...    web.zope.plone....    user-groups.lin...   

Re: Re: optional elements not displaying: msg#00003

Subject: Re: Re: optional elements not displaying
Andrzej Jan Taramina wrote:

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.

just an idea: wouldn't it be possible to use a repeat instead of a select1 here and use relevant to select the actual choice of the user?

i agree, that XForms cant handle the readonly/relevant props for single items in a select1/select cause they don't have these props by themselves but only their parent.

Joern


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/
_______________________________________________
Chiba-developer mailing list
Chiba-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/chiba-developer





-------------------------------------------------------
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/



Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>