Gregory Ruiz-Ade wrote: > On Wednesday 25 May 2005 09:41 am, John H. Robinson, IV wrote: > > With WindowMaker, you can assign a key sequence to bring up the root > > window menu. You don't have to maintain any free space. Since Window > > Maker has a dock and a fiend (clip) you usually do have root window > > space available. I don't cover my dock or fiend, so I can view the > > system monitoring dockapps. There is (almost) always root window space > > below my dock. > > I've never understood the stupid clip thing. It always seems to just get in > the way.
The Dock is persistent across workspaces. The clip(fiend) changes per workspaces. If you only use one workspaces, then the distinction is meaningless. You can also make items on the clip(fiend) persist, so the dockapps or launchers you put there act like they are on the dock. I use it by putting the system monitors, xmms control applet, and xterm launcher all on the dock, so they are always there. I put other dockapps and appicons on the clip in different workspaces. For instance, I have the WPrefs on Workspace 1; Firefox, lynx, and acroread on Workspace 2; Mutt on workspace 3; IRC and IM on Workspace 4. I also keep the clip on the bottom edge, where the mini windows go. That keeps the clip out of the way. You can have loads of fun, by attaching dockapps/icons to the bottom of the clip, then put the clip at the bottom of the screen. Voila! Those dockpps/icons have just disappeared. I'mnot sure the benefit of that, but you can do it. You can also jsut turn off the clip and the dock. With persistent clip items, the dock has become redundant. I'm not certain that MacOS X has a concept of Workspaces. Which I would dind odd, considering that Window Maker and Mac OS X are both based upon NeXTStep. -john -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
