W3C home > Mailing lists > Public > www-forms@w3.org > August 2003

Svar: Storing values of "select" controls

From: David Landwehr <DLandwehr@novell.com>
Date: Sat, 23 Aug 2003 17:11:15 +0200
Message-Id: <sf47923e.058@emea1-mh.id2.novell.com>
To: <roman.huditsch@hico.com>, <www-forms@w3.org>

Hi Roman,

You can use copy to get this behavior. The following is a simple example of what you could do:

<xforms:model>
  <xforms:instance id="defaultInstance">
    <data xmlns="">
      <selectedValues/>
    </data>
  </xforms:instance>
  <xforms:instance id="selectValueInstance">
    <data xmlns="">
      <selectedValue>red</selectedValue>
      <selectedValue>green</selectedValue>
    </data>
  </xforms:instance>
</xforms:model>

<xforms:select ref="selectedValues">
  <xforms:label>Select colours</xforms:label>
  <xforms:itemset nodeset="instance('selectValueInstance')/selectedValue">
    <xforms:label ref="."/>
    <xforms:copy ref="."/> <!-- Will copy the selectedValue into selectedValues -->
  </xforms:itemset>
</xforms:select>

Best regards,
David

>>> "Roman Huditsch" <roman.huditsch@hico.com> 19-08-03 10:26 >>>

Hello,

I am actually confronted with an user requirement concerning the layout and logic of an XForms file, which I currently can't fullfil.
I hope that someone of this mailinglist can give me an important hint.
So what's the problem...

As I have understood the XForms specification, all selected values of a "select"-control are stored in the bound element (or attribute) as whitespace seperated list.
Example: <selectedValues>yellow red green blue</selectedValues>

So far so good.

What my user want is the following:

He want to be able to select different values from a "select"-element, but the corresponding values should not be stored as a whitespace seperated list.
But the values should be stored like:
<selectedValues>
	<selectedValue>red</selectedValue>
	<selectedValue>green</selectedValue>
	...
</selectedValues>

Is there any way to do so?
I thought about solving this problem over repeating structures, but this would mean that following select-elements must not include values ehich have been chosen before....

Pleas help me.

with best regards,
Roman 

-----Ursprüngliche Nachricht-----
Von: Klotz, Leigh [mailto:Leigh.Klotz@pahv.xerox.com]
Gesendet: Dienstag, 12. August 2003 22:18
An: 'Daniel Fowler'; 'www-forms@w3.org'
Betreff: RE: Clarification of id attribute



Daniel,

The sentence  "A host language must include an attribute of type xsd:ID on
each
XForms element." means that the definition of the host language  must allow
for the placement of an ID on each XForms element, not that every document
conformant to the XForms+host-language definition must have an ID attribute
on each element in the document.

Leigh.


-----Original Message-----
From: Daniel Fowler [mailto:daniel.fowler@focus-solutions.co.uk] 
Sent: Tuesday, August 12, 2003 3:10 AM
To: 'www-forms@w3.org'
Subject: Clarification of id attribute



Hi All,

I'd like some thoughts on the following issue, I sent a mail to the editors
on 27/6 so it was probably to late for the Proposed Recommendation.

The Proposed Recommendation refers to the use of "the terms may, must and
should in accord with [RFC 2119]". The last paragraph in section 3.2.1
states "A host language must include an attribute of type xsd:ID on each
XForms element."

However, the example "G.1 XForms in XHTML" does not include an attribute of
type xsd:ID on all the XForms elements.
..
Received on Saturday, 23 August 2003 11:21:06 GMT

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