News for hackers. Stuff that matters.
Re:Ask HN: Give feedback on my project and I'll do yours by karmakaze on Friday July 02, 2021 @10:43AM (#27712148)
It took a long while to 'get' what it can do, or how it's doing it. I started out thinking it was a list of lists. After playing with it some, realized that there was no 'nesting' and that all nodes are 'at the same level'. Ended up with the model being a directed acyclic graph (DAG).

I made this structure:

    / a1 / a21
  a - a2 - a22
    \ a3 \ a23
Then wanted to make a node that follows a1, (a21, a22, a23), a3. [I do realize that the (a21, a22, a23) grouping is only in my head.] So I selected each of those and clicked the '>' button and ended up with:

    /------ a1  \
  a ------- a3  \\
    \     / a21 -- b
     \ a2 - a22 //
          \ a23 /
This is the graph I was expecting but not laid out as I expected. Showing a grid gives the sense that you are working in a spreadsheet mode with some control where things go. It would be better to show nodes and edges with arrows that rearrange as the graph is changed to more closely set expectations.

One thing that I really wanted was a grouping mechanism where I could treat a subgraph as a node. But then a list of lists fits better than a DAG. What sort of information would a DAG suit better than a list of lists? My above example would be [a, [a1, [a2, [a21, a22, a23]], a3], b]. It seems what's lost is the ability to fan-in from arbitrary nodes and not a single group.

My main feedback point is that the layout I choose also encodes information additional to the actual graph. For that reason if I were to want something more than a list of lists would go for a drawing tool.

I had/have many projects but none that I'm actively working on. If I get to that point, I'll do as you've done and post a feedback for feedback post.

Re:Ask HN: Give feedback on my project and I'll do yours by escot on Friday July 02, 2021 @12:34PM (#27713718)
Thanks for your detailed look at it. Im glad you got something working, but I agree its not great it was so confusing at first. Youre right that its a DAG, like how many flowchart tools represent the data.

> grouping mechanism

This would be cool. I want to nail down the basics before adding more features. For most of my use cases I havent found it to be a show stopper, but once it can support larger graphs it will be required.

> the layout I choose also encodes information

Thats true however Im trying to make a tool optimized for speed. Manually adjusting layout doesnt help with that. It should feel more like editing a text doc where everything is done from the keyboard. However, I could see adding layout adjustment as a final step in producing some visualization you want to share.

Thanks again. And please reply here with a project, or email/tweet me (bio).

Re:Ask HN: Give feedback on my project and I'll do yours by karmakaze on Wednesday July 07, 2021 @06:17AM (#27759399)
I do recognize that this is an early sneak peek and it will be interesting to see how it evolves. The thought about grouping wasn't merely to deal with larger graphs, but rather if it was the core way in which organization happens, I believe that it would 'click' in the user's mind and produce autolayouts that more closely resemble what the user had in mind.