Cross-platform window manager written in Rust. https://srdusr.com/git/srdwm/atom?h=main 2026-08-30T17:12:00+00:00 2026-08-30T17:12:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2026-08-30T17:12:00+00:00 urn:sha1:bac91a6162542025676f57afc3e514b88aa65366 2026-08-30T15:39:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2026-08-30T15:39:00+00:00 urn:sha1:3d06793cdf7b44d380af6e9608c98d23ea193fa9 2025-12-02T20:17:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2025-12-02T20:17:00+00:00 urn:sha1:96aff79ae2df2ade1a29a68c1a8108d258596bc3 The intro read as a marketing claim ("aiming to feel like a native window manager... rather than a compromise") instead of stating what the project actually does. Replaced with concrete, verifiable facts: every backend draws a real title bar with drag/resize/minimize/maximize/close. The status table implied Windows and macOS were unplanned ("designed, not built") rather than real, in-progress work blocked only on hardware access. All four backends are equal in design intent; Linux is verified because it is the only platform with a working development machine right now, not because the others are lower priority. Windows/macOS rows now name the real cfg-gated code that already exists for each and state plainly why it has never been built or run for real. 2025-10-03T20:09:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2025-10-03T20:09:00+00:00 urn:sha1:d7031dd060ec12e6de334518aa75122c65794047 Codebase modularization, requested directly. Surveyed the whole workspace first: at ~38k lines it's already organized by topic (crates/core/src/manager/, crates/wayland/src/{state,udev,decoration}/ already split into small per-concern files) - crates/platform/src/ ipc.rs was the one real outlier, 1894 lines holding the socket lifecycle, every payload type, both dispatch match statements, and its own tests all in one file. Split into ipc/{mod,types,dispatch,tests}.rs by concern, matching the established pattern exactly - mod.rs keeps IpcServer itself, types.rs the response/event structs and snapshot functions, dispatch.rs handle_request/handle_set, tests.rs the existing suite moved verbatim. Extracted via exact line-range copies against git's own HEAD content (not retyped), specifically to rule out a transcription bug in a file this central. Pure reorganization: build/test/clippy clean before and after, exact same test count (29 in crates/platform) both times. README.md separately corrected: it still linked to legacy-cpp/ (deleted this shift) and described the Wayland backend as the smaller, less-done one - backwards from current reality, where Wayland is the daily-driver target and by far the more complete backend. 2024-05-29T12:40:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2024-05-29T12:40:00+00:00 urn:sha1:3d3057ae384ef7389284af8988410889e99c6bb9 Config path drops a level: ~/.config/srd, not ~/.config/srdwm/srd, which said the same thing twice. No other user-facing path had the same problem -- srdwm reads the config dir and writes nothing else. Cursor shapes. A client's own cursor surface is now rendered with the hotspot it declared, so an I-beam over text or a hand over a link shows the app's image instead of srdwm's arrow. The built-in arrow stays as the fallback when no client has set one, over decorations and the desktop. Named shapes still fall back to the arrow; most toolkits set a surface. Decorations and cursors now share one OverlayElement type, since render_output takes a single custom-element slice. Key repeat (srd.bind_repeat, Hyprland's binde). Held volume, brightness and switcher keys repeat at the seat's own rate rather than firing once. Driven from the poll loop, not a timer source: the winit backend has no calloop loop of its own, and poll_events already runs continuously in both backends. Repeat stops when *that* key is released, not when any key is. Always-on-top / pin, for the picture-in-picture and HUD rules that used it. Window::always_on_top was another declared-but-never-read field. Enforced in WindowManager's stacking order rather than at render time, so every consumer of stacking_order gets it and none can forget to honour it. Mouse-only window management, checked end to end: drag the titlebar to move, drag any edge or corner to resize, titlebar buttons to close/maximise/ minimise, click to focus, drag to a screen edge to snap, and now double-click the titlebar to maximise. The resize grab band went from 6px to 10px - a hairline is genuinely hard to hit with a mouse, which is why Hyprland ships extend_border_grab_area. Also removed the emoji status markers from docs/IMPLEMENTATION_STATUS.md. 2024-04-01T22:58:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2024-04-01T22:58:00+00:00 urn:sha1:8110bb2773b6c841029a51eca7971f42a36f480c The C++ prototype (moved to legacy-cpp/) was mostly a design skeleton: X11 and Windows backends were partially real, Wayland created the wlroots object graph but never wired a single event listener, macOS was stub except monitor enumeration, and the Lua engine's srd.bind() stored a key-combo string but never the actual closure. See docs/PRIOR_ART.md for the full audit. This replaces it with a Cargo workspace: - srdwm-core: platform-independent window/workspace/monitor state, a real master-stack tiling layout, and SmartPlacement grid/cascade/ snap-to-edge placement - fixing several bugs in the C++ version (hardcoded 2-column grid, cascade that never cascaded, snap-to-edge that always returned a fixed rect). 35 unit tests. - srdwm-config: the srd Lua API via mlua, implementing the surface docs/DEFAULTS.md always documented but the C++ engine never actually built (srd.window.close()/focus(direction), srd.workspace.next(), real keybinding closures, require("srd") support). 10 unit tests. - srdwm-x11: a real reparenting WM with a drawn title bar (buttons, drag, resize), verified live under Xephyr - frame placement and client offset match srdwm-core's computed geometry exactly, and the decoration renders correctly on screen. - srdwm-wayland: a from-scratch smithay compositor (the C++ version had nothing working to port from) - runs via the winit backend, tracks xdg-shell toplevels through the same WindowManager and hit-testing code X11 uses, verified to start/render/run without crashing. Decorations are solid-color (no text yet); see docs/IMPLEMENTATION_STATUS.md for exact scope. - srdwm-windows / srdwm-macos: structured, cfg-gated designs informed by komorebi/glazewm and yabai/AeroSpace respectively (see docs/PRIOR_ART.md), honestly marked as unbuilt/unverified since this sandbox has no Windows or macOS target. 2024-04-01T21:50:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2024-04-01T21:50:00+00:00 urn:sha1:d1f856edc516047575cf46f12fad2b59006363c8 2024-03-25T18:09:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2024-03-25T18:09:00+00:00 urn:sha1:0ea49730db789f60349d49187fee2896a947646d 2024-03-19T09:00:00+00:00 srdusr 99972264+srdusr@users.noreply.github.com 2024-03-19T09:00:00+00:00 urn:sha1:862295787da70f03b4a57c73989b9089959ce381