Architecture decisions
Why vyom is built the way it is: each significant decision as a short record (context, the decision, its consequences), in the ADR format. A decision is never edited away: a later one supersedes it. Sources: docs/adr.
Record architecture decisions
Decisions about how vyom is built (its dependencies, its boundaries, the trade-offs it accepts) were made in conversations and commit messages, where nobody finds them later. A con…
One resident process for every panel
Each wofi-based popup started a new process: GTK start-up, theme loading and script start-up made every panel take a visible moment to appear, and each script reimplemented its own…
Panels are layer-shell surfaces, through gtk4-layer-shell
Panels must float above every window, take the keyboard while open, and sit at an exact place (centred, or under the bar for quick settings). Regular windows are managed by the com…
Every tool is its own repository
Bundling all tools in Vyom would force every user to take all fourteen, tie every tool's releases together, and blur the line between the runtime and its users.
Search panels share one size; cards size themselves
With each tool choosing its own size, switching tools with Tab made the panel jump around. But card panels (power menu, battery, quick settings) are different kinds of things: stre…