Re: DRAFT: Actions Module (XForms 1.2)

Hi Mark,

I included my response in-line.

Nick Van den Bleeken  -  Research & Development Manager
Inventive Designers
Phone: +32 - 3 - 8210170
Fax: +32 - 3 - 8210171
Email: Nick_Van_den_Bleeken@inventivegroup.com

"Mark Birbeck" <mark.birbeck@webbackplane.com> wrote on 07/14/2008 
11:34:27 AM:

> Hi Nick,
> 
> > I started working on the action module. You can find a first version 
on [1],
> > for the source archive see[2].
> >
> > Any feedback would be helpful.
> 
> One small thing, and one larger one, from a quick read.

Thank you for reading it.

> 
> The small thing is that, in the section where you say that there are
> two types of events that can be dispatched (XForms events and
> user-defined events), you should probably mention that we can also
> dispatch events that are defined in other modules, such as SMIL or
> SVG.

Yes, I know this part needs to be rewritten, but I have sent a separate 
e-mail (http://lists.w3.org/Archives/Public/public-forms/2008Jul/0029.html
) with a question about this section.

> 
> The larger one is, should this module not be using XML Events 2 [1],
> which includes the conditional attributes, the event() XPath function,
> the dispatch action, and more, rather than defining them ourselves?
>

That's a good remark, and I thought about it too. I think we should 
discuss this in the WG, if this is one of the things we want to do for 
XForms 1.2.

After quick re-read of the XML events 2.0 spec I have the following 
questions : 
  - Is there an overview of what was added/changed between XML events 1.0 
and 2.0 (obviously the if, while attributes and the XML handlers module)
  - The dispatch action of XForms threats the XForms events differently of 
other events, regarding to the bubbles and cancelable attributes. I'm I 
correct that this can't be enforced when we adopt XML events 2.0
  - Do you know any other negative impacts it will have if we upgrade to 
XML Events 2.0? I did a quick look at the most obvious additions and found 
no negative impact so far :
     * 'if' and 'while' attributes can be made compatible with existing 
ones in XForms 1.1 (when we import the module we can specify the context 
attributes)
     * 'stopPropagation' and 'preventDefault' actions are just other ways 
to do what already could be done with the attributes on a listener (with 
some advantages in some use cases)
          * 'addEventListeren' and 'removeEventListener' could also be 
written with 'if' on a listener, but these actions could simplify some use 
cases
          * 'script' some XForms processors already supported this action

This is probably a good topic for the next telecon, I will put it on the 
agenda for next call.
 
> Regards,
> 
> Mark
> 
> [1] <http://www.w3.org/MarkUp/2008/ED-xml-events-20080625/>
> 
> -- 
> Mark Birbeck, webBackplane
> 
> mark.birbeck@webBackplane.com
> 
> http://webBackplane.com/mark-birbeck
> 
> webBackplane is a trading name of Backplane Ltd. (company number
> 05972288, registered office: 2nd Floor, 69/85 Tabernacle Street,
> London, EC2A 4RR)
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> --
> 
> 

Inventive Designers' Email Disclaimer:   http://www.inventivedesigners.com/email-disclaimer =
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--