3d-force-graph VS troika

I used neo4j and https://github.com/vasturiano/3d-force-graph to make the visuals. Full graph is here: https://lewington-pitsos.github.io/committees/committees.html

Tool: The visuals were made with neo4j, and for the 3d graph I also used https://github.com/vasturiano/3d-force-graph

Oof, yeah, I hadn't even noticed that "rouster" somehow got almost perfectly overlapped onto the line linking "lobster" to "louster". I'd have to experiment with more layout algorithms and their parameters. In the meantime, the interactive viz (all I did was throw JSON at 3d-force-graph) gets around the layout problem by letting you freely rotate the scene and drag nodes: https://pjleimbigler.github.io/wordgraph/graph.html

The Examples section on this page shows many different types of 3D graphs. The Text example presents the graph as text nodes.

I will open source the whole thing at some point, but need to cleanup a bit first It is a simple page built using Svelte, and then the graph rendering is done using this library https://github.com/vasturiano/3d-force-graph

anyway it is a simple svelte app with typescript and was primarily made using this three.js library https://github.com/vasturiano/3d-force-graph i will open source my own code at some point but now it is a bit messy

thanks, it doesn't look like the right kind of visualisation, i'm looking for something to render lots of nodes (10-100s of thousands), so probably something along the lines of this would be better: https://github.com/vasturiano/3d-force-graph , except that 3d force graph determines the positions in space by fitting, rather than specifying positions. (having looked at it again, it may be possible to modify it to fix positions however..)

https://github.com/vasturiano/3d-force-graph is the library used, if anyone is curious

troika (specifically troika-three-text)

Text is relatively hard to render with WebGL and browsers have a limit, of usually 16 framebuffers that you can use for WebGL contexts. Our charts are written for a WebGL target so we don't want to use up that precious resource for text rendering. In our specific use case we usually have a large degree of control over the browser so we can configure it, but if the target is web we don't have that control. Grabbing a WebGL context also takes a significant period of time, usually a hundred milliseconds or more on my computer, and not displaying data in that time isn't a great user experience.

There's a great WebGL library for doing that on the web using any .ttf, .otf, or .woff font - https://github.com/protectwise/troika/tree/master/packages/t...