Moves to using Graphviz instead of D3 #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Creates a graph containing everything rather than a tree that only shows extends. Changes line_stream so that block tags and other non-relational data can be represented.
Changes graph.Graph() to use extend_edges as a flat list instead of tree
Removes D3 and existing graph.js code. Removes sidebar. Adds viz.js library Adds basic viz.js integration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This means we can save a dot file locally and use the dot commandline tool, and in the view, we can use the viz.js tool. With this pull request in place, the extends and includes are shown in a directed graph. There is now parsing of the block tags but I haven't messed with adding them to the graph. It shouldn't be too hard though.