All posts by Olivier

KDE memory usage

I came out across an article from Lubos Lunak on KDE memory usage, relayed by OSNews.com.
I find the article very interesting as memory usage is a topic that pops up regularly on our mailing lists. I’d just like to point out a small detail, regarding the methodology used for measuring “plain” desktop usage with real life apps.
Both OpenOffice.org and Mozilla Thunderbird used with Xfce to measure its memory usage, are quite heavyweight applications. Usually, people use lighter alternatives with Xfce, like Abiword. Abiword can be plain GTK+ and doesn’t require GNOME libs (it can make use of GNOME libs, but there are not mandatory and Abiword can compile and operate w/out).
Same goes with Thunderbird, people sometime prefer a plain GTK+ mailer like Sylpheed or Sylpheed-Claws which are very capable mailers instead of Thunderbird. With these apps, you can run plain GTK+ apps w/out KDE and GNOME libs.
Still, I agree that people who want to use a Web browser will probably choose Firefox. But similarly a lot of people I know use Thunderbird, OpenOffice.org or Firefox with either KDE or GNOME too.

Xfce window manager now includes its own compositing manager

It tooks me a while and a lot of work to get the compositing manager working in xfwm4, the Xfce window manager (obligatory screenshot)

I’ve been asked why making a separate compositor rather than using X.org’s xcompmgr.

To make it short, because it makes perfectly sense. The compositor is like a WM on its own, it manages a stack of all windows, monitor all kinds on X event and reacts accordingly.

Having the compositing manager embedded in the window manager also helps keeping the various visual effects in sync with window events.

An RPM archive for fedora with compositor enabled is available here (source RPM here)

This package is to be used in place of the regular xfwm4 package from Xfce 4.2 RC2 available here

xfwm4 native multihead support

Hey, xfwm4 now supports native multi screen and is able to manage all the screens connected to a display from a single xfwm4 process.

Adding this caused deep and complex changes in the core of xfwm4, so that might be still a bit rough on the edges…

If someone with the HW could just test… What’s needed is a multiscreen configuration but without running Xinerama (ie, a setup with :0.0 and :0.1 as screens, for example)

Cheers,
Olivier.