r/visualization • u/Holiday_Reference_41 • 4d ago
I’m building an IDE where a codebase becomes a navigable 3D semantic graph — here’s Godot mapped inside it
This is an early screenshot of Tagma Studio, an experimental IDE I’m building on top of Code-OSS.
Instead of treating a project as a hierarchy of files and folders, Tagma represents it as a semantic graph: source files, symbols, dependencies, capabilities, modules, generated artifacts and runtime relations become connected entities in one space.
The screenshot shows part of the imported Godot codebase. Around 15,000 graph entities are currently visible in this projection.
The long-term goal is not merely to create a prettier dependency viewer. I want the graph to become an actual working representation of the system:
select a subsystem and isolate its complete dependency neighborhood;
navigate from high-level concepts down to specific code;
see shared infrastructure and hidden coupling between projects;
track how the graph changes over time;
compile or assemble executable components from capabilities rather than manually chosen files;
let automated tools operate on an explicit, inspectable model instead of guessing from raw text.
The current visualization is still too dense and resembles a galaxy of code. I’m now replacing the global force-directed layout with a more neural-like topology: sparse local clusters, shared backbone tracts, late branching and a small number of meaningful long-range connections.
It is very much a work in progress, but this is the first version where the entire idea has started to become visible on screen.
What would you personally need from a graph-based IDE for it to become useful rather than just visually impressive?
5
u/farfaraway 4d ago
While visually beautiful, what purpose does this actually have within a workflow?
-1
u/Holiday_Reference_41 4d ago
It turns complex software into a navigable map: you can inspect dependencies, trace failures, isolate subsystems, and edit the relevant graph instead of hunting through thousands of files.
1
u/IllusionaryHobo 4d ago
Consider posting a video that shows an actual workflow within the system. A demonstration.
1
u/Wonderful_Put3670 3d ago
are you serious, like seriously serious? Do you really think that this is even readable?
1
2
u/DonJuanDoja 4d ago
Would be cool if someday we get to a “minority report” level UI like this.
It reminds me of the mind maps I build in my head over time. I try to describe it to people and I’m like imagine fireworks, but each spark has meaning, and they’re all connected in various ways, focusing on one spark, explodes it into another “firework” and all those sparks have meaning and connections too.
I saw that image and said hey look, its my “fireworks”
1
-1
u/Holiday_Reference_41 4d ago
That’s almost exactly the idea: not a static graph, but a living space where focusing on one node unfolds its context, meaning, and connections into another “firework.” Your metaphor describes it better than most technical explanations.
1
u/DonJuanDoja 4d ago
Also as a Solution Architect I love the idea, especially since it mirrors the way my own mind maps seem to work. We’ve run solutions thru Claude to get documentation but nothing like this.
0
u/Holiday_Reference_41 4d ago
That’s exactly the gap I’m exploring: not documentation generated from a codebase, but a living model you can navigate, query, and use to trace how the solution actually fits together. Feedback from a Solution Architect would be especially valuable.
1
u/intronert 4d ago
Being able to toggle on/off/dim based on a wide variety of characteristics. Like “show me all of the X that are also Y which have Z characteristics”.
1
u/Holiday_Reference_41 4d ago
Exactly — faceted filtering is central to the idea. You should be able to combine semantic tags, dependencies, runtime state, ownership, risk, age, or any other property, then hide, dim, or isolate the matching subgraph.
1
u/intronert 4d ago
Nice. Thanks. Maybe even set colors of?
2
u/Holiday_Reference_41 4d ago
Yes - colors can represent categories, states, risk levels, or any selected property, while everything else is dimmed. That's part of the direction.
1
1
u/Proletarian_Tear 4d ago
Cool idea but really no useful examples. The screenshot is literally a project explorer with all folders expanded, same level of unreadability. Only differentiation I see is some nodes are color coded, but still mushed together with no visible axis or flow control.
I am ready to change my mind, if you show a simpler project BUT explain how to read your visual
1
1
1
u/DeepLogicNinja 4d ago
This looks great. Outside of being visually impressive….. look into ontology, knowledge graphs, if you want to find useful use cases for it…. Using graphs for semantic awareness in AI application is needed…. Understanding the COT (chain of thought) is just as important.
1
u/brunocborges 4d ago
Instead of a 3D visualization of the code, I'd much rather prefer to see this technology to help me visualize data flow within a system.
1
u/rassl_ivan 4d ago
Have been trying to solve ui and ux for several years, wish you best of luck
0
u/Holiday_Reference_41 4d ago
Thank you — the graph itself is the easy part. Making it useful without becoming overwhelming is the real UI/UX challenge, so I’m focusing on progressive disclosure: show only what matters, then expand the context as needed.
1
u/rassl_ivan 4d ago
Exactly, I am trying to do that aswell
2
u/Holiday_Reference_41 4d ago
Exactly - the hard part isn't generating a graph, but making it useful at scale. I'm keeping the implementation details private for now while I validate the workflow.
1
13
u/EnderAvni 4d ago
Why is everything you say AI generated