Finite State Hine Editor Portable Across The

With XComponent you can create services fully designed using state machines.

Sure, youll start with a boolean, then two, then youll need to manage three states and there will be an invalid state to avoid then youll just consider quitting all together.;) Stateless is a simple library for creating state machines in C code.

They achieved this not by targeting.NET Core but by writing to the.NET Standard.

Just like API levels in Android abstract away the many underlying versions of Android,.NET Standard is a set of APIs that all.NET platforms have to implement.

Finite State Hine Editor Portable Across The

Even better, the folks who wrote Stateless 3.0 targeted.NET Standard 1.0, which is the broadest and most compatible standard - it basically works everywhere and is portable across the.NET Framework on Windows,.NET Core on Windows, Mac, and LInux, as well as Windows Store apps and all phones.

Sure, theres Windows Workflow, but it may be overkill for some projects.

In Nicholas Blumhardts words:.over time, the logic that decided which actions were allowed in each state, and what the state resulting from an action should be, grew into a tangle of if and switch.

Inspired by Simple State Machine, I eventually refactored this out into a little state machine class that was configured declaratively: in this state, allow this trigger, transition to this other state, and so-on.

You can certainly describe high-level business state machines, but you can also easily model IoT device state, user interfaces, and more.

Even better, Stateless also serialize your state machine to a standard text-based DOT Graph format that can then be generated into an SVG or PNG like this with.

Its super nice to be able to visualize state machines at runtime.

Modeling a Simple State Machine with Stateless Lets look at a few code examples.

You start by describing some finite states as an enum, and some finite triggers that cause a state to change.

Like a switch could have On and Off as states and Toggle as a trigger.

A more useful example is the Bug Tracker included in the Stateless source on GitHub.

To start with here are the states of a Bug and the Triggers that cause state to change: enum State Open, Assigned, Deferred, Resolved, Closed enum Trigger Assign, Defer, Resolve, Close.

For example, if a Bug is triggered with Assign you can pass in Scott so the bug goes into the Assigned state - assigned to Scott.

State state State.Open; StateMachine machine; StateMachine.TriggerWithParameters assignTrigger; string title; string assignee.

But as this is written (you can change it) you cant close a Bug that is Open but not Assigned.

He is a failed stand-up comic, a cornrower, and a book author.

But its good to know whats on the market and that more and more of these libraries are migrating to netstandard.

In behaviour, the generated state machines would be similar to the ones generated by this library, including the firing of events for state transitions.

One thing my T4 template is missing compared to this is parameterised triggers.

It doesnt have DOT graph output either, though that would be really easy to add.

The T4 might have the edge for when there are design changes to the states and transitions, as a lot of boiler-plate code will be rewritten automatically, whereas it looks like youd have to do more of that by hand with the fluent API, but the T4 cant take care of it all and manual changes would still be required.

Finite State Machine Editor For Mac