That's really well done; I wish I had that in the program I'm working on. I ended up traversing my data structure and making a graphviz file, then doing it again after the manipulation I was testing in order to verify that it worked correctly. That works, but it really doesn't scale very well. Plus, the being able to see the individual steps of the algorithm would make it much more clear and obvious.

As an example, http://db48x.net/reposurgeon/pathmap-diagrams/generated-path... is one of the graphs I generated.

Have you published the server and the protocol anywhere? I'd use it even though I would have to write the client side myself. For my project it would even be desirable to write the client side twice; I'm porting a program from one language to another, and it would be amazing to be able to compare the implementations visually.

I am thinking about publishing the source etc soon. I have a mailing list for the project here. I’ve never actually sent anything out on it but I will announce the open sourcing there if you are interested. More info at http://symbolflux.com/luciditystory.html

I really like your projects! Especially your ideas in Tiled Text. I think we should think more outside the box and question our current way to write software.

Thanks! I hope to work on a successor to Tiled Text some day. I have a better sense of how much work is involved now, though. My current approach is to do a smaller project[0] with the potential to help fund work on more ambitious projects like Tiled Text and Lucidity.

[0] https://diskatlas.com/