2 ms·
The problem here is that a fundamental question has not been answered, and as far as I can tell, has not been addressed by any of these visual environments: Wh
by WillAdams 3y ago
The problem here is that a fundamental question has not been answered, and as far as I can tell, has not been addressed by any of these visual environments:
What does an algorithm look like?
Herman Hesse alluded to this in his novel _The Glass Bead Game_, but despite decades of discussion and work, no one has made a convincing pysical representation of that system.
I love the concept, and have made some moderately complex attempts, e.g.,:
https://www.blockscad3d.com/community/projects/1430644 https://www.blockscad3d.com/community/projects/1430644
https://github.com/WillAdams/gcodepreview https://github.com/WillAdams/gcodepreview
it always devolves to screen size being out-paced by problem complexity --- one gets something of an inkling of this at:
https://scriptsofanotherdimension.tumblr.com/ https://scriptsofanotherdimension.tumblr.com/
Alternately, one can just break a project down into modules, but then the top-level view becomes the wall of text representation (albeit w/ nice lines or captured into pretty boxes) which one is ostensibly trying to escape.
I'd love to see someone succeed in this, and I've been using:
https://github.com/derkork/openscad-graph-editor https://github.com/derkork/openscad-graph-editor
quite a bit, and put a bit of money towards:
http://nodezator.com/ http://nodezator.com/