-- Forwarded message --
From: cat
Date: Thu, Sep 15, 2011 at 7:27 AM
Subject: Re: seprate window management component
To: Michal Suchanek
On Thu, Sep 15, 2011 at 4:03 AM, Michal Suchanek wrote:
> On 14 September 2011 18:21, cat wrote:
>> well if clients are allowed
t; Hello,
>
> On 14 September 2011 16:55, cat 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
would it be to much trouble to make window management a proxy program?
Ex.
-
| appliation | -> | window manager | ->| display server |
-
and instead of figh
this might be a question more for these programs than for this list,
but how can one of these programs handle the full desktop realestate?
wouldn't that itself force the same condition that you have with the
rogram being a single window?
On Tue, Sep 13, 2011 at 11:13 PM, Bill Spitzak wrote:
> Alo
If I understand the proposal correctly this shouldn't be a problem. If the
application becomes unresponsive the server has the ability to manage it
(move, resize, raise, lower, possibly hide/show, and an option to kill it)
and it knows if it didn't respond to events.
I do think that there is one t
-- Forwarded message --
From: cat
Date: 2011/5/6
Subject: Re: client side decorations
To: Kristian Høgsberg
2011/5/6 Kristian Høgsberg
> On Fri, May 6, 2011 at 3:14 PM, cat wrote:
> >> "Window management policy" should also be client-side. I may not
>
> "Window management policy" should also be client-side. I may not have been
> clear about that. The wayland compositer almost NEVER moves or raises or
> resizes a window. Clients do this in response to clicks or whatever. This
> would have made it TRIVIAL to implement Gimp the way they intended,
On Thu, May 5, 2011 at 9:48 AM, microcai wrote:
> 于 2011年05月05日 22:13, cat 写道:
> > I thought the compositor would/could provide decoration. the compositors
> are
> > after all their own projects as wayland is a protocol, and if you haven't
> > noticed, most metacity
I thought the compositor would/could provide decoration. the compositors are
after all their own projects as wayland is a protocol, and if you haven't
noticed, most metacity/emrald themes are just a set of pictures, would it be
bad if the compositor had the ability to handle images from files? i do
there hasn't been any on the subject but I think that most of the work would
be in kernel space, I think that some of these gpu switching systems use
GPUs from different manufacturers (EX. ATI + Intel), so it is not clear if
every instance of this feature is driver dependant or not. if its not
thou
On Wed, Apr 6, 2011 at 11:57 AM, Michal Suchanek wrote:
> On 6 April 2011 18:34, Jerome Glisse wrote:
> > 2011/4/6 Michal Suchanek :
> >> 2011/4/5 Kristian Høgsberg :
> >>> On Tue, Apr 5, 2011 at 5:59 AM, Michal Suchanek
> wrote:
> Hello,
>
> what is the plan for screensave/screen
On Wed, Mar 23, 2011 at 6:42 PM, Bryce Harrington wrote:
> In testing, we found an oddball issue that with enabling GL for
> libcairo, when running under NVIDIA's proprietary driver applications
> see significantly increased memory utilization.
>
> https://bugs.launchpad.net/ubuntu/+source/cairo/
I'm not sure about who to contact about this but the wayland repository on
anongit was moved and http cloning fails with this message:
fatal: http://anongit.freedesktop.org/git/wayland/wayland.git/info/refs not
found: did you run git update-server-info on the server?
from what I can tell the prob
13 matches
Mail list logo
