Window Managers (WM)

notes

I dont cover wms integrated with desktops. And of course i test only what runs in Devuan.

wm / characterizations

characterization

The primary function of the window manager is to control the layout of top level windows on screen. Window Maker is a window manager. It provides a titlebar and a resizebar to change window layout, application menus to launch applications and execute special commands, application icons, miniwindows and an application dock. They will be explained in more detail in the following chapters. @windomaker-site
Window managers can tell X11 what windows to see, where to position them, and give you tools to organize all the running windows. Fvwm provides an interface in which the user can tell X11 what to do with the running windows, though both user input from the mouse and keyboard, to responding to scripts and events. @fvwm site

wm / apis

Each wm has an api-tookit that a gui program can use to leverage the facilities offered by the wm. Motif, OpenLook, and Athena

wm / table of facilities

facilities afterstep fvwm jwm openbox icewm windowmaker berry stumpwm xmonad i3
window shading
workspaces

wm / common functionality

configuration

Some wm due to running on interpreters support dynamic configuration withiut having to restart the wm.

keymappings

Keymapping seems to be more easily integrated to tiling wms.

window

movement

focus

change size

custom
max , min

rolling (shading)

organization

automated
fluxbox's appfile
One of the most underestimated - although one of the most powerful features - is the apps-file. With this file it is possible to set application-specific parameters for dimension, decoration, default workspace to open on, stickyness and much more. It will let you manipulate almost every setting for any window or application. The best way to learn about it is to visit the wiki-site for the apps-file. @ref
devilspie

@projectsite

curated by the user
tabbing

fluxbox ( @ref ) , pekwm

workspaces

A workspace is essentialy a customized-curated grouping of windows done by the user. A user using own criteria creates own non automated groupings.

wm / configuration

wm / workspaces

wm / common workflows

selecting our current wm

xinitrc

Most likely if you are not using a graphical log in, then you are using startx to begin an X session. In that case you need to run your wm from your ~/.xinitrc file.

After installing a window manager how i choose which to execute when i login with xdm? As default the $HOME/.xinitrc is our first choice where we enter our wm xecutable path $ nano .xinitrc exec /usr/local/bin/jwm or

xsession

$ nano .xsession

wm / twm

@wikipedia

wm / fvwm

@site

wm / windomaker

@site

windowmaker / installation

$ sudo apt-get install wmaker

windowmaker / enable

$ nano .xsession exec wmaker

wm / IceWM

wkp

wm / Openbox

wkp, @openbox website

wm / jwm

jwm / about

@jwn website

jwm / Starting JWM

The preferred method for starting JWM varies depending on distribution and the display manager used to login. A common approach is to add the following line to either "$HOME/.xsession" or "$HOME/.Xinitrc": exec /usr/local/bin/jwm This will typically cause JWM to load immediately when X starts (if you are not using a login manager) or when the "user-defined" login is selected.

wm / i3

about

i3 website

wm / stumpwm

about

stumpwm website

wm / pekwm

pekwm / about

pekwm / installing

$ sudo apt-get install pekwm

Adding exec pekwm to ~/.xinitrc if you start X running startx or ~/.xsession if you use a display manager should usually be enough to get pekwm running.

pekwm / config

@ref

/etc/pekwm/config is copied to ~/.pekwm/config

wm / gooddocs

It's always welcoming to have a nice site explaining the in and outs of your project. Here is my list of good wm sites: