The Virtual tab Window Manager 5.4.7
The latest stable release vtwm-5.4.7.tar.gz
The latest development snapshot vtwm-snap.tar.gz
$ git clone git://git.code.sf.net/p/vtwm/code vtwmYou can also browse around to see the source code tree, revision history and commit logs here.
If you have a stack of patches you've been hacking on, we can create a branch for you on sourceforge for you to push your changes to. Contact on the mailing list (see below).
Thanks to Branden Robinson for previously hosting the subversion repository.
VTWM suports a fully configurable 3D interface.
Check out the "Vtwm and..." page for sample configuration files and examples of the interfaces users of Vtwm have made for you. In fact they're using it mostly on a daily base.
Variables and Bindings: Make VTWM work with you.
VTWM parses one of a variety of resource files. They are simple, plain-text documents. Within a resource file, you may specify variables that set up overall traits like GUI features, auto-raising windows, screen panning, and the like. You may also bind nearly any combination of pointer buttons or keys to any number of functions and contexts.
There is no configuration tool. Nobody's written one, and they usually end up crippling the potential, anyway.
VTWM maintains backward compatability with TWM, adds a slew of it's own variables and functions, and can throw in m4 pre-processing, to boot!
Icon Managers: The badly-named feature.
Long before Microsoft presented the taskbar, TWM had the icon manager; a little window filled with buttons, each indicating the state of a managed window. By default, icon managers forward events to the indicated application window. Within this context, however, keys could be bound to navigation functions, for fast access to managed windows. Pointer buttons can be bound to nearly any function you'd bind directly to an application window. You can have multiple icon managers, too, for visually segregated applications.
The virtual desktop and other features of version 5.4 haven't made it another bloated X client. It requires only Xlib, Xext, and Xmu, but depending on build configuration, also the Xpm, regex, and/or rplay libraries. It can still build and run under X11R4, and lose no self-supported functionality.