[PATCH v2] xdg-shell: Add tiled state
jadahl at gmail.com
Tue Jun 7 07:58:51 UTC 2016
On Mon, Jun 06, 2016 at 11:31:48AM +0200, Olivier Fourdan wrote:
> When tiled, clients must obey the window geometry specified in the
> configure event and can choose to hide some of their decorations.
> Signed-off-by: Olivier Fourdan <ofourdan at redhat.com>
> v2: Simplify the proposal and keep only one "tiled" state instead of one
> per edge.
> Note that the edges in my initial proposal were surface edges, not
> monitor edges. Anythow, if some other (tiling) Wayland compositor
> needs more granularity, we could use the "draw states" from Mike's
I don't think any kind of semantic state (like maximized, tiled etc)
should go into the draw state enum.
> I do however reckon that "tiled" is not the same as "maximized",
> even though a client has to obey the geometry in both cases, a
> client would need to distinguish between the two states to adapt
> its decorations accordingly.
> A single "tiled" state would get my vote (at least ^_~) as it's
> simple enough.
The edge based tile state gives more flexibility, and would eventually
in one way or another be introduced for semi tiled window management
(like the one in GNOME), so I think we could just as well just go with
If this opinion is in minority, I'm fine with this one for now.
> unstable/xdg-shell/xdg-shell-unstable-v6.xml | 6 ++++++
> 1 file changed, 6 insertions(+)
> diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
> index ce57153..99465cd 100644
> --- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml
> +++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
> @@ -343,6 +343,12 @@
> active. Do not assume this means that the window actually has
> keyboard or pointer focus.
> + <entry name="tiled" value="5" summary="the surface is tiled">
> + <description summary="the surface is tiled">
> + The surface is tiled, either to another surface or a monitor
> + edge. The window geometry specified in the configure event must
> + be obeyed by the client.
> + </description>
More information about the wayland-devel