This protocol seems to be barking up the wrong tree. This protocol only serves traditional floating WMs for whom tiling only goes as far as filling 50% of the screen with a window (as mentioned by others) and isn't very flexible beyond that. I think this should be addressed in two alternative ways:
1. Surfaces always respect the geometry they're given by the compositor. I'm looking at you, gnome-calculator. 2. A protocol that communicates window management capabilities from the compositor to the surfaces like whether or not maximizing or minimizing surfaces makes sense in this compositor. Then if you need an extra protocol for your floating WM's 50% stuff so that the windows can adjust their window decorations or whatnot then that should be seperate. I also think with respect to window decorations that there needs to be a protocol that communicates a preference between the compositor and the clients. The compositor should be able to say "please don't draw window decorations" and the client should either say "okay" or "but I have meaningful UI components in my window decorations so I'm gonna draw them anyway, and I'm letting you know that so you don't do it for me". -- Drew DeVault _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel