Native window chrome: one title row on every OS (no stacked bars), a contract every desktop app follows

Offen
#1,315 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
css, typescript

Rechercherichtung

Start with the existing Windows WindowControls.svelte and the Svelte 5 component conventions in the kit, since that is the one piece of prior art the issue names. Read the per-OS rules table as the spec for TitleRow, CaptionButtons, AppMenu and the platform probe, and settle the token names (--title-row, --window-pad) before writing components. Done looks like the components and rules doc landing with the per-OS light/dark screenshot matrix and visual tests in the kit gate, then the Linux one-row fix in codeatlasdev/atlas#269. This is a design proposal spanning many files and three operating systems, so it needs a maintainer to scope it down before anyone starts.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Why

Atlas Desktop (Tauri) runs on macOS, Windows and Linux. Each app currently decides its window chrome by itself, and on Linux the result looks improvised: a native title bar, then a GTK menubar ("Atlas File Edit View Go Window Help") in an otherwise empty band, then the page's own drag row. That is three stacked bars (codeatlasdev/atlas#269). A native app built on @codeatlasdev/ui should look deliberate everywhere, and the kit is where that rule should live, so every app gets it for free.

Proposal: a WindowChrome contract in the kit

One title row, drawn by the page, on every OS. The rules:

macOS Windows Linux (GNOME, KDE, …) Linux tiling (Hyprland, Sway, i3)
Native title bar overlay (traffic lights inside the row) none (decorations: false) none none
Native menubar the system's own, at the top of the screen none none none
Caption buttons system traffic lights page-drawn, right, Windows 11 metrics page-drawn, order and side from gtk-decoration-layout / button-layout hidden: the WM owns the window
Drag / double-click title row title row → maximize title row → maximize n/a
Menu commands menubar plus palette palette plus a ⋯ app menu in the row palette plus ⋯ palette plus ⋯

Components and tokens:

  • TitleRow with drag region, slots (leading, title, trailing), height token --title-row, and the window pad --window-pad.
  • CaptionButtons (min / max-restore / close): per-OS glyphs, hit areas that reach the screen edge (Fitts), hover and pressed states, a red close on Windows, symbolic icons on GNOME.
  • AppMenu (⋯): every command of the old native menu, with its shortcut; the same source as the command palette.
  • A platform probe the app passes in (os, tiling, buttonLayout, prefersReducedTransparency), never sniffed from navigator.platform alone.
  • Rules doc: no stacked bars, never an empty band, one row of max --title-row height, focus order, a11y names for the caption buttons, and what to test (drag, double-click, resize edges, fullscreen F11, RTL).

Acceptance

  • The components and tokens in the kit, documented with a per-OS screenshot matrix.
  • A visual test per OS and theme (light and dark) in the kit's gate.
  • Atlas Desktop adopts it: Linux shows one row (codeatlasdev/atlas#269), and Windows moves its WindowControls.svelte into the kit.
Vorherrschende Sprache
TypeScript
Sterne
6
Forks
3
Ø Merge
5 Std. 21 Min.
Gemergte PRs (30 T.)
378

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus codeatlasdev/ui

Alle Issues in codeatlasdev/ui

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.