bernardo/Nomarchy
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(system): nomarchy-control-center TUI

Browse Source 
Implemented TUI control center using gum. Added to systemPackages and rofi System menu. Verified: V1. Pending: V3 visual check.
This commit is contained in:
Bernardo Magri
2026-07-06 18:09:39 +01:00
parent 3f15f6451f
commit 93521c8617
7 changed files with 190 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
agent/BACKLOG.md
View File

@@ -267,11 +267,7 @@ decide.
would flatten the aligned hand-formatting of ~33 files. Adopt or
declare never?
- **Docs site vs Markdown-in-repo** (from the docs-review item).
- **Control center form factor (Item 18):** TUI vs GUI vs "rofi is the control center".
Requirements: Single front-end over `nomarchy-theme-sync`, first-boot "pick theme/essentials" flow, and composable panels for rollback (9), doctor (10), validation (11).
- *Option A (Rofi-native)*: The rofi menu *is* the control center. Add a `SUPER+C` root or `Control Center ›` submenu. First-boot is a script that chains rofi prompts. Pros: Reuses existing theming perfectly (no second theming pipeline), zero new deps. Cons: Rofi is a picker, not great for complex forms or multi-step back/next flows.
- *Option B (TUI - gum/ratatui)*: A floating terminal running a TUI. Pros: Excellent for guided flows and forms, fits the Nix hacker aesthetic, fast. Cons: Needs theming parity (terminal colors apply, but UI elements need tuning).
- *Option C (GUI - GTK4/WebKit)*: A dedicated GUI app. Pros: Premium feel, handles image previews (wallpapers/themes) easily. Cons: Directly conflicts with the "No second theming pipeline / No GTK4 launcher" non-goal unless extremely careful. High effort.
- **zram swap:** faster under pressure and pairs with NOW#3, but it
interacts with the hibernation-swapfile story (resume device/priority
ordering) — adopt, adopt-with-hibernation-guard, or skip?