|
I've been noticing this too - I'm getting literally EVERY W/M installed on my system (metacity and kwm, being exceptions) showing up in my GDM session list.
Xfwm is not broken, so you don't need to worry about that. The window managers that are a part of desktop environments tend to be very, VERY simple. You would be surprised at, comparatively, how much more ornate other window managers are (fluxbox, enlightenment, etc.). Enlightenment especially - when you install enlightenment ("E" for short) in Etch, you get two other sessions added to your GDM list, and they are "EGNOME" and "EKDE". E is replacing Metacity and KWM (respectively) for those desktop environments. However, I wouldn't suggest trying to use it unless you REALLY pare down your E desktop setup, because it can look pretty messy pretty quickly.
I highly doubt this is the correct way to look at it (please correct me if I am horribly wrong in thinking this way), but I figure that the window managers that come with desktop environments (Metacity, KWM and Xfwm), are forked from a single "session" script. Next time you hop into any desktop environment (KDE, Gnome or Xfce) pop over into a console and type "ps -ef | grep -i "session" | grep -v grep" and you will most definitely see a "gnome-session", "kdesession" or "xfce-session". As these session scripts call the different parts of the desktop environment (window manager, panel, system tray, file manager, etc.), it would seem logical to me that the window managers (and such) return events (mouse clicks, etc.) to the main session controlling program and from there, it decides what to do.
I have stumbled around trying to use Metacity and Xfwm by themselves, without a DE around them. Pretty sparse.
Last edited by indienick; 08-29-2007 at 08:57 AM.
|
