31 implements a way to publish events happening in the network in a publicly subscribable way. In order to make use of that we have to build a mechanism for catching these events and either analyze them or visualize. This issue is concerned with visualization.
Since events will be emitted by a SocketServer (#31), the visualization engine will simply implement socket client which connects to the server and gets all events that are emitted by it. Visualization itself will be done on a (preferably static) web page using cytoscape.js library, which allows to visualize creation, connection, properties change, etc.
kabirkbr
commented
6 years ago
31 implements a way to publish events happening in the network in a publicly subscribable way. In order to make use of that we have to build a mechanism for catching these events and either analyze them or visualize. This issue is concerned with visualization.
Since events will be emitted by a SocketServer (#31), the visualization engine will simply implement socket client which connects to the server and gets all events that are emitted by it. Visualization itself will be done on a (preferably static) web page using cytoscape.js library, which allows to visualize creation, connection, properties change, etc.