Skip to content

feat(ui): CPU/MEM gauges, mono only for machine identifiers, Cmd+, everywhere - #239

Merged
sergey-zededa merged 1 commit into
mainfrom
feat/app-usage-gauges
Oct 30, 2026
Merged

sergey-zededa merged 1 commit into
mainfrom
feat/app-usage-gauges

Conversation

@sergey-zededa

Copy link
Copy Markdown
Owner

Summary

CPU / memory gauges

  • Running Applications rows show CPU and memory as a small gauge pill (caps label, mini bar, value) instead of plain secondary text, so they no longer read as another label next to the IP chips.
  • The collapsed Device summary uses the same pill (shared UsagePill); EVE version and uptime stay text.
  • The expanded Device grid gets 4px bars with percent used next to memory and storage (CPU's value already is a percent; core count stays in its tooltip).
  • Bars use the existing thresholds (amber ≥75%, red ≥90%). CPU is still omitted while the device is offline. The old one-line text is kept as the pill's accessible name.
  • No sparklines: the controller reports a single 1-hour average per workload, no history.

Typography: monospace only for machine identifiers

  • Mono stays for IPs, localhost:port, key fingerprints / raw key lines, API tokens, logs and the terminal; every stray monospace / Menlo now uses --font-mono.
  • Device names (list and header), SSH key type and controller URL presets use the UI face, with slight negative tracking (--tracking-name) for names; the header name is semibold.
  • Ports (picker, port input), version values, TX/RX stats and the VNC: <port> chip use the UI face with tabular figures.
  • Terminal window toolbar: device name in primary weight, target in secondary. VNC window gets the same name tracking.

Fix: Cmd+, on the device page

  • Cmd+, (and Ctrl+, on Windows/Linux) opens Settings from every view, regardless of focus. It was handled in the container's onKeyDown, which returned early on the device page and missed keys when focus had dropped to <body>; it now listens on window.

Test plan

  • cd frontend && npm test -- --run: 198 passed (new tests for AppUsage, the summary gauges, grid percent captions, and Cmd+/Ctrl+, from the device page with focus on <body>)
  • npm run build
  • Visual check in npm run dev (light and dark)

🤖 Generated with Claude Code

…erywhere

- Running Applications rows and the collapsed Device summary show CPU and
  memory as a gauge pill (mini bars) instead of plain text; the expanded
  Device grid gets thicker bars with percent used for memory/storage.
- Monospace is reserved for IPs, host:port, fingerprints, tokens, logs and
  the terminal; device names, key types, URLs and readable numbers use the
  UI face (tabular figures). Stray monospace/Menlo use --font-mono.
- Cmd+, (Ctrl+, on Windows/Linux) opens Settings from the device page too,
  regardless of focus: handled on window instead of the container handler,
  which returned early on the device page.

Signed-off-by: sergey-zededa <sergey@zededa.com>
@sergey-zededa
sergey-zededa merged commit b29e0b4 into main Oct 30, 2026
6 checks passed
@sergey-zededa
sergey-zededa deleted the feat/app-usage-gauges branch October 30, 2026 12:35
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