-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add configuration options to Graph for usage by a Renderer #10
Comments
Copy-pasting the relevant section of my comment in ticket #6:
The Perhaps even better, we should consider a bigger cleanup and move everything to |
Moving everything to graphviz is a bad idea as we have more output engines: GraphML, Graph API (Drupal) which all need Graph and or global Vertice or Edge (meta) data. Graph API uses views to get it's Graph data and knows which engine + layout meta data is needed. I want to use Graph for that next hand over the Graph to the right engine GraphViz / D3 / Graph Phyz / The Jit which then process the requested layout (dot/neato/force directed/space tree/etc). |
Thanks to your input in #12, we now have a temporary working branch I also added the helpers IMO the current implementation of Other than that, this ticket can probably be considered resolved. |
Opened PR #22 to merge the above-mentioned branch. |
As a side note in #6 we need to set some attributes when defining the Graph for later rendering. We have covered this for Vertice and Edge but not for Graph.
Why not mimic the GraphViz way to set global aka Graph level stuff?
This way we can define general Vertice and Edge attributes in one go.
The text was updated successfully, but these errors were encountered: