Skip to content

[EPIC] Multi-theme GUI engine: layout-owned Default / Brushed Metal appearance #44

Closed as not planned

Description

@masarray

Goal

Implement a multi-theme Appearance system for the canonical ArSonMix GUI, initially studio-default and brushed-metal, without allowing theme packs to own layout. This is an implementation epic, not proof that the runtime engine exists.

Architecture and plan

Required principles

  • GUI core retains grid/flex/spacing/positions/hitboxes/interactions. Theme packs have semantic appearance tokens only.
  • Preserve 12 channel strips + MASTER, six FX slots per strip, dB alignment, physical fader and PAN assets.
  • studio-default must be pixel-equivalent to the latest approved GitHub main until further approval.
  • brushed-metal uses silver chassis/controls but FX insert and FX power remain glossy black-blue glass.
  • Switch theme without re-rendering mixer, restarting the engine or changing gain/mute/pan/FX state.
  • Store armix.ui.theme.v1 separately from audio/session snapshots.
  • Current CSS legacy cascade has !important; migrate property ownership before introducing layered theme bundles.
  • Test Chromium geometry at 1680x920, 1440x820, 1280x768, 1100x740 and 125%/150% Windows DPI.

PR ladder (separate reviewable PRs)

  • T0 Baseline screenshot/computed-style/geometry fixtures (no styling changes)
  • T1 Extract active material CSS from 10-console-legacy.css into component owner
  • T2 Semantic surface/control/state token consumption with default parity
  • T3 Static theme manifest, allowlist, compiler and build-time validator
  • T4 Theme manager + early bootstrap + persistence and safe fallback
  • T5 Compact accessible Appearance chooser (no toolbar collision or audio SETUP hijack)
  • T6 Optional strict dimension-matched fader/PAN alternative finishes
  • T7 Windows WebView2 persistence/native regression tests and user QA

Release gate

JS syntax, CSS + standalone parity, existing GUI lock/PNG tests, new cross-theme geometry/interaction tests, native CI. Production remains untouched until product-owner review and green checks. Real hardware audio FAT remains a separate concern.

Activity

  1. masarray commented on Oct 26, 2026

    @masarray
    OwnerAuthor

    Approved Brushed Metal CSS has now been preserved in draft PR #46. Future thread: read START HERE and exact adapter.css first. Build the original preview using scripts/render_brushed_reference.py, verify with tests/theme_reference_fixture_test.py. No CSS restyling from scratch is needed. The historical adapter is a visual fixture and not production theme code. Run T0 baseline, then migrate its existing material values into tokens T1–T3, add live switch T4/T5. GUI controls layout; FX Rack and FX power remain blue-black glass. Runtime theme engine still NOT IMPLEMENTED.

  2. masarray commented on Oct 26, 2026

    @masarray
    OwnerAuthor

    Current reference/handoff PR is now #48 on branch docs/theme-golden-source-handoff-20261026, rebased onto newer main; old #46 was superseded due conflicts. Exact adapter.css (Git blob 1086c285a44d2d06787a12ae809c1d4c5c80bb44), checksum manifest, preview reconstruction script, integrity test, full ARD and optimized next-thread handoff are included. Do not recreate metal styling. Implement T0→T5 from this preserved appearance reference with GUI-owned layout and FX-glass ownership.

  3. masarray commented on Oct 26, 2026

    @masarray
    OwnerAuthor

    Theme source preservation and handoff DONE, merged to main via PR #48 (merge commit 6b5ad42e56c0e5967a893df3d887ba08bf305169). The approved Brushed Metal CSS is preserved byte-identical at design-references/brushed-metal-v1.0/adapter.css, checked by SHA256/Git blob. Handoff: docs/THEME_ENGINE_NEW_THREAD_HANDOFF_2026-10-26.md. Preview generation script and test now available in main; Chromium UI smoke and Windows native CI passed before merge. This completes only preservation/ARD/handoff, NOT the T0–T7 runtime theme engine. Start T0 against fresh main, extract component material owners, migrate the exact reference paints into semantic tokens. Do not invent new CSS or copy reference !important overrides wholesale. FX Rack stays glass.

  4. masarray commented on Nov 2, 2026

    @masarray
    OwnerAuthor

    Closed as superseded legacy skin/theme implementation tied to old 12-channel L2 layout and outdated CSS ownership. Approved product GUI is now #271 (reference #278, V5 hardware material), and no parallel studio-default/brushed-metal appearance engine should be merged into the retired workbench. If Appearance becomes a requirement for the NEW console, define it against that GUI and its native/standalone parity as a separate new scope. Closing does not delete prior source/history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions