Gui.cs VS Stateless

Thanks but I'm sticking with Terminal.Gui

Used this neat library to handle the GUI gui-cs/Terminal.Gui: Cross Platform Terminal UI toolkit for .NET (github.com)

Terminal.GUI - cross platform terminal UI for .NET: https://github.com/gui-cs/Terminal.Gui

Two I've used are Terminal.Gui for .net https://github.com/gui-cs/Terminal.Gui and BubbleTea for Go https://github.com/charmbracelet/bubbletea

In that case you can use console (https://github.com/gui-cs/Terminal.Gui) to make games.

As you can see the tool is always integrated into the terminal because it has built on a cross platform UI toolkit based on a fantastic open source project called Terminal.Gui. Now you can select the objects by using space bar and than confirm the selection with enter. The result will be:

C# - https://github.com/gui-cs/Terminal.Gui

Since you mentioned minimal GUI, have you thought of a TUI? I haven't spiked it out but I would guess Terminal.Gui would work with Native AOT

I've had to resort to make TUIs with https://github.com/gui-cs/Terminal.Gui because there's no sane way to make a GUI app in Linux without a 300-files boilerplate or obscure languages.

I like this method and state machines in general. Makes it more easier to reason about complex software. Also, ithe f the state machine gets bigger (more states) in the past I have used the Stateless library which is very good. But what you described above is perfect for managing the state of a menu system.

After using stateless for three years, my conclusion is that I cannot imagine a scenario, where it makes sense to use it.

This is a great article. Here is the Stateless library he is writing about. The link to the library is kind of buried in the middle of a sentence.

Yes! And we're using one. https://github.com/dotnet-state-machine/stateless We're creating the configuration dynamically based on how the user wants his workflow to work.

Stateless is my go-to state machine library for .NET. It's reasonably advanced but can also be very simple if you don't need the more advanced features.

I'm playing around with this library for a medium sized state machine I'm setting up, and it has this functionality. I think explicit state machines are a good use-case for having an actual diagram, since they can take up enough space that it becomes hard to build a mental map from reading the code due to locality issues.