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

Improve graph layout for provenance visualization #14

Closed
remram44 opened this issue May 12, 2014 · 1 comment
Closed

Improve graph layout for provenance visualization #14

remram44 opened this issue May 12, 2014 · 1 comment
Labels
A-help wanted Attention: More help is needed here, as I am out of my depth C-graph Component: The graph command, showing the provenance as a Graphviz graph good first issue Newcomers welcome! This should be easy and self-contained enough for someone new to the codebase T-enhancement Type: En enhancement to existing code, or a new feature
Milestone

Comments

@remram44
Copy link
Member

remram44 commented May 12, 2014

Right now all the nodes, regardless of whether they are processes, system files or user files, are laid out together.

What I envision is:

  • Programs in the middle, one above the other. Also put subsequent executions underneath.
  • System files (i.e. package files) on the left
  • Other files on the right

The output is in GraphViz DOT format and done by graph.py

@remram44 remram44 added this to the 0.x milestone May 12, 2014
remram44 pushed a commit that referenced this issue Aug 3, 2015
@remram44 remram44 added good first issue Newcomers welcome! This should be easy and self-contained enough for someone new to the codebase hacktoberfest labels Oct 6, 2016
@remram44
Copy link
Member Author

Closing after #273 & #269

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-help wanted Attention: More help is needed here, as I am out of my depth C-graph Component: The graph command, showing the provenance as a Graphviz graph good first issue Newcomers welcome! This should be easy and self-contained enough for someone new to the codebase T-enhancement Type: En enhancement to existing code, or a new feature
Projects
None yet
Development

No branches or pull requests

1 participant