StateS is intended to be a simple yet effective Finite State Machines (FSMs) tool.
Currently, StateS allows you to:
- Draw a FSM
- Simulate it
- Animated graphic representation
- Timeline for visualizing the evolution of variables values
- Verify it
- Export it graphically
- as PDF
- as vector image (SVG)
- as bitmap image (PNG or Jpeg)
- Export it to code (very experimental feature)
- VHDL
You can test interacting with a machine by loading file Demo.SfsmS (hit the "Download raw file" button on the top right).
You'll find compiled versions for both Windows and Linux on the Releases page.
Download and unzip the archive (or download the executable), then launch StateS_**.exe.
Latest versions of Windows are a bit strict on security, so you may obtain a security warning at opening. Indeed, StateS is a very small application, not very well-known. Windows sometimes automatically blocks this kind of programs when downloaded from the Internet. The warning window is built to make difficult running the executable: the execution option is hidden. I guarantee there is no malicious code in StateS, so to avoid the warning, right-click on the executable, choose "Properties", check "Unlock", and hit "OK".
The Windows version is built using MinGW Qt6 static package under MSYS2. The distributed version is a static (i.e. standalone, portable) 64-bits version.
Download the appimage, then run the file.
Note: on some systems, you may have to allow the appimage file for execution:
- From command line, cd to the folder containing the executable, and type
chmod +x ./<name of the file>. - Or graphically, right-click on the file, hit "Properties", search for an "Allow execution" or similar checkbox, and check it.
The Linux version is an AppImage file (a self-contained archive) built using a Debian virtual machine using appimage-builder. I had to resort to using Debian for the packaging as appimage-builder still struggles with ArchLinux (my base installation).
StateS is still in beta phase.
If you think you found a bug in StateS, please open an issue to report it. Make sure to check the known bugs file first.
Remember StateS in still under heavy development! It is not intended to be complete, or even useful for now!
StateS code license (GNU GPL V2) can be consulted using the LICENSE file, or at this address. Qt 6 is required to compile StateS, as well as a compiler supporting C++ 2017.
To obtain the code, use the following command:
git clone https://github.com/ClementFoucher/StateS.git states
To compile, use the qmake command on .pro file, then run make.
Under Windows, I recommand using the MinGW-based toolchain as Visual Studio has non-standard exception function signature If you still want to use VS, you'll have to edit the source to make the function signature match before compilation.
Most art used in the software is, or is based on, third-party art work released under open source licences. Authors information and corresponding licences can be found in the "art" folder in the git repository (here).