feat(editor): finalize M2 content workspace UX

This commit is contained in:
Rbanh committed 2026-07-22 17:14:07 -04:00
1 parent 93e23ba194
commit 106d947c98
69 files changed
+5893 -4343

No files matched your search

@@ -65,6 +65,12 @@ result.
base. Promotion requires a resolved project or imported Material base.
- Ordinary editor/runtime loading is read-only. Registry, project-settings, and scene migrations
run only through the explicit transactional project upgrader.
- Editor thumbnails use typed content-addressed artifacts under managed
`assets/.thumbnails/<version>/` storage. Their visual signatures cover source/dependency bytes,
resolved Material inputs and textures, custom shader files, subasset identity, and the studio
renderer version. Normal catalog invalidation revalidates the signature while retaining the
last-good GPU image; replacement publishes atomically after a valid render/readback. These
artifacts are editor-only, untracked, watcher-excluded, and absent from packages.
## Consequences
@@ -79,9 +85,10 @@ result.
imported source because failure uses the project/engine fallback deliberately.
- One cached DefaultGrid/emergency handle covers repeated primitive and mesh hydration, so missing
assignments do not grow the material asset stores.
- Thumbnail cache ownership includes the backing Egui image registration. Replacement, retry, and
catalog invalidation explicitly release the last registration before a new studio render owns
the key, preventing refresh-driven GPU resource growth.
- Thumbnail cache ownership includes the backing Egui image registration. Replacement releases the
superseded registration only after the new artifact is usable; manual retry/full teardown release
it immediately. Catalog refresh retains it as last-good while revalidating visual signatures,
preventing both refresh flicker and hidden GPU resource growth.
- File operations and imports must be staged transactions that update authored references,
registry state, derived manifests, and runtime catalogs together.
- Ordinary asset-property edits use the explicit dirty-document and two-phase publication boundary
@@ -114,9 +114,34 @@ field, vector, selection, and overlay components across the Inspector. Built-in
dispatch through the registry and share one clipped actor-body scroll owner; domain behavior stays
outside the visual primitives.
The Content Browser is the next migrated workspace. Its Penpot reference deliberately includes a
36 px standalone title row, but the production dock tab already owns that identity; docked content
therefore renders the remaining 55 px single-row toolbar at wide widths rather than duplicating
chrome. Compact composition uses the exported 88 px two-row toolbar, starts with the content grid,
and exposes mutually exclusive Sources and Details drawers from explicit actions. Wide composition
uses fixed 216 px Sources and a 290 px default resizable Details pane around a flexible content
lane. The 56 px content heading precedes one continuous row-major card stream in which folders and
assets share the same bounded card footprint. Toolbar, breadcrumb, content header, cards, Details
identity, and the catalog/processing/selection footer consume the same semantic tokens and return
actions to the owning editor module. Long identity and dependency paths use the exported bounded
two-line Details geometry rather than unbounded egui wrapping or a single unreadable clipped line.
Those presentation functions live together in
`editor_ui::content_browser` and are invoked by both the production panel and the UI Gallery;
`editor::ui::asset_browser` remains the sole owner of project queries, selection, transactions,
thumbnail scheduling, and action resolution. A fixture-only Gallery body is not valid evidence for
production conformance.
The 1240 px toolbar remains the standard-wide reference. A separate 1600 px expanded reference
exposes sort and thumbnail scale in the toolbar at the 1400 px production breakpoint; standard and
compact layouts retain those controls in overflow. Card scaling preserves a fixed 40 px identity
footer and changes only the preview footprint, with square cached artifacts aspect-fitted rather
than stretched. Sorting and scaling are presentation operations and never mutate authored content.
## Consequences
- New editor UI has one reviewed visual vocabulary rather than panel-local approximations.
- Standalone design/gallery boards and docked production panels share one component without
duplicating dock-owned title chrome.
- Theme colors have one runtime owner and one design-side asset vocabulary; the material panel does
not carry a private blue/teal palette.
- The 620 px and 420 px geometries are deterministic and unit-testable. The Inspector has a 420 px