RE: Grouping tag for actions

It is important to remember the role of events in conjunction with
<button> and actions. You only use <action> when you need to sequence
more than one action for any single event (e.g., activate). Multiple
other actions would be defined for different events. You should find
with a DOM implementation that you are looping over children where the
event attribute matches the event you are handling. There is not that
many additional siblings to the action elements to cause concern. 

> -----Original Message-----
> From: Eric Fu [mailto:ericfu@etrieve.com]
> Sent: Thursday, December 13, 2001 12:45 PM
> To: www-forms@w3.org
> Subject: RE: Grouping tag for actions
> 
> 
> I think the "action" tag is supposed to do what I asked for, i.e. for
> grouping purposes, right?
> Just want to confirm.
> 
> eric
>  
> 
> -----Original Message-----
> From: Eric Fu [mailto:ericfu@etrieve.com]
> Sent: Thursday, December 13, 2001 9:22 AM
> To: www-forms@w3.org
> Subject: Grouping tag for actions
> 
> 
> I found it programmatically easier to introduce a "grouping" 
> tag around
> XForms action. 
> 
> For example, in the current specification, you define something like: 
> 
> <button>
>   <caption>Press Me:</caption>
>   <resetInstance ev:event="..." />
>   <loadURL href="..." ev:event="..." />
> </button>
> 
> It would be easier for a programmer of the XForms viewer to 
> group the action
> tags together, for example: 
> 
> <button>
>   <caption>Press Me:</caption>
>   <actions>
>       <resetInstance ev:event="..." />
>       <loadURL href="..." ev:event="..." />
>   </actions>
> </button>
> 
> It's more efficient because the code does not have to search 
> for all the
> possible action tags but just iterate through the "actions" tag.
> 
> Has the working group considered this?
> 
> 
> Eric
> 
>

Received on Thursday, 13 December 2001 13:45:12 UTC