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

Process Sam & RJ Feedback #21

Open
shamshirz opened this issue Feb 25, 2021 · 0 comments
Open

Process Sam & RJ Feedback #21

shamshirz opened this issue Feb 25, 2021 · 0 comments

Comments

@shamshirz
Copy link
Owner

shamshirz commented Feb 25, 2021

Interactive graph w/ more data

not knowing anything about the codebase, i found myself wanting to learn more about what these functions are trying to do - had the urge to mouse over a node and see if the docstring would pop up

  • Instinct to hover for more info about each fxn
    • Meta data - doc string, spec, etc

Graph Orientation

you may consider a horizontal flow to the visualization - i'm finding myself wanting to look at the 1st generation children of the root node in order, to get an idea of the flow of logic

  • Try some other display types, horizontal
  • Research how other people display graphs

Grok-ability

Lots of information on the page

…very difficult to make sense of in graph form (although I would claim that they're likely at least as difficult to make sense of in source code form, probably more)

Provide a way to select what's important (filter by depth)

But I think what I'd want is basic filtering functionality E.g. to be able to specify the number of edge traversals from the originating function node visible at once on the graph

  • Where 1, for example, would mean show me all of the functions called directly by this one
  • 2—all functions called directly by this one and all functions called directly by those

Filter by branch

But yeah. I'd also like to be able to filter by just one "branch" of the original function

  • Idea: would this be like folders in a graph? You can close it, and we may say how many outgoing edges exist, but don't display them

Insights

Can we provide "areas of interest" based on what a good graph pattern might be

I think it could be huge if you could come up with some heuristics like that. At that point you could do even better than say "look at this graph to see if you have lots of the same arrow pointing between the same two nodes," you could encode it!!

@shamshirz shamshirz changed the title Sam & RJ Feedback Process Sam & RJ Feedback Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant