rich-cli VS svgbobrus

I hope he doesn't mind, but the creator of Rich and Textualize is a good guy, and Scottish: https://www.willmcgugan.com/about/

https://www.textualize.io/

https://github.com/Textualize/rich

You are using print statements too much. I understand the use due to it being a CLI application but still I suggest you look at textualize.

For more than a year I have been refactoring coBib, getting rid of its original ncurses-based TUI in favor of a more modern and a lot more maintainable textual-based TUI. Developing it has been a lot of fun and I must say that the team over at Textualize is doing a great job at developing libraries which are somehow very powerful and extensible while still being easy to use!

Will McGugan is among the most well-known Python developers. He's the author of Rich, a library for formatting output in the terminal. It's used, among others, by pip, and has more than 40K stars on GitHub. In 2021, Will started building Textual, a TUI (text user interface) framework based on Rich. At the end of the year, he founded the company Textualize.

The future of the command line is something along the lines of what these guys are doing:

https://www.textualize.io

IF you ever wanted to build rich User Interfaces that work in the terminal with mouse support written in Python, then Textual is the Library for you.

If you change your mind about Python there's textual+rich, https://www.textualize.io/.

I recently had to draw some diagrams for documenting something. After looking at various Markdown-friendly options I landed on svgbob[1]. I believe it's a superior solution to these kinds of graph drawing tools for Markdown for one specific reason: the code is still readable. When I go to look at a Markdown file I don't always open the output. I will commonly open up a README file in Vim or just cat it to the terminal. In this case diagrams like those in this post is next to useless. I'm not going to read through some complex drawing definitions and try to visualise the results. With svgbob (or Typograms[2] or any of the other similar options) you can still read the Markdown text document and see the diagrams which is great!

Of course this comes with a tradeoff, drawing the diagrams can be a bit of a pain. But I believe this can be solved by a good Markdown editor or editor plugin. Alternatively a spec like this could be converted into an svgbob-compatible diagram.

[1]https://ivanceras.github.io/svgbob-editor/

Online playground svgbob-editor is also updated to use the latest version of svgbob. It is however a painfully slow to edit the diagrams from there, so it's better if you draw the diagram somwhere else and paste it to there.

There’s Svgbob. Plus when it comes to more complex diagrams or graphs where creating the ASCII art by hand in can be quite finicky, there’s a number of tools (including drawing tools) to make creating ASCII art much easier.

https://ivanceras.github.io/svgbob-editor/

svgbob

Since the post contains ASCII art, let me recommend you svgbob :)

The app can now render Svgbob code blocks (https://ivanceras.github.io/svgbob-editor).