Hi developers, just a share. I’m a Java developer and a graphviz user, I wrote a tiny version of graphviz in Java, I’m not sure if this is interesting : GitHub - jamisonjiang/graph-support: Java re-implementation of tiny graphviz
Can you describe (even at a high level) what parts of Graphviz you cover/reproduce (and what parts you don’t)?
I noticed good-looking “ortho” edges. Maybe Graphviz should reverse-engineer your code.
Briefly describe cover and not cover:
only java api, still not support dot;
svg and Java objects (to facilitate the program to extract some layout information)
Some commonly used fixed shape and dynamic shape like record | mrecord | regular_polyline;
Support NONE | ROUNDED | SPLINE | LINE | POLYLINE | ORTHO
Support table structure;
In addition, since the api uses strongly typed Java, all the attributes that can be set represent all the features that can be supported, and the rest are not supported.
Ortho route In my test, I think graphviz does a better job in most cases, especially in the scene of separating line segments and avoiding bending. I compared some other projects that can perform Ortho layout. Graphviz I feel it’s the best.
In the implementation of graph-support, I think the only thing better than graphviz is the handling of labels, because I found that grahviz ortho does not seem to support labels, and labels are not always placed next to the lines. Other than that I feel that graphviz is always the better side of the Ortho route (in my tests).
Hi Jamison, that’s great!
We are about to add a GraphViz based visualizer in our Java project GitHub - kovzol/Java-Geometry-Expert: Java Geometry Expert.
It would be great to try out your project as a possible use case.
There is now a GraphViz export but we would like to show the graphical output directly in the application. Of course, the program should work on multiple platforms (Windows, Mac, Linux). So it is crucial to use a platform independent solution.
Do you think your library could be an option?