4 ms·
You only need a single implementation that exposes an API for running a WM as an extension. I don't really get why would it be a good idea to somehow mandate a
by gf000 7mo ago
You only need a single implementation that exposes an API for running a WM as an extension.
I don't really get why would it be a good idea to somehow mandate a specific architecture design from the standard.
- nine_k 7mo agoWe need a compositor that exposes everything as an extension. Preferably in a hot-reloadable, tweakable way, say, using Lua (with JIT). And also exposing its APIs in a way that allows having an analog of xdotool.
- hrmtst93837 7mo ago[flagged]
- gf000 7mo agoWell, window management is likely compositor-specific in the first place, so I don't really see the problem. It's not part of the spec, because it would unreasonably constrain what an implementation could do. E.g. what window management does a kiosk compositor have? What even is window placement, what if I am writing a 3D compositor so x/y positioning doesn't even make sense?