Spent a bit of time this weekend adapting a 3d graph visualizer to render JGF files and am working on a tool to turn abstract syntax trees into JGF files. This way I can view code as a graph and work on tools to manipulate it at the graph layer instead of just text. Gonna work on better labelling and display next week and then work on connecting between source files and highlighting node types / quick searching them
@brandon do you have thoughts on how the transformation should work? VR gesture control is on the TODO list hut I'm not sure I'd want to dangle my hands in the air that long. I'm thinking operations would be around selecting nodes by type / label, graph traversal to "select" further nodes, then operations on the selected graph like renaming/replacing/duplicating.
@mauve I think of it like a graph database, so it should be able to do whatever a graph db can do, like EdgeDB. Queries, inserts, deletes, etc. Elements like cursors and selections are like functional lenses, which are essentially reified database queries (where you can use a query for both reading and modifying a selection).