Why not writing rendering backend agnostic code and switch out backends as the library evolves? You can simply work with lines, points and text types, and decouple things from the visualization code completely. This way you could also use GLVisualize <http://www.glvisualize.com/>, which should help quite a bit with latency ;)
Am Donnerstag, 17. März 2016 14:17:15 UTC+1 schrieb Abhijith Anilkumar: > > Hi, > > I'm happy to announce the first registered version of NetworkViz.jl > <https://github.com/abhijithanilkumar/NetworkViz.jl>, a julia interface > to visualize graphs using ThreeJS.jl > <https://github.com/rohitvarkey/ThreeJS.jl> and Escher.jl > <https://github.com/shashi/Escher.jl>. The package is tightly coupled > with LightGraphs.jl <https://github.com/JuliaGraphs/LightGraphs.jl>. It > uses Escher.jl to interactively modify the visualization. The following > examples demonstrate what NetworkViz is capable of : > > > - WheelGraph Visualization > <https://www.youtube.com/watch?v=qd8LmY2XBHg> > - Code-Mirror example <https://www.youtube.com/watch?v=Ac3cneCRTZo> > > > I've planned to implement the following features in the future releases : > > - Implement different Graph Plotting algorithms > - Better Text Support > - Blink Integration > - Generalize the package (to work with packages other than LightGraphs) > > > I would like to take this up as a GSoC project and continue working on the > package. I would therefore like to ask if there is someone who would like > to be a mentor for this project? > > Please give your suggestions so that I can use it to improve the package > and make it useful for the community. > > Regards, > Abhijith >
