@Christian_Byron, The engines are small plugins that wrap existing public libraries and exposes them using a graphengine module (whose API I’m still finalizing). TW5-Graph is its own plugin independent of these wrappers, and it’s where 90% of my work went into this. One could create an SVG engine which creates and SVG image out of an input of nodes and edges. It could even be interactable, and even animated to some extent, though I expect there won’t be any physics.
@vuk I’ll fix that up typo with the next release. Thanks!
@jeremyruston I would be honored to have this plugin featured in the HelloThere tiddler. It’s already got stability set to “experimental” on the plugin, so that should be clear, but as long as people aren’t hacking my plugin or making their own engines, it’s pretty solid and good-to-go already.
A built-in TOC graph is definitely do-able. And I can have a built in widget for that soon. I haven’t done it yet simply because it’ll just take some work to make it look nice.
@Peter It can show relationships for a current tiddler. The feature already exists as its “live view”, which you might find to your liking. I should probably update the documentation to make this more readily discoverable.
@dongrentianyu A few dozen is perfectly fine for performance. Vis-Network can handle up to a few hundred before it starts getting choppy. Once I get around to finishing up Memgraph Orb as an alternative engine, it will be able to handle several thousand with no problem. But I’m going to polish the Vis-Network plugin to a shine first.
As for emulating Mermaid or GraphVis, it’s very likely I’ll be making a suite of <$graph.*> style widgets which do that stuff very simply. I’m just hoping to get some feedback first to get a sense of what people would like to see.
I recommend opening some feature requests on the TW5-Graph github page for specific requests. We’ll all be able to track them better there.
@fastfreddy Yeah… A lot of people are getting that, but I’m having trouble reproducing it. I’ve got some ideas (It looks like Felix Hayashi, the TiddlyMap creator, may have run into this too). I’ll push out a possible fix in a day or two.
@Mohammad tmap.id was such a problem. Some people discovered that when you mixed TiddlyWiki with lazy loading, it could delete your entire wiki. Those were some very angry bug reports.
@Lamnatos Thank you very much. I’ve always believed that documentation is equally important to the software itself.
@etardiff I’m sure I can do a “zoom to node” feature somehow. I just didn’t flag it as “first release” important. I haven’t looked into how Felix did it for TiddlyMap, and I’m not sure whether it was his own brew, or if it was vis-network specific. But either way, if he did it, I can do it too. If you’d like, you can open a github feature request for it. That’ll help me keep it in mind.
@TW_Tones I agree. In all my projects, when I started to get over 200-300 nodes in a graph, it became cumbersome, even if it was still rendering quickly. Either way, for those who want to have huge visualization, perhaps using more number-crunchy procedurally-generated nodes, Memgraph orb will actually be good for that once I get to polish it. It was meant for super large graphs.
)
