[Enhancement] Figma-style sections

[youssefvdel]

Figma-Style Sections as Workspaces

Overview

Transform sections from canvas decorations into workspace-like containers that are created dynamically at runtime (not via config).
Key difference from config-based: Sections are runtime entities created via right-click menu or keyboard shortcut, stored in memory/state file only.

---

Context Menu Flow

Right-Click on Canvas

┌─────────────────┐
│ New Section     │ ← Creates section at viewport, switches to it
└─────────────────┘

Right-Click on Active Section

┌─────────────────┐
│ New Section     │
├─────────────────┤
│ Suspend         │ ← Suspends all apps in section (frees RAM/CPU)
│ Rename          │
│ Delete          │
└─────────────────┘

Right-Click on Inactive Section

┌─────────────────┐
│ New Section     │
├─────────────────┤
│ Active          │ ← resume from suspended
│ Rename          │
│ Delete          │
└─────────────────┘

---

Suspend:

• Get all windows in active section
• Get their PIDs (from window/app_id mapping)
• Send SIGSTOP to each PID
• Mark section as suspended
• turn into gray

---

Future

1. Drag windows between sections — drag to edge, peek into adjacent section
2. Per-section backgrounds — different wallpaper per section (color picker)
3. Section locking — prevent moving section instead of window
4. Move window to section — context menu on window → "Move to Section X"

[malbiruk]

Do I understand correctly that the sections here are basically window clusters -- the implicit groups you get by snapping windows together?

On suspending/activating apps:

The suspend part doesn't really work on Wayland. A stopped client can't pong xdg_wm_base.ping, so it'll get marked unresponsive. Its DBus services freeze, so anything talking to it (notifiers, MPRIS, browser parent/tab IPC) hangs. And SIGSTOP doesn't actually free RAM — the kernel only reclaims pages under memory pressure regardless. No major Wayland compositor suspends apps on workspace switch for these reasons.

But what you already can do -- get windows' app_ids, positions, and sizes from $XDG_RUNTIME_DIR/driftwm/state, and add them to config file as window rules via external script, which solves the same problem of preserving the session basically.

Also there are go-to actions already, which are like bookmarks, and you can move windows to them. Though they're a bit hard to use now because they're defined in config by coordinates. I'm planning to make them dynamic by making actions to save bookmark and jump to bookmark.

[rwx7]

Can you navigate between clusters with key bindings? eg "mod+alt+right" = "focus_cluster right"