Re: IR and XPath DM implementation

Hi,

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

Great then, hope all goes well.


> 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
>

Sure, a wider discussion around external SCXML interfaces for practical use
and interoperability would be very nice. I guess it is not required for the
1.0 spec to go out though.


> 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.
>

I'm simply using typed definitions for the standard JQuery library. Keeping
it as simple as possible right now. Haxe has a number of interesting
selector libraries (usable outside JS context also) [1][2][3][..] ..so
interesting options maybe later, including XPath and what not. Here are
some recent Haxe/JS notes if interested [4].

Zjnue

[1] https://github.com/therealglazou/JSCSSPHX
[2] https://github.com/jasononeil/detox
[3] https://github.com/rockswang/hxquery
[4] http://io.pellucid.com/blog/the-benefits-of-transpiling-to-javascript