-
Notifications
You must be signed in to change notification settings - Fork 246
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 in support for graphviz diagrams #24
Comments
Sorry, read this as In case you are referring to Trying to decide what would be best :
@rich-iannone, your decision, but those are the options I see as viable. Any I am forgetting? |
That is confusing but I did mean viz.js, with which ongoing development is likely abandoned. However, it does everything it needs to do and is pretty well documented as far as examples. Rationale for inclusion to DiagrammeR was a bit difficult at first. I thought that it could exist as a separate package, but, since there are several input code methods available in viz.js for GraphViz, I thought: why couldn't it exist alongside the mermaid engine? Alright! That is it. I think there is more positive than negative from including this. If during development it doesn't work out very well, the viz.js support could be dropped. I'm definitely okay with giving it a try. Could be very interesting. |
I am impressed with On a separate note, we should be able to leverage
|
For simplicity's sake, I'm thinking that an auto-detection scheme will be less burdensome for the user. I have to look into |
Great! It's in! |
This is possibly a big one, and I wanted to get some opinions on this. If we add the viz.js library, we can essentially have graphviz diagrams defined using one of several layout engines like "dot", "neato", "circo", or "twopi". Graphics would be rendered as SVG. The examples of the types of diagrams using dot alone look very nice. I think that getting this in early would set the package up for great things down the road. Then, a very strong focus on documentation and ease-of-use enhancements will be needed.
The text was updated successfully, but these errors were encountered: