After long time again a little post of mine. This time on organization of the desktop or window manager
Two days ago I switched on the lookout for a new Window Manager at the suggestion of Seba on fluxbox. Fast, lean, highly configurable. Even though I still miss a couple of gimmicks, I found features that I think I do not want to miss.
things I miss
The System Monitor Gnome was quite practical. You could see in a panel, the CPU utilization and memory consumption. Currently I only have the CPU utilization of both CPUs without distinction in Nice, System, and IO-Wait. The wmaker docks are too large and also not on the panel. One 'swallow', as then, the fvwm2 would be great to integrate applications to the panel.
The work surfaces can not change order in two dimensions, that is, I can only left and right, not up and down. But that was relatively efficient, to quickly switch between applications. A matter of getting used to, I hope.
The killer feature
One of the killer features is par excellence but the possibility of arbitrary action by several macro command to put to keyboard shortcuts.
Not only that you can adapt to things like maximizing or switching desktops, you can also new functionality To create an application, for example, assign a keyboard shortcut and start it only if it is not already running.
News is my fluxbox now configured so that programs like Firefox, Thunderbird, etc. have a key combination that either switches to the desktop with the application and displays it or a dialog box pops up with the question of whether it should be started. In addition, the applications a work surface and size is permanently assigned to begin running on it.
the application is running that is not, it starts invisibly on your desktop and then I can switch to it later when she is ready.
Straight switching to Instant Messenger or Media Player and back to the browser or the IDE is so very quickly.
Note: You may only works with the current git version of fluxbox, because next window also does not search all workspaces.
Here the relevant excerpts:
/ .fluxbox / keys: Mod4 C: Reconfigure Mod4 Q: If {Some Matches (class = Iceweasel)} {next window (class = Iceweasel)} {exec ~ / .fluxbox bin / fbexec.sh iceweasel} Mod4 G: If {Some Matches (class = gmpc)} {next window (name = gmpc) (class = gmpc)} {exec ~ / .fluxbox bin / gmpc fbexec.sh Mod4 M}: If { Some Matches (class = Icedove) } {Next window (class = Icedove)} {exec ~ / .fluxbox / bin / icedove fbexec.sh} Mod4 p: If {Some Matches (class = Pidgin)} {next window (class = Pidgin)} {exec ~ / fluxbox. / bin / pidgin fbexec.sh Mod4 R}: If {Some Matches (class = RSSOwl)} {next window (class = RSSOwl)} {exec ~ / .fluxbox bin / fbexec.sh ~ / bin / RSSOwl.sh} Note: Mod4 is the 'Windows' button. The values for class I have taken the apps file that expands fluxbox automatically when you click the right mouse button on a title bar and 'Remember' by clicking on attributes such as the workspace of the application store. Alternatively, is also xprop or wmctl -l ~ / .fluxbox / apps: ... [App] (name = navigator) (class = Iceweasel) (role = browser) [Workspace] {5} [Dimensions] {1198 682} [Position] (UPPER LEFT) {0 80} [end] ... / .fluxbox bin / fbexec.sh: # / bin / sh # timeout returns 0 (success) Thus we have to use need ...