From 8110bb2773b6c841029a51eca7971f42a36f480c Mon Sep 17 00:00:00 2001
From: srdusr <99972264+srdusr@users.noreply.github.com>
Date: Tue, 2 Apr 2024 00:58:00 +0200
Subject: Rewrite srdwm in Rust: working X11 and Wayland backends, Lua config

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.
---
 src/layouts/dynamic_layout.cc | 31 -------------------------------
 1 file changed, 31 deletions(-)
 delete mode 100644 src/layouts/dynamic_layout.cc

(limited to 'src/layouts/dynamic_layout.cc')

diff --git a/src/layouts/dynamic_layout.cc b/src/layouts/dynamic_layout.cc
deleted file mode 100644
index 7f10ac8..0000000
--- a/src/layouts/dynamic_layout.cc
+++ /dev/null
@@ -1,31 +0,0 @@
-#include "dynamic_layout.h"
-#include "../core/window.h"
-#include <iostream>
-
-DynamicLayout::DynamicLayout() {
-    // Constructor implementation if needed
-}
-
-DynamicLayout::~DynamicLayout() {
-    // Destructor implementation if needed
-}
-
-void DynamicLayout::arrange_windows(const std::vector<SRDWindow*>& windows, const Monitor& monitor) {
-    std::cout << "DynamicLayout::arrange_windows called for monitor (" << monitor.x << ", " << monitor.y << ", " << monitor.width << ", " << monitor.height << ")" << std::endl;
-    std::cout << "Arranging " << windows.size() << " windows dynamically." << std::endl;
-
-    // Basic placeholder: In a real dynamic layout, you might not resize/reposition
-    // windows automatically here unless triggered by user interaction or specific rules.
-    // For now, just iterate through the windows and acknowledge them.
-    for (const auto& window : windows) {
-        std::cout << "  - SRDWindow ID: " << window->getId() << ", Title: " << window->getTitle() << std::endl;
-        // In a real implementation, you might update window properties based on
-        // the dynamic layout logic, or simply leave their positions/sizes as they are
-        // unless a move/resize operation is in progress.
-    }
-
-    // Future implementation would involve logic for:
-    // - Remembering window positions and sizes.
-    // - Handling user-initiated moves and resizes.
-    // - Potentially snapping windows to grid or other windows.
-}
-- 
cgit v1.2.3