All Projects → cmars → statechart

cmars / statechart

Licence: MIT license
A rust implementation of statecharts: hierarchical, reactive state machines

Programming Languages

rust
11053 projects

Projects that are alternatives of or similar to statechart

qp-arduino
QP real-time embedded frameworks/RTOS for Arduino (AVR and SAM)
Stars: ✭ 37 (-9.76%)
Mutual labels:  state-machine, statechart, event-driven
qm
QM model-based design tool and code generator based on UML state machines
Stars: ✭ 54 (+31.71%)
Mutual labels:  state-machine, statechart, hierarchical-state-machine
Watermill
Building event-driven applications the easy way in Go.
Stars: ✭ 3,504 (+8446.34%)
Mutual labels:  reactive, event-driven
StateBuilder
State machine code generator for C++ and Java.
Stars: ✭ 30 (-26.83%)
Mutual labels:  state-machine, statechart
ThingML
The ThingML modelling language
Stars: ✭ 91 (+121.95%)
Mutual labels:  state-machine, statechart
Effector React Realworld Example App
Exemplary real world application built with Effector + React
Stars: ✭ 119 (+190.24%)
Mutual labels:  reactive, event-driven
Newbe.claptrap
This is a frameworks with reactive, event sourcing and Actor pattern as basic theories. On top of this, developers can create "distributed", "scale out", and "easy to test" application more simply. Claptrap and it`s Minions is on the way.
Stars: ✭ 163 (+297.56%)
Mutual labels:  reactive, event-driven
use-secret-code
Custom hook for adding cheat codes to your React app.
Stars: ✭ 16 (-60.98%)
Mutual labels:  state-machine, statechart
Beedle
A tiny library inspired by Redux & Vuex to help you manage state in your JavaScript apps
Stars: ✭ 329 (+702.44%)
Mutual labels:  reactive, state-machine
tsm
A Hierarchical State Machine Framework in C++
Stars: ✭ 30 (-26.83%)
Mutual labels:  state-machine, hierarchical-state-machine
simple-state-machine
A simple Java state machine for Spring Boot projects
Stars: ✭ 25 (-39.02%)
Mutual labels:  state-machine, statechart
Workflow Swift
A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines.
Stars: ✭ 92 (+124.39%)
Mutual labels:  reactive, state-machine
State Machine
🤖 A state machine library for Kotlin, with extensions for Android.
Stars: ✭ 72 (+75.61%)
Mutual labels:  reactive, state-machine
Pos
Sample Application DDD, Reactive Microservices, CQRS Event Sourcing Powered by DERMAYON LIBRARY
Stars: ✭ 207 (+404.88%)
Mutual labels:  reactive, event-driven
Workflow
A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines.
Stars: ✭ 860 (+1997.56%)
Mutual labels:  reactive, state-machine
ency
Enhanced concurrency primitives for Javascript.
Stars: ✭ 32 (-21.95%)
Mutual labels:  reactive, event-driven
Unity3D-ReactiveScriptables
ScriptableObject based framework / scaffolding that facilitates loosely coupled communication and automatic update propagation between MonoBehaviour components.
Stars: ✭ 25 (-39.02%)
Mutual labels:  reactive, event-driven
Workflow Kotlin
A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines.
Stars: ✭ 255 (+521.95%)
Mutual labels:  reactive, state-machine
Effector
The state manager ☄️
Stars: ✭ 3,572 (+8612.2%)
Mutual labels:  reactive, event-driven
cl-gserver
Actor framework featuring actors and agents for easy access to state and asynchronous operations.
Stars: ✭ 121 (+195.12%)
Mutual labels:  reactive, event-driven

statechart

Build Status Crate

A rust implementation of statecharts. Statecharts are a visual approach to expressing hierarchical state machines, useful for describing reactive, event-driven systems. Statecharts were originally introduced in Harel87. Harel07 gives background and context to the innovation and development of statecharts. For technical context, application to MDSD and practical systems design, see D. Harel and M. Politi, Modeling Reactive Systems with Statecharts: The STATEMATE Approach, (with M. Politi).

Current project focus

This crate initially aims to provide a statechart document model and interpreter, influenced by, and probably mostly isomorphic to the concepts, entities and behaviors described in the W3C State Chart XML specification. However, the focus is not full scxml compliance, but the following use-cases:

  • Rust macros for expressing and executing statecharts from Rust code directly.
  • Interpreter compatibility with futures & streams to support asynchronous execution.
  • Automating some useful, operational tasks with software agents, expressed as statecharts.
    • Personal assistants
    • Automated software operations, auto-{healing,scaling,alerting,reconfiguring}
    • Privacy and security, "situational awareness" for networked applications & devices
  • Performance, after usefulness and correctness

Possible areas of further interest

Applications which I am not actively developing for yet, but could be interesting and useful contributions:

  • no_std support for embedded applications. The kind of thing statecharts were invented for!
  • A compiler backend. Target LLVM or an FPGA!
  • SCXML compatibility, where it doesn't conflict with the above goals, and there's a good use for the angle brackets.

Copyright 2017 Casey Marshall

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].