Wayland Window Management Proposal

[Michal Suchanek]

On 11 May 2011 20:25, Bill Spitzak <spitzak at gmail.com> wrote:
> Michal Suchanek wrote:
>
>> Moves and resizes implemented in the client can't work well.
>
> Any resize solution that does not allow an atomic on-screen update of a
> window to it's new size, with the resized decorations and contents, is
> unacceptable. The whole point of Wayland is that the user NEVER sees a
> partially-updated window.
>
> It is therefore impossible to finish a resize without waiting for the client
> to update the window contents. Since you have to wait for that, there is no
> reason the client can't also draw the decorations. I'm sorry if this makes
> writing clients harder. Deal with it.

Always waiting for the client is something that cannot be upheld.

There are situations when

 - the client is busy or stuck
 - the client is swapped out or a low priority process
 - the client is remote and therefore resizing it will take some time
whatever  you do

If Wayland can't deal with any of the above it's junk.

The window management functions should be working without lag so long
as the window manager and Wayland server have enough resources and
high enough priority.

You can't expect that every single client is high-priority and lag-free.

Thanks

Michal