From c99bd40463186bda2f54f2087c4c9de1c3942c24 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lubo=C5=A1=20Lu=C5=88=C3=A1k?= Date: Fri, 11 Jan 2008 14:05:29 +0000 Subject: [PATCH] Simplify sentence a bit. svn path=/trunk/KDE/kdebase/workspace/; revision=759919 --- NOTES_4_0 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/NOTES_4_0 b/NOTES_4_0 index 602bb66e45..60cad76df2 100644 --- a/NOTES_4_0 +++ b/NOTES_4_0 @@ -242,7 +242,7 @@ plugins from KWin would essentially require KWin to become Compiz. == Why add compositing support to KWin when Compiz is better ? == There can be different ideas about what better means, but regardless of that, to main aim of KWin -is not to replace Compiz. Many users have asked for compositing support in KDE, and, for reasons -listed in 'Why not Compiz?', the best way to achieve that has been considered to be adding compositing +is not to replace Compiz. Many users have asked for compositing support in KDE, and, as explained +in 'Why not Compiz?', the best way to achieve that is considered to be adding compositing support to KWin. KWin aims to provide compositing support, focusing on providing useful compositing features and basic visual effects, while keeping its other strengths.