W3C home > Mailing lists > Public > www-forms@w3.org > May 2006

Re: @value on value element?

From: Stefano Debenedetti <ste@demaledetti.net>
Date: Thu, 11 May 2006 15:19:45 +0200
Message-ID: <446339F1.30106@demaledetti.net>
To: David Landwehr <david.landwehr@solidapp.com>
CC: Allan Beaufour <beaufour@gmail.com>, www-forms <www-forms@w3.org>

Yes, wouldn't this be useful on labels too? Using output inside label seems more of a hack than allowing value directly on label itself...

ciao
ste

David Landwehr ha scritto:
> 
> This has been suggested before by Kenneth and I was all for it then but
> it never came down to solution. This would be such a useful feature!
> 
> /David
> 
> Allan Beaufour wrote:
> 
>>
>> It occured to me that it maybe could be useful to have @value (like
>> for setvalue and output) on the <xf:value/> element too.
>>
>> So you could do:
>>    <xf:select1 ref="foo">
>>      <xf:label>Choose something: </xf:label>
>>      <xf:itemset nodeset="/listitems">
>>     <xf:label ref="@name"/>
>>     <xf:value value="concat(value1, ',', value2)"/>
>>      </xf:itemset>
>>    </xf:select1>
>> To create "val1, val2" as the value of foo when an item is selected.
>> This could be used for constructing URIs or creating requests to
>> abitrary services.
>>
>> The only problem I can see (right now :) ), is how to handle the
>> semantics for relevancy for values -- if we want to give that any
>> meaning (as per the thread Erik started some time ago).
>>
>> What do you say?
>>
> 
> 
Received on Thursday, 11 May 2006 13:20:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:04 GMT