Re: Aquamarine + beryl

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Aquamarine + beryl
by zonk on Wednesday 30/May/2007, @10:21

First of all, KWin is MUCH more advanced. Not on the visual side, but instead it has all those little things that go unnoticed while making the work more pleasant and fast. Clever auto-arranging of windows is only one of those underestimated features. The second reason would be that Compiz/Beryl architecture is a mess. Those WMs were a trip into an uncharted territory, and as such they could not benefit from existing experience in writing compositing managers. The effect is a messy codebase that either way should be rewritten. So if a complete rewrite is needed, why not stick with the good and mature KWin codebase, and extend it to embrace new possibilities given by compositing?

Related Links

·   Articles on KDE Public Relations and Marketing
·   Also by zonk
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"I learnt programming in a very lovely language named GFA Basic." -- Michael Brade
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.