graph should not write always an image

[spaceone]

We should split the graph() function. One function should write the image file (where one can specify also a filename/path). The other one should return the ascii-art. Both use cases exists. Both functions are very nice!

[prologic]

Actually... I'm thinking we should remove the image functionality and leave that to external tools. We should improve the "graphing" API(s) such that we have:

• graph() ASCII graph representation of the system
• dotgraph() DOT graph representation of the system
• ... Something that some kind of real-time JS graphing frontend can render

[ri0t]

Check this one out: http://cytoscape.github.io/cytoscape.js/demos/5b192c88616af2f75344/
I like it. Plays well with parent/child relations and can visualize handlers and possibly with few additional code even live events.
The library's home is here: http://cytoscape.github.io/cytoscape.js/

[prologic]

We should build a mini webapp with an API that drives data for real-time gendering of the system component grpah:

Maybe using this library: http://cytoscape.github.io/cytoscape.js/

Demo: http://cytoscape.github.io/cytoscape.js/demos/5b192c88616af2f75344/

[prologic]

@riot haha jinx; )

[spaceone]

@prologic
ec9f5b9
I don't know it it's possible to let the image e.g. be written into a io.BytesIO() ? Then one could give a file descriptor as argument.

[prologic]

Yeap you can use:

buf = io.BytesIO()
plt.savefig(buf, format='png')