Relatively intuitive once you get started. I love it! Are the graphs themselves relatively easy to make up? I could definitely see using these instead of excel for D&D maps.

It doesn't really do anything for me. I can't really get much out of it. That could be just a me thing, like I'm generally not good at this type of thing anyway.

Hi.

I tried it and it seams to work fine, i'm not someone who'd use this though so I can't give you good feedback.

@2 glad you can see the value in something like this as well! you can shoot me an email at [email protected] and I will email you when there are any major developments

@3 thanks! glad you like it. DnD maps are definitely a great use case for this sort of thing

@4 so as for a sighted person sending you an url with a graph you can look at. take a look at the demo/guide I link in #1. thr graphs are just embedded as part of the page and you press a button to enter one of them. I will explain how you create graphs in next post

@5 would you mind expanding on why you couldn't get any use out of it? maybe if you could tell me at what point you stopped understanding things or just got stuck? helps me to understand the cases where the viewer doesn't work well

@6 wow thats perfect! I was looking for exactly those sort of lists

Absolutely brilliant idea. A couple of things: seems a little verbose, which maybe good for learning how it works, but it would be nice to not feel like you're being flooded with information with each node. All I really need to hear is the name of the next node and its direction. I don't really need to hear that I can press F1 all the time. Second, maybe it would be nice to not wrap, or make wrapping a setting you can toggle. It's confusing to me when you reach the last node and it wraps back to the first node.

This is interesting and comprehensible for at least small examples.  I will have to play with the larger graph at some point to see how well it scales up.  Two things:

Having to press enter in order to expand what you're calling subgraphs is annoying and it seems that the table is always two columns.  Why not let right arrow expand indefinitely?  Right arrow on a node moves to the edges, right arrow on an edge moves to the target of the edge, left arrow takes you "back".

The left "column" which is always only one node seems superfluous.  It feels like down arrow should do something there.  I imagine that if right arrow always expanded then that would go away because left arrow always takes you back to where you were.  Maybe I missed something and that's not always one column.

It feels sort of  like a treeview but with a bunch of extra levels for no particular reason, if that makes sense.

@13 really appreciate the feedback. I think I get what you are getting at. tree views are a really neat design pattern, which I was initially considering to use, but then was inspired to model the UI more like a table because I wanted to be able to seperate different categories of information into different columns, where each column might be made up of multiple items.

I think you missed that if you navigate to a node's table, like if you are on kitchen in the parts column and press enter, the table in that instance has 3 columns: summary, undirected edges, and parent. to your point, the parent column does also like the summary column, just contain a single item, which is a link to its parent. in that way it is also kind of superfluous, since there could instead just be some "navigate to parent" keyboard command, but the value of having this tabular layout with columns I think comes in once you are dealing with a graph with directed edges or even a mixture of directed and undirected edges.

that's because when inspecting a node, it will have a seperate colunn for each edge type. so one column for its undirected edges, one for its outgoing edges, and one for its ingoing edges. I hypothesize (basing on some research as well) that seperating out that info will make accessing some information more efficient. using the manager hierarchy example from towards the bottom of the guide, if you want to figure out who someone is managing, then you just want to look at that node's outgoing edges and its other edges would just get in the way of answering that particular question.

but your tree view idea is totally valid. as I mentioned before, I was very much considering a similar idea to what you proposed, but I am hoping that this multi-column layout shows to have benefits, at least for directed graphs.

Just added another feature. Essentially made the history commands better. Now you can go both forward and backwards in history as far back or forward as you like, using Ctrl+Left/Right, analogous to going back or forward in web browser history. I think this can be useful for retracing your steps or just reviewing the path you have taken while going through the graph.

Note: before you could only go back in history one step and couldn't go forward in history at all. Also pressing backspace doesn't go back in history anymore, since ctrl+Left takes care of that now.