[RFC] Enforcing Compositing

[Martin Gräßlin]

On Sunday 20 February 2011 22:00:58 Davide Bettio wrote:
> Hi,
> 
> On 02/20/11 21:57, Martin Gräßlin wrote:
> > No, while the KCM sucks it will still suck after those three options
> > have been
> > removed. It needs a proper redesign, but that is out of the scope of this
> > thread ;-)
> 
> 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.

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).
-------------- 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/96b0a9b6/attachment.sig