Skip to content

The plan in space: each part a planet, its files its moons, around what it uses - #57

Merged
ngodzik merged 1 commit into
mainfrom
plan-space
Nov 8, 2026
Merged

ngodzik merged 1 commit into
mainfrom
plan-space

Conversation

@ngodzik

@ngodzik ngodzik commented Nov 8, 2026 •

Copy link
Copy Markdown
Owner

The plan view now opens in 3D, in the universe's space, as the database does.

  • Each part of the level shown is a planet in its layer's colour (cool foundations, warm tops, as the cards), larger the more lines it holds. Its longest files are moons on a ring around it; a file part has none.
  • The parts that use no other gather at the heart; the others stand in shells around it by their layers, each outside what it uses and near it.
  • Each link is an arc from the part that uses in to the part used, brighter for more imports, magenta when it goes through an API, red around a loop.
  • Pointing at a part lights what it uses (orange) and what uses it (cyan), with how much each link holds on a pill, and its files' names around its ring. A click glides the camera to it and lists its files; a double click opens it onto its own parts, and the way back in the title leads up.
  • 3D / 2D beside the title gives back the cards. The choice is the same as the database's, now shared.

What both scenes share moved to a module of its own, space: the shells and their layout, the camera, the body under the pointer, the names and the labels around a body. The window's flag for the database in space became the view in space, the plan or the database, which keeps the window drawing while either shows.

Tried in the window on a public project: its 13 parts at the top, then one of them opened onto its 93.

Tests cover the shells (each layer outside the one below, no body in another, joins given twice or to oneself, off a single plane, the bounds), picking, the labels' spread, the plan's scene (a part outside what it uses, its longest files the largest moons, a design laid out once) and the links' colours.

🤖 Generated with Claude Code

…at it uses

The plan view now opens in 3D, in the universe's space, as the database
does: each part of the level shown is a planet in its layer's colour,
larger the more lines it holds, its longest files moons on a ring around
it. The parts that use no other gather at the heart; the others stand in
shells around it by their layers, each outside what it uses and near it.
Each link is an arc from the part that uses in to the part used, brighter
for more imports, magenta through an API, red around a loop.

Pointing at a part lights what it uses (orange) and what uses it (cyan),
with how much each link holds, and its files' names around its ring. A
click glides the camera to it and lists its files, a double click opens
it onto its own parts, and the way back leads up. 3D / 2D beside the
title gives back the cards, the database's choice being the same.

What both scenes share moved to `space`: the shells, the camera, the body
under the pointer, the names. The window's flag for the database in space
became the view in space, the plan or the database.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ngodzik
ngodzik changed the base branch from database-planets to main November 8, 2026 17:22
@ngodzik ngodzik closed this Nov 8, 2026
@ngodzik ngodzik reopened this Nov 8, 2026
@ngodzik
ngodzik merged commit 9ebbaf2 into main Nov 8, 2026
5 checks passed
@ngodzik
ngodzik deleted the plan-space branch November 9, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant