- From: Josef Dietl <josef@mozquito.com>
- Date: Mon, 15 Oct 2001 15:25:11 +0200
- To: "xavier" <xavier.gagneur@e-xmlmedia.fr>, <www-forms@w3.org>, <w3c-forms@w3.org>
Hi Xavier, let's see if I understand you correctly: You propose to add "maxOccurs='unbounded'" to the following line: <xsd:group name="commonUIChildren"> <xsd:all> ... <xsd:element ref="xform:action" minOccurs="0"/> <!-- here --> ... </xsd:all> </xsd:group> I'm afraid that would be another of the (in)famous "ordered and unbounded vs. unordered and maxOccurs='1'" instances. Other than that, what you suggest appears reasonable to me. We'll discuss it at the next telephone conference. Josef -----Original Message----- From: xavier [mailto:xavier.gagneur@e-xmlmedia.fr] Sent: Monday, October 15, 2001 1:59 PM To: www-forms@w3.org Subject: Form controls reacting to several events Hi, If I understand correctly the spec (more precisely §8 XForms Actions), it's possible to launch several actions on only one event for a formControl, but it's impossible to launch several actions for different events. For instance,it is legal (according to xforms schema) to have two actions launched by an event: <xform:input ref="boss:name"> <xform:caption>Name</xform:caption> <xform:action event="mouseover"> <xform:setValue ref="boss:surname" value="new value"/> <xform:setFocus idref="boss:surname"/> </xform:action> </xform:input> But the following isn't legal (actions are launched by two different events), althought it seems useful: <xform:input ref="boss:name"> <xform:caption>Name</xform:caption> <xform:action event="mouseover"> <xform:setValue ref="boss:surname" value="new value"/> </xform:action> <xform:action event="Click"> <xform:setFocus idref="boss:surname"/> </xform:action> </xform:input> So I think that we should put maxOcurrs = "unbounded" for xform:action element in commonUIChildren group to define several actions launched by different events. Thank you for feedback. Xavier
Received on Monday, 15 October 2001 09:26:02 UTC