On Sun, 2005-02-13 at 02:11 +0100, Holly Bostick wrote: > > If you do the latter (change GNOME's WM) you still have all the > infrastructure of GNOME running on the backend (most notably Nautilus, > to draw the desktop, for one example).
Just this example is one I dislike, since I personally run it without Nautilus on the desktop. > > If you run gnome-panel under a different WM (but not gnome-session), > the GNOME backend is much minimized, which really speeds things up a > lot. For a few things, however not all. You instead postpone the load of a few factors until after program initialization. The one I really like is the gnome-settings backend, which sets fonts, DPI theme and so on, (and that I cheatingly use to set my background, rather than a configfile where I had bsetbg before) Why? Because I liked the gui. ;) The other thing that is nice about having the session managing the backend rather than the windowmanager, is that you can restart the WM without risking anything. ( good for openbox when you muck up the xml syntax. What? You've never done that? I hope you're kidding me, that is one of the ... ugh. :p ) gconf-d will run anyhow. you have the panel, panel needs its configuration. the vfs-daemon will run if its needed by an application, not started by the session. Other things might want the sm-proxy (if you launch other items from the session) but to avoid clobbering, I keep my session to a few defaults, and don't save it at exit. Hopefully a bit clearer on what the session manager actually does :) //Spider -- begin .signature Tortured users / Laughing in pain See Microsoft KB Article Q265230 for more information. end
signature.asc
Description: This is a digitally signed message part
