dummyVariable here
shoudl occur after dummyVariable last
registerCustomActionTags
and I will plan to fix this soon
@jbeard4 Oh understand. So far everything worked out.
1) "dummyVariable last" in <onexit> and "dummyVariable here" inside <transition> so as per SCXML rule, if I am not wrong,
while transitioning out from the state , sequence of execution : <onexit> of source state, <transition> executatable content
and then <onentry> of target state..
2) We wanted to use the ramp in parallel to the main execution i.e. in a separate thread.But it was pointed out to me that javascript is a single thread framework. Hence I decided to use uscxml- SCXML interpreter and transformer/compiler written in C/C++,
just to compare input and output files in the ramp. All credit goes to Korel for this :)
@Mumbasms Yes, in 2010 I developed an early version of SCION (then called scxml-js) as a project for the Apache Software Foundation as a part of Google Summer of Code, and this was implemented as an XSLT pipeline, such that it transformed SCXML to Javascript. I wrote a paper about it, which you can read here:
Slides are here:
Here is the source code:
http://svn.apache.org/repos/asf/commons/sandbox/gsoc/2010/scxml-js/trunk/
Hope this helps.
I feel like there were some pretty good ideas in that project. It would be neat to extend it to support multiple language compilation targets, like Ragel:
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2005/07/scxml
https://www.w3.org/2011/04/SCXML/scxml.xsd"
xmlns:conf="http://www.w3.org/2005/scxml-conformance"
<script>
, @expr
, etc), or validate referenced javascript variables against variables declared in your <datamodel>
Hi @AbdallahNasser, here is a rough outline of the approach I would recommend taking to bring the @scion-scxml/eslint-plugin up-to-date. @scion-scxml/eslint-plugin is based on eslint-plugin-html:
https://github.com/BenoitZugmeyer/eslint-plugin-html/
@scion-scxml/eslint-plugin should be brought up to date with the changes in the latest eslint-plugin-html version. I would recommend diffing eslint-plugin-html version v4.0.6 to latest tagged release v6.2.0, then applying the relevant changes to @scion-scxml/eslint-plugin. Then the @scion-scxml/eslint-plugin can be tested locally with eslint. I would recommend using the command line version of eslint, rather than trying to use vscode integration for this.
I looked at this some time ago, and this seemed like a good approach, but did not have time to finish it. Let me know if you have any questions and I will attempt to help answer them.