[PATCH] Suggesting the surface state functions for maximized and fullscreen.

antognolli at gmail.com antognolli at gmail.com
Mon Jun 24 14:07:04 PDT 2013

From: Rafael Antognolli <rafael.antognolli at intel.com>

Just as discussed a lot already on the list, I'm sending a proposal for
implementing the surface states, changing from surface types, for fullscreen
and maximized.

I know that it was said already that fullscreen could be kept as a surface
type, instead of being another state, but making it a state was also proposed.
I like more this option. But this is something up for discussion.

Another important part of this patch is that I added 4 new functions, two for
setting/unsetting maximized, and two for setting/unsetting fullscreen, so we
can have a different set of parameters for each state. I personally don't like
this much, since once we have several different states, the API will grow a

There's no change for adding the events from server since that can be done
after we settle this one. IMHO we have to decide if we are going to have just a
single set/unset API or a pair of set/unset for each state, and if we are
keeping fullscreen as a state of as a surface type. Once that's decided I'll
send more patches that add events which come from the server to clients.

Rafael Antognolli (1):
  protocol: add state set functions for maximized and fullscreen.

 protocol/wayland.xml | 94 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 94 insertions(+)


More information about the wayland-devel mailing list