Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text tree view of nodes #383

Open
keyserj opened this issue Mar 25, 2024 · 0 comments
Open

Text tree view of nodes #383

keyserj opened this issue Mar 25, 2024 · 0 comments
Labels
accessibility clarity makes something easier to understand convenient makes the tool easier to use enhancement New feature or request exciter Feature that some users might really really like grasping large topic helps to better understand, use, build a topic that has a large number of nodes

Comments

@keyserj
Copy link
Collaborator

keyserj commented Mar 25, 2024

Describe your issue

If I want to scan through all nodes of a type, using the node types filter and looking through the diagram is ok, but seeing relations in this case is not necessary, and so the spread-out nodes doesn't provide extra value and is just distracting. It'd be nice to have a view that's more organized and compressed for reading through a bunch of nodes.

This is particularly nice if I just want to see all the questions, or all the sources and facts, or all the arguments that exist.

Solution you'd like

A tree view seems like it'd be good for this (example from vscode):
image

  • "Tree" format (vs diagram/table)
  • Having a tree view branch for the child relations of the node type could be a really convenient way to quickly add facts for sources, but this should probably be done separately to keep scope of this ticket narrow

Questions to answer

  • Should the tree view be filtered the same as the diagram is? That seems good and basically free to implement
    • might be excessive. at least should be able to choose which node types to show at the root of the tree
  • Can this be built via yml/JSON? Maybe this could be a human-readable way to edit a diagram? Maybe hard though because editing would require node id's in the yml?
    • could build the yml/JSON with id's to be human editable, and just have the tree not show id's
  • Could the tree view default to parent->child direction, but flip the other way via toggle? e.g. questions might be better parent->child, but sources seem sometimes better child->parent for adding facts
    • might be better to expand to both parent and child nodes, could distinguish via a symbol
      • would this be doable even if expanding parents/children could lead to infinitely-nested expansion?

Alternatives you've considered

No response

Additional context

No response

Technical ideas

  • maybe MUI tree view, but it looks a bit new and have some features that are paid-only
  • arborist also looks like a relatively popular tree view component for react

Technical questions

No response

@keyserj keyserj added enhancement New feature or request exciter Feature that some users might really really like clarity makes something easier to understand accessibility convenient makes the tool easier to use grasping large topic helps to better understand, use, build a topic that has a large number of nodes labels Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility clarity makes something easier to understand convenient makes the tool easier to use enhancement New feature or request exciter Feature that some users might really really like grasping large topic helps to better understand, use, build a topic that has a large number of nodes
Projects
Status: No status
Development

No branches or pull requests

1 participant