This content originally appeared on DEV Community and was authored by Charles Zhang
Overview
It's known from day 1 that Divooka documents need to support multiple graphs for things to be efficient, but it's not that straightforward to implementing that. There are lots of interesting things going on: serialization, file format, graph referencing, which we may talk about in the future. I would argue it's essential for scripting purpose, for dealing with file system entry reference is the last thing we worry about when trying to quickly get something done. In traditional programming languages, especially OOP ones, this is done by permitting defining multiple classes per file - it C#, it even allows you to define partial classes in separate files, which can be a source of confusion when not done well.
Objective
By storing multiple graphs inside a single document, it should also enable referencing such graphs/documents from other documents.
Implementation Progress
Today, the goal is to support navigating and switching between different graphs in Neo.
Preliminary work on refactoring graph editor to be a reusable component was already done before - in fact it's also essential for subgraph editing window to work.
Because when graphs are switched, the current view can stay the same, we also implemented a mini-map for easier identifying where we are.
Mipmap Behavior
The math is a bit tricky, so it's worth documenting here: ....
This content originally appeared on DEV Community and was authored by Charles Zhang
Charles Zhang | Sciencx (2025-07-29T01:29:14+00:00) DevLog 20250728: Multi-graph Navigation GUI. Retrieved from https://www.scien.cx/2025/07/29/devlog-20250728-multi-graph-navigation-gui/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.