ASCIIFlow Diagram Tool
asciiflow.com
asciiflow.com
I've embraced the diagrams-as-code world, with graphviz, plantuml, Structurizr DSL, AsciiDoctor Diagram, Mermaid, and WebSequenceDiagrams all having a place. It's even possible to generate SVG using ruby or any language with a decent SVG library.
Yes, I had to give up making my diagrams "just so", but the time I've saved not dragging around elements, trying to connect lines and arrows makes it worth it. Being able to commit them to source control as text rather than binary files that don't diff is a bonus
A new tool that has impressed me, though, is FigJam [1], which is a new type of document in Figma that's currently in beta. It's basically Visio, but with a fantastically intuitive UI and beautiful rendering style; super easy to draw boxes and lines and so on. Best of all, it's got real-time, web-based collaboration built in, and it's as solid as Figma (which is also fantastic).
Two questions about FigJam then:
1. What format does it store the saved files? Is it plain text, does it compress well, can it be diff'd?
2. Can I store the saved files locally and put them in the version control/CRM system of my choice, or are they all stored on Figma's servers?
It doesn't do auto-layout, which is fine, because nobody does that well anyway — ultimately, layout tends to be a "semantic" issue that tools can't automate.
You can import/export diagrams as files, but they're in a proprietary binary format. You can, however, export as SVG. And Figma does support versioning.
1, proprietary binary, it's not plain text, can't be diff'd doesn't compress as well as plain text at least.
2. files are stored on Figma's servers and I'm bound to their storage and versioning infrastructure.
This is another reason I have settled on Markdown, R Markdown driven documentation and even presentation. The 2 dimensional presentation created via Markdown and Revealjs is much faster and looks great and best of all it forces you to limit how much content to write in a slide and I don’t have to worry about layout.
[2] http://bakoma-tex.com/doc/latex/tikz-timing/tikz-timing.pdf
Asciiflow in VS Code - https://news.ycombinator.com/item?id=22840295 - April 2020 (23 comments)
ASCIIFlow Infinity - https://news.ycombinator.com/item?id=16051428 - Jan 2018 (56 comments)
ASCIIFlow Infinity – ASCII diagrams with export - https://news.ycombinator.com/item?id=9130756 - March 2015 (10 comments)
AsciiFlow Infinity: Powerful In-Browser ASCII Art Editor - https://news.ycombinator.com/item?id=7560599 - April 2014 (7 comments)
Asciiflow - https://news.ycombinator.com/item?id=7085133 - Jan 2014 (69 comments)
Asciiflow - ASCII Flow Diagram Tool - https://news.ycombinator.com/item?id=6365612 - Sept 2013 (1 comment)
Asciiflow - ASCII Flow Diagram Tool - https://news.ycombinator.com/item?id=3598177 - Feb 2012 (9 comments)
AsciiFlow - diagram & wireframe tool - https://news.ycombinator.com/item?id=2847177 - Aug 2011 (20 comments)
ASCII diagram creator - https://news.ycombinator.com/item?id=2651745 - June 2011 (39 comments)
┌───┐
│ │
│ │
│ I │
│ N │
│ │
│ │
└─┬─┘
│ ┌───────────┐
│ │ │
└───────────► OUT │
│ │
└───────────┘
OK. Works.Seems some hope for that https://stackoverflow.com/questions/3211801/graphviz-and-asc...
Seems to work well..!
I would probably use something else when modelling a solution but sometimes it really is best to keep the documentation as close as possible to the source.
I get that ┼ is a single point, and the logic would be more complicated if it were · or *.
However, I think in these cases the line segments should consist of - and |.
───
x┼x
┌──
│
┼x┼
x
┼I couldn't get it working on windows but it looks interesting and it's very old.
Good discussion here 10 years ago