[RFC] Enforcing Compositing

Martin Gräßlin mgraesslin at kde.org
Sun Feb 20 22:25:31 CET 2011

On Sunday 20 February 2011 22:18:16 Davide Bettio wrote:
> Hi,
> On 02/20/11 22:06, Martin Gräßlin wrote:
> >> I can't understand the point about removing enable/disable options.
> > 
> > if we don't want to give the user the possibility to disable, we don't
> > need an option to enable/disable.
> I don't see anything bad about having enable/disable options on the KCM.
> The only con that I'm aware of is that we have more checkboxes.
Consider the button would not be there: would you see pro arguments to add 
> > Let's turn the question around: why should the user be able to enable or
> > disable compositing? What would be a valid reason to do so? And keep in
> > mind: with Wayland it will be impossible to turn off compositing, same
> > in GNOME Shell, Unity and Mac OS X (don't know about Windows).
> The main reason is that buggy software is still around.
And how do we get the buggy software fixed if we allow workarounds?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20110220/4647639d/attachment.sig 

More information about the Plasma-devel mailing list