- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Fri, 4 Apr 2008 07:59:55 -0700
- To: www-forms@w3.org
Done. http://www.nabble.com/Suggestion-for-XML-Events-2%3A-listening-to-events-in-a-separate-document-td16488849.html -Erik On Feb 26, 2008, at 5:11 PM, John Boyer wrote: > > Hi Erik, > > I don't think so, unfortunately. > > The instances are *separate* running DOMs from the main document > where event listeners would be expressed, and their is no way with > XML events to indicate that you would like to listen for something > to happen in another document. > > Actually, you should send that along as an XML Events 2 suggestion > to www-html-editor > > Cheers, > John M. Boyer, Ph.D. > Senior Technical Staff Member > Lotus Forms Architect and Researcher > Chair, W3C Forms Working Group > Workplace, Portal and Collaboration Software > IBM Victoria Software Lab > E-Mail: boyerj@ca.ibm.com > > Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer > Blog RSS feed: http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw > > > > > Erik Bruchez <ebruchez@orbeon.com> > Sent by: www-forms-request@w3.org > 02/26/2008 05:29 PM > > To > www-forms@w3.org > cc > Subject > Re: xforms:upload updating two parts of the model > > > > > > > Couldn't one register a listener for DOM Mutation Events? Does any > XForms implementation do this? > > -Erik > > On Feb 26, 2008, at 3:43 AM, Mark Birbeck wrote: > > > > > Hi John, > > > >> Not sure, but I think you may have suggested that an xforms-value- > >> changed > >> (XVC) will happen on the filename child element of an upload. > >> Just in case that's what you meant, the current spec does not > >> support that > >> because the ref used in filename is not a UI binding. Only full- > >> blown form > >> controls receive events from the model corresponding to their UI > >> bindings. > >> > >> It may work in an implementation that treats every ref as a UI > >> binding, but > >> then you have odd stuff happening like XVC events going to setvalue > >> and such. > > > > No...I'm definitely *not* saying that XVC applies to anything other > > than a form control. > > > > And that's exactly the problem! > > > > It means that for authors to register a handler that will perform > some > > action whenever a particular node has changed, they have to create a > > redundant form control: > > > > <style> > > .xvc-event-handler { display: none; } > > </style> > > > > <xf:output ref="node-to-watch" class="xvc-event-handler"> > > <xf:action ev:event="xforms-value-changed"> > > ... > > </xf;action> > > </xf;output> > > > > Best regards, > > > > Mark > > > > -- > > Mark Birbeck > > > > mark.birbeck@x-port.net | +44 (0) 20 7689 9232 > > http://www.x-port.net | http://internet-apps.blogspot.com > > > > x-port.net Ltd. is registered in England and Wales, number 03730711 > > The registered office is at: > > > > 2nd Floor > > Titchfield House > > 69-85 Tabernacle Street > > London > > EC2A 4RR > > > > -- > Orbeon Forms - Web Forms for the Enterprise Done the Right Way > http://www.orbeon.com/ > > > -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/
Received on Friday, 4 April 2008 15:00:36 UTC