Interesting, thanks for sharing. I‘ll have a look at it - at first it looks a bit like what PlantUML is doing, in case you know that. My project focuses mainly on the execution of the behavior.
Cool! Let me know when it's open. My past project focus more on the semantic analysis to avoid invalid/non-deterministic state-transition. As for syntax, I took inspiration from drawing language like PlantUML, graphviz, and state-machine-cat. The only difference is that the arrow can be either reversed or bidirectional.
Off<->On@ToggleClose<--On@ExitOff-->Panic@Exit
This simple change in arrow syntax make it easy to refactor and prototype a state machine.
Interesting, thanks for sharing. I‘ll have a look at it - at first it looks a bit like what PlantUML is doing, in case you know that. My project focuses mainly on the execution of the behavior.
Cool! Let me know when it's open. My past project focus more on the semantic analysis to avoid invalid/non-deterministic state-transition. As for syntax, I took inspiration from drawing language like PlantUML, graphviz, and state-machine-cat. The only difference is that the arrow can be either reversed or bidirectional.
This simple change in arrow syntax make it easy to refactor and prototype a state machine.
The very first version of Act, my state machine library, is now online on Github. See the following post.