Linked by Thom Holwerda on Tue 10th Feb 2009 17:13 UTC
X11, Window Managers Ever since its inception, there have been problems with Compiz; people unsatisfied with the direction of the project forked it, then they merged again. Recently, the project, now known as Compiz Fusion, faced other problems, such as multiple branches and a lack of direction. A major reorganisation of the project is supposed to fix all this.
Thread beginning with comment 348268
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Calipso
by ba1l on Wed 11th Feb 2009 15:07 UTC in reply to "Comment by Calipso"
Member since:

The only thing worse than reinventing the wheel, is reinventing the same mistakes the other team already dealt with.

Which is why the KDE guys want to do compositing in kwm, rather than using Compiz.

KDE's window manager was already a well-established window manager. As a window manager, it works far better than Compiz. It integrates with KDE better. It's more configurable. It has better general window management behaviour (like focus-stealing prevention that actually works). It's an established codebase with very few bugs by this point.

The KDE guys were not willing to throw away 11 years of bug fixes. Especially considering that Compiz doesn't work with a non-composited desktop, so they'd still need kwm anyway. Using two WMs was not an option - there's no way to make Compiz's behaviour consistent with kwm's. Hell, it's not even consistent with metacity.

They decided that re-implementing the two year's worth of work that had already gone into Compiz (and learning from Compiz's problems, and benefiting from work done elsewhere in X to support Compiz) was better than re-implementing the 11 years worth of work that went into kwm.

I tend to agree with them. So do the maintainers of metacity (Gnome's WM) - they are also working on adding compositing support. They just started a lot later than the KDE guys, so they're pretty far behind.

Give it a couple of years, and Compiz will not be the primary compositing window manager. Metacity and kwm will be, with Compiz probably provided for people who want lots of crazy extra effects. Or it'll be completely unmaintained, and nobody will use it.

Reply Parent Score: 4

RE[2]: Comment by Calipso
by siride on Wed 11th Feb 2009 15:16 in reply to "RE: Comment by Calipso"
siride Member since:

I'll add to this by saying that compiz went the wrong way by being a standalone WM. What should have happened is that all the compositing and effects work that went into compiz should have been put into a library that other WMs could have used and then have KWin, Metacity, XFWM, heck, even Fluxbox, be able to make use of those features, but otherwise integrating with the existing DEs/WMs that people actually want to use. As it stands now, Compiz has its own configuration system, its own theming system, its own horrible window management system, etc. Yes, there are plugins to try to connect to native backends, but that's really the wrong solution. Compiz should itself be the backend, with existing WMs, configuration systems and theme systems working as they did before.

Reply Parent Score: 2

RE[2]: Comment by Calipso
by spiderman on Wed 11th Feb 2009 15:38 in reply to "RE: Comment by Calipso"
spiderman Member since:

they are also working on adding compositing support. They just started a lot later than the KDE guys, so they're pretty far behind.

Do you know that Metacity supports compositing since 2006?
You just have to activate it in gconf. I use it since more than a year. I don't think they started any later than the KWin guyz. I believe it is the other way around.
compiz was the first one and will always be an excellent project for experimenting with new features.

Edited 2009-02-11 15:41 UTC

Reply Parent Score: 1