To summarize the state of affairs here, the purpose of this protocol is
to communicate:
- The compositor's preference to use SSD or leave the client to its own
devices
- The choice of the client to have SSD displayed
We can completely remove CSD from the question because the term is
barely meaningful. CSD is just a code-word for "some client-provided
mechanism for window manipulation". SSD on the other hand is an apt
description for what the server is going to do here.
I think we can settle the matter by making the following change to
Simon's proposal:
<enum name="mode">
<description summary="window decoration modes">
These values describe window decoration modes.
</description>
- <entry name="client_side" value="1" summary="client-side window
decoration"/>
- <entry name="server_side" value="2" summary="server-side window
decoration"/>
+ <entry name="server_side" value="1" summary="server-side window
decoration"/>
+ <entry name="none" value="2" summary="no window decoration"/>
</enum>
Then updating the prose accordingly. We can include a note along the
lines of "if the client chooses not to use server-side decorations, it
is responsible for its own window management operations."
--
Drew DeVault
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
