I would like to propose a suggestion for the TODO list.
The vivagraph guide to use the library is very neat, I miss a step by step guide for ngraph that shows, without browserify but with 'vanilla approach', how to use ngraph modules - I would like to better understand how layout computation is de-coupled from rendering (done with viva, or three, or pixi... ).
I also would find useful an example to combine the library (or some of its modules) with a reactive component - maybe vue.js, that looks light and easier to be learnt.
Graph object can be already used to persist data and render the graph in other ways (not necessarily as a force-directed graph), but I think it would be helpful an example that shows how to extend some of its capabilities.
As example, observers on data binded to nodes or links, or to the graph on the whole - imagine you want to populate the graph dinamically (fetch new nodes from servers).
Hello,
I would like to propose a suggestion for the TODO list. The vivagraph guide to use the library is very neat, I miss a step by step guide for ngraph that shows, without browserify but with 'vanilla approach', how to use ngraph modules - I would like to better understand how layout computation is de-coupled from rendering (done with viva, or three, or pixi... ).
I also would find useful an example to combine the library (or some of its modules) with a reactive component - maybe vue.js, that looks light and easier to be learnt.
Graph object can be already used to persist data and render the graph in other ways (not necessarily as a force-directed graph), but I think it would be helpful an example that shows how to extend some of its capabilities. As example, observers on data binded to nodes or links, or to the graph on the whole - imagine you want to populate the graph dinamically (fetch new nodes from servers).