Eliminitate dependency on Cytoscape?

[feliksik]

It seems this project is doing some really cool stuff. I used your fscose algorithms before, but I abandoned cytoscape since and I'm experimenting with a different visualization library now. Also, I think your goals of hyse may be very suitable for my usecase.

Unfortunately, your code seems to be dependent on cytoscape, also using the cytoscape-node data fields to store some algorithm values.

Would you be interested in reducing the dependency on cytoscape, to make your algorithm more broadly usable? (I don't think this should be very hard, but I'd be happy to offer ideas on how to achieve this).

[ugurdogrusoz]

Thanks @feliksik That's a very good idea. In fact most of our algorithms are suited for this kind of a separation. We will work on this when we have the time and resources.
If you don't mind me asking, what renderer are you using or you think people use these days for graph visualization components?

[feliksik]

I'm not sure which are the most popular, but GitHub stars can be an indication. React-flow, vue-flow, Rete.js, react-diagrams, and probably others seem to be useful libraries that are fairly modern and have good html support, which dus not seem to be the case for cytoscape.
Not that some of them position themselves as diagramming libraries for flows, but basically they are graph libraries, and also used as such (can also be for non directed graphs).
If you do want to be more framework independent, but you're not sure how to go about it, feel free to get in touch with me and I can tell your more.