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

RE: Event questions.

From: Alessandro Triglia <sandro@mclink.it>
Date: Fri, 28 Jul 2006 11:28:17 -0400
To: "'Rogelio Pérez Cano'" <rogeliop@satec.es>, <www-forms@w3.org>
Message-ID: <000401c6b25a$780d5be0$8b01a8c0@aldebaran>

 

> -----Original Message-----
> From: www-forms-request@w3.org 
> [mailto:www-forms-request@w3.org] On Behalf Of Rogelio Pérez Cano
> Sent: Thursday, July 27, 2006 08:43
> To: www-forms@w3.org
> Subject: Event questions.
> 
> 
> Hi All,
> 
> I have three questions related to Events in XForms.
> 
> 1- The latest XForms 1.0 recommendation doesn´t forbid a 
> handler attribute
> in an <action> element,so does it mean that an <action> can 
> be defined with
> a handler attribute pointing to another <action>? 
> 
> (This can be usefull in order to reuse code).
> 
>   Something like that should it work? 
> 
> ....
>     
> <xforms:trigger id="trigger1"> 
>   <xforms:label>Button1</xforms:label> 
>   <xforms:action ev:event="DOMActivate" ev:target="trigger1"
> ev:observer="trigger1" ev:handler="action2"/>
> </xforms:trigger>
> <xforms:trigger>
>   <xforms:label>Button2</xforms:label> 
>   <xforms:message id="action2" level="modal" 
> ev:event="DOMActivate"> Hi
> again!!</xforms:message>
>    
> </xforms:trigger>
> ......
> 
> I mean, when the "Button1" is pressed should the message be shown?
> 
> 
> 2- What is the interpretation of an <action> in terms of XML 
> Events, is it a
> listener or can be always considered like a handler?
> 
> 3- What is the aim of having events in a <model> element, 
> more specifically
> what does this sentence mean?
> 
> "Attributes from XML Events are allowed on this element to facilitate
> creating observers"


That's an interesting question.  I was going to ask the same question.

Clearly, there can be only one "ev:event" attribute on this element (for the
whole instance(s)).   If the objective is to facilitate the creation of
observers for events occurring within the instance data, shouldn't there be
a facility for including handlers (like <action>s) as children of the
<model> events, rather than a single handler for a single type of event via
"ev:" attributes?

Alessandro
Received on Friday, 28 July 2006 15:29:39 GMT

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