xdg-output doesn't belong in the xdg namespace

xdg-output doesn't fit well in the description of the xdg namespace.

In general, regular clients shouldn't care about geometry metadata they can get from xdg-output. There are special cases like Xwayland, which needs this information. There's an opportunity to stop exposing this protocol from regular clients to prevent them from e.g. configuring the size of their surface depending on the xdg-output geometry.

Another part of xdg-output are the more recent name/description events. Arguably these could (should?) be part of the core protocol, because compositors not arranging clients in a 2D coordinate space (e.g. VR compositors) may still want to advertise a name/description (without advertising a geometry).

Apart from these two issues, I guess the real issue is that xdg-output has nothing to do with window management.

2019-02-19 19:27:32     jadahl  honenstly I think the original "xdg_output" should have been xwayland_output and distributed by Xwayland. then we could hav created a wp_output for name, description etc

---

We can't really do anything about xdg-output-unstable-v1, but maybe we should consider fixing this for v2.