W3C home > Mailing lists > Public > www-voice@w3.org > October to December 2014

Re: IR and XPath DM implementation

From: David Junger <tffy@free.fr>
Date: Sun, 26 Oct 2014 19:48:47 +0100
Cc: "www-voice@w3.org (www-voice@w3.org)" <www-voice@w3.org>
Message-Id: <8A9D7664-0827-4E4E-B0AB-AED6AA37D250@free.fr>
To: Zjnue Brzavi <zjnue.brzavi@googlemail.com>
Le 26 okt 2014 à 18:15, Zjnue Brzavi <zjnue.brzavi@googlemail.com> a écrit :
> 
> Glad to hear there is someone else willing to make the final push for DOM events.
> I don't have much time for this either, so hoping we can stick to supporting assertions 1-9 as mentioned by Jim.
> In case it helps, here are the applicable routines in my implementation [1][2][3][4].

Sure. JSSC already covers most of that, though the details differ slightly. Should be really simple to fix.

One thing that's not in the spec is the name and arguments of the method exposed to external code to queue (DOM) events into the interpreter. It would be nice if we agreed on some of our API. In JSSC that method is called fireEvent and you can pass it a DOM event (among other things).
http://www.jsscxml.org/api.html#methods

Maybe you want to look at my heuristics to determine whether to parse target as CSS or XPath, see if we're interoperable in case you want to suport both (I see you're passing the target to JQuery, do you know how it interprets it?):
https://github.com/Touffy/JSSCxml/blob/master/SCxmlProcessors.js#L44-L75
JSSC instances are always attached to an Element in the parent HTML document so that elements serves as the default target and the starting point for relative XPaths.

			David
Received on Sunday, 26 October 2014 18:49:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:45 UTC