Re: Analysis of the effects of moving to XML Events 2 for XForms 1.2

Nick,

you are right, no response yet from the XHTML 2 group. Maybe Steven or
Mark could tell more about this issue?

Regards,
Uli.

Nick_Van_den_Bleeken@inventivegroup.com wrote:
> 
> Uli,
> 
> The e-mail that you copied to the XHTML 2 list was as a response on my
> initial e-mail to which I included a link in my previous e-mail. But am
> I missing something or am I correct that nobody from the XHTML 2 replied
> to your e-mail?
> 
> Regards,
> 
> Nick Van den Bleeken  -  Research & Development Manager
> Inventive Designers
> Phone: +32 - 3 - 8210170
> Fax: +32 - 3 - 8210171
> Email: Nick_Van_den_Bleeken@inventivegroup.com
> 
> 
> *Ulrich Nicolas Lissé <unl@dreamlab.net>*
> 
> 09/16/2008 11:35 AM
> 
> 	
> To
> 	Nick_Van_den_Bleeken@inventivegroup.com
> cc
> 	XForms <public-forms@w3.org>
> Subject
> 	Re: Analysis of the effects of moving to XML Events 2 for XForms 1.2
> 
> 
> 	
> 
> 
> 
> 
> 
> Nick,
> 
> thanks for the analysis. I already sent an email with questions about
> the naming in XML Events 2 to the Forms and XHTML 2 lists some time ago
> [1]. Maybe we can use this as a starting point for discussion.
> 
> Regards,
> Uli.
> 
> [1] http://lists.w3.org/Archives/Public/public-forms/2008Aug/0031.html
> 
> Nick_Van_den_Bleeken@inventivegroup.com wrote:
>>
>> All,
>>
>> After a detailed analysis of the effects of moving to XML Events 2[1]
>> for XForms 1.2 I came to the following differences between the action
>> module, which was based on XForms 1.1 and XML Events 2:
>>
>> Events attribute group
>> ===================
>>
>> * The 'taget' attribute is renamed to 'targetid'
>> * phase has extra values 'bubble' and 'target'
>>
>>
>> The dispatch Element
>> ====================
>>
>> * Element is renamed to 'dispatchEvent'
>> * The 'name' attribute is renamed to 'raise'
>> * The 'target' attribute is renamed to 'to'
>> * The delay attribute isn't supported
>> * 'name', 'target' and 'delay' can't be dynamic (xpath-expressions)
>>
>> Extra functionality in XML events 2
>> ========================
>>
>> * addEventListener : allows the addition of a listener at run time (also
>> introduces the declare attribute on listeners)
>> * removeEventListener : allows removing  of a listener at run time
>> * stopPropagation : action that stops propagation of an event (to
>> support conditional stopping of propagation of events)
>> * preventDefault : action cancels the event (to support conditional
>> cancelation of events)
>> * optional script element
>>
>>
>> After doing this detailed analysis I come to the same conclusions we
>> came on the previous thread[2]:
>>
>>    XML events 2 = our Action module + some not hard to implement new
>> features + some renames - (delay, dynamic values for 'name' 'target' and
>> 'delay')
>>
>>
>> What does everybody think about me ( or somebody else) sending an e-mail
>> the XHTML 2 Working Group with Forms WG in CC asking why they have
>> chosen dispatchEvent over dispatch (how it was called in XForms), why
>> they  changed attribute 'target' to 'targetid' and call it 'to' on
>> 'dispatchEvent', and if they could add 'delay' and allow xpath
>> expressions for 'name', 'target' and 'delay'.
>>
>> Regards,
>>
>> Nick Van den Bleeken  -  Research & Development Manager
>> Inventive Designers
>> Phone: +32 - 3 - 8210170
>> Fax: +32 - 3 - 8210171
>> Email: Nick_Van_den_Bleeken@inventivegroup.com
>>
>> 1: <http://www.w3.org/MarkUp/2008/ED-xml-events-20080625/>
> <http://www.w3.org/MarkUp/2008/ED-xml-events-20080625/>http://www.w3.org/MarkUp/2008/ED-xml-events-20080625/
>> 2:
>> < <http://lists.w3.org/Archives/Public/public-forms/2008Aug/0029.html>
> <http://lists.w3.org/Archives/Public/public-forms/2008Aug/0029.html>http://lists.w3.org/Archives/Public/public-forms/2008Aug/0029.html>
> <http://lists.w3.org/Archives/Public/public-forms/2008Aug/0029.html>
> <http://lists.w3.org/Archives/Public/public-forms/2008Aug/0029.html>http://lists.w3.org/Archives/Public/public-forms/2008Aug/0029.html
>>
>> Inventive Designers' Email Disclaimer:
>> <http://www.inventivedesigners.com/email-disclaimer>
> <http://www.inventivedesigners.com/email-disclaimer>http://www.inventivedesigners.com/email-disclaimer
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content, and is believed to be clean.
>> --
>>
> 
> -- 
> Ulrich Nicolas Lissé
> 
> -- 
> 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, and is believed to be clean.
> -- 
> 

-- 
Ulrich Nicolas Lissé

Received on Tuesday, 16 September 2008 12:36:28 UTC