The main purpose of a window manager actually should be -- well -- to manage windows. However, nearly all widespread window managers like those included in Microsoft Windows or in MacOS only allow you to manually move/resize/maximize and minimize windows. In my opinion, it should really try to manage my windows for me by automatically moving or resizing them when appropriate.
This means, that it should dynamically change the window layout when new windows are created or old ones are destroyed. Moreover it is essential that an advanced manager can easily be used with the keyboard only. This can be best described by Tuomo Valkonen -- "the'' person in terms of innovative user inteface design -- himself:
Present-day graphical user interfaces are far less usable than they are praised to be. Usability simply does not equal low learning curve, as the Official Truth seems to be these days. Power and keyboard users, those who just do not like or have medical problems with mice, are forgotten when "modern" graphical programs are designed. Mouse-based search-and-click interfaces simply are not efficient except for some very specific tasks and often involve lots of tedious repetitive tasks. And while most widget-based GUIs provide keyboard shortcuts to some operations, the general application design still makes them difficult to use from the keyboard. For example, tabbing through dialog entries is difficult if the dialog is laid out in a complex fashion. Most command line and other text mode programs are simply much more usable once you get used to them, but are limited in their output capabilities.1. PWM & Ion
Tuomo Valkonen was the first one who tried in an experiment to create a different kind of window management model. This attempt to create a totally new way to interact with windows was later copied by several other window manager's like TrsWM or WMI.
This was the first window manager which featured tabs in the title bar. If you open up 3 browser windows, normally these windows are all over the screen with different locations and sizes. With a tabbed window manager you can group them together and easily manage all grouped windows simultaneously. In order to add a window to a group you just need to drag it the group and drop it. You can also configure PWM to auto-group certain application windows (in our case, we would set it up to group all browser windows into one group).
So as you can see in the next screenshot, all 3 browser windows share one common title bar, and if I chose to maximize one window, the other two would be maximized too automatically:
The solution of PWM solved some problems, but it was still a difficult task to completely manage all windows with the keyboard only. Tuomo Valkonen therefore quickly improved his own PWM and came up with the first tabbed and tiling window manager.
It tries to address the navigation problem by dividing the screen into mutually non-overlapping frames that take up the whole screen. By using this frame-based instead of coordinate-based approach, it is conveniently possible to move between the frames entirely with the keyboard, because by this window layout it's always possible to say which is the next frame on the right/left/top/bottom side of the current one.
So in the next figure, if I want to quickly switch from my tv application on the bottom right to my browser, I just need to tell Ion (by keyboard shortcuts) to switch to the left window.
Another big advantage of this frame-based layout is scriptability. Since the frame layout is saved after a restart and I can have custom names for all of my frames, I can configure Ion so that if I start large application windows like browsers or e-mail clients, they are moved to the upper left frame. On the other hand, small applications like an MP3 player or instant messanger should go in a small frame on the right. Also moving windows can be done very conveniently, since I don't need to move them pixelwise, but I just need to drag the window from one frame to another and drop it. Then the window will occupy the full space of the frame.
- Make all windows full screen
- Fully extendable with Lua scripts
- A Query module with autocompletion. Use this to quickly start programs.
- Small and fast
WMI is a very new project and it's development started at the end of 2003. It tries to feature all good things from Ion but also to bring tiling window managers to the masses by making them easier to use.
To configure Ion (or newer versions of PWM) you need to have some knowledge of a turing complete scripting language called Lua.
In contrast, WMI let's you configure some settings at runtime and other things like the keybindings in a simple text file. Furthermore it has an always visible status bar which shows the current time, a pager and something like a task bar which lists running applications. This makes it easier for users who do not want to completely rely on the keyboard for these commands.
WMI also breaks the concept, that all windows must not overlap but combines the advantages of a tiled window manager with the possibility of having some windows floating above the others. While a tiled layout is suitable for most application, for some special applications like a media player, it's sometimes convenient to be able to move the player around above all other windows.
Another very interesting feature of WMI is the close connection to the famous vi editor. So, people accustomed to this great editor will feel like at home when using WMI.3. Exposť
To be exact, Exposť is actually not a window manager, but a feature of newer versions of Apple's window manager for MacOS X. It does not try to arrange windows non-overlapping nor does it try to favor the keyboard in window management. However, by pressing a keyboard shortcut it tries to make it easier to select the next window by temporarily moving (and resizing) all application windows so that they don't overlap. Now, the user sees all windows at the same time, and can select one with the mouse. Afterwards, all windows are moved to their previous location and the selected window is made topmost.References
http://wmi.berlios.de About the author
This article was written by Martin Stubenschrott. He lives in Austria and studies Computer Science at the Technical University of Vienna. He is a long term Ion user and enjoys editing everything text-based with vim.