[PATCH wayland v3] protocol: Add minimize/maximize protocol

[Bill Spitzak]

Jason Ekstrand wrote:

> One more thing before I go onto the technical details: Bill Spitzak.
> Just because he gets on your nerves doesn't mean you should just
> ignore him.

Thanks but I think my email was pretty rambling and I should not have 
sent it. Can try to say what I wanted in a *short* way:

A surface can be both "minimized" and "maximized" at the same time, ie 
it looks minimized but when un-minimized it then looks maximized. I 
thought it might be necessary for both the client and the compositor to 
know this, and thus a set of on/off flags sent as a batch would be the 
best way to communicate this. A sequence of on/off command for each flag 
would have annoying bugs if the two ever got out of sync.

> Thanks for your comments Bill!  I have thought about this solution and
> I think it would work fairly well if we were to have the client send
> an explicit next state such as minimized, maximized, or normal to the
> compositor.

I think you may be right that the compositor does not actually need to 
know the set of states, so there is no problem with bugs making the 
compositor and client disagree, which was the primary reason I thought 
sending the entire set of states at once was a good idea.

This will require the compositor to send an un-minimize event, though, 
since it does not know if the result will be normal or maximized or 
fullscreen. My main concern is now the enumeration of possible messages 
is now larger than the number of states since it has to include these 
"un-state" messages.