[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    Re: Re: Review Request: Add Rule/Property based composite blocking
From:       Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date:       2011-03-21 17:04:16
Message-ID: 1898110.hSxZbTs4ru () martin-desktop
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 21 March 2011 17:49:40 Thomas Lübking wrote:
> Am 21.03.2011, 11:38 Uhr, schrieb Sebastian Kügler <sebas@kde.org>:
> 
> Can any of them (at least as a design aspect) toggle compositing at  
> runtime like KWin does?
I think Compiz in 0.9 supports non-composited. So with Unity2D + Compiz it should be possible 
to not require compositing (I expect Unity2D to be Unity in 11.10). GNOME Shell is a plugin to 
Mutter and AFAIK does not support non-composited or any other window manager.
> 
> > What kind of apps would block compositing?
> Typically "I run the show" fullscreen clients like mediaplayer/centers,  
> games aso.
> Especially if they've high/clashing (GL HW) resource demand.
> 
> But some HW is simply not capable to run even just GoogleEarth (or  
> Marble?) and at the same time a GL compositor. So it would help those  
> users to (by rule in this case) automatically suspend compositing while  
> such client is running (fullscreen or not).
> 
> Cheers,
> Thomas
> _______________________________________________
> kwin mailing list
> kwin@kde.org
> https://mail.kde.org/mailman/listinfo/kwin
> 

["signature.asc" (application/pgp-signature)]

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin


[prev in list] [next in list] [prev in thread] [next in thread]