-- Forwarded message --
From: cat zixo...@gmail.com
Date: Thu, Sep 15, 2011 at 7:27 AM
Subject: Re: seprate window management component
To: Michal Suchanek hramr...@centrum.cz
On Thu, Sep 15, 2011 at 4:03 AM, Michal Suchanek hramr...@centrum.cz wrote:
On 14 September 2011 18:21
Michal Suchanek wrote:
Still the clients should not know about the windows of other clients
so they would not know how their windows stack and not knowing that
they can't really decide it either.
I don't think the clients will know about any windows other than a few
ids that the compositor
On Wed, Sep 14, 2011 at 11:19 PM, Michal Suchanek hramr...@centrum.cz wrote:
Hello,
On 14 September 2011 16:55, cat zixo...@gmail.com wrote:
would it be to much trouble to make window management a proxy program?
The wayland server has to know how the windows stack but the clients
are not
Hello,
On 14 September 2011 16:55, cat zixo...@gmail.com wrote:
would it be to much trouble to make window management a proxy program?
The wayland server has to know how the windows stack but the clients
are not trusted to tell it how the windows should stack so either the
server has to figure
well if clients are allowed to decide how their own windows stack, the
window management proxy would be in control.
the idea I have is that there isn't any special protocol changes
(though that might be bad for this system), but because of the proxy,
a call to or a response from (or lack of one)
On 15/09/11 04:33, Michal Suchanek wrote:
On 14 September 2011 20:26, Bill Spitzakspit...@gmail.com wrote:
I think the idea is that what you are calling the window manager is in
fact a library running in the client process and memory space. It would
probably be part of the toolkit.
Which is
