andrew
4321209e92
Introduces a dedicated layer-shell `WindowChromeSurface` that renders macOS-style traffic-light controls over the focused Sway window titlebar, replacing the old top-bar window controls. Adds theme tokens and a reusable `TrafficLightButton` component, updates shell QML/CMake wiring, and adjusts Sway titlebar padding/title format so window titles do not overlap the overlay. Window tracking was extended with focused-window geometry/deco/fullscreen properties plus backend refresh support so the chrome follows window movement and state changes in near real time.
Nebula Windows
Shared C++ window-management service. Desktop, the future Bigscreen shell, and a future Nebula compositor backend should all talk to this library rather than to a compositor directly.
Nebula QML
↓
WindowService
↓
generic WindowBackend
↓
Sway IPC now
Nebula compositor later
QML must not run swaymsg. Sway-specific protocol, socket handling, and tree parsing stay in backends/sway/.
Behaviour
- Connects to the compositor IPC socket from
SWAYSOCK. The path is never hard-coded. - If IPC is missing or fails, the shell keeps running and WindowService stays empty. A development warning is logged.
- Subscribes to
window,workspace, andoutputevents instead of polling. - Exposes
WindowModel(QAbstractListModel) andWorkspaceModel. - Tracks the focused normal application window. Layer-shell chrome (desktop, top bar, launcher) is not treated as the active app.
- Resolves a user-facing name via
ApplicationServicewhen possible, then a small identifier humanizer (footclient→ Foot,org.mozilla.firefox→ Firefox).
QML module URI: Nebula.Windows.
Operations
focusWindow, closeWindow, maximizeWindow, restoreWindow, setWindowFloating, plus moveWindow / resizeWindow / snapWindow / switchWorkspace.
closeWindow asks the compositor to close the client. It does not kill the process.
Maximise fills the current workspace usable area (below the Nebula exclusive zone) using compositor-relative sizing. Restore returns the previous floating geometry when WindowService saved it.
Minimise is implemented for the Sway backend using scratchpad semantics, but the UI must not mention scratchpad. The user-facing idea is only hide / show.
Snap edges (SnapLeft, SnapRight, SnapMaximize) are prepared for a later Snap Layouts UI.
See shells/desktop/README.md and compositor/README.md for session behaviour.