Simplify sentence a bit.
svn path=/trunk/KDE/kdebase/workspace/; revision=759919
This commit is contained in:
parent
756f80301e
commit
c99bd40463
1 changed files with 2 additions and 2 deletions
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue