Original author(s) | Tom LaStrange |
---|---|
Initial release | 1987 |
Stable release | |
Repository | |
Written in | C |
Type | Window manager |
License | MIT-open-group [3] MIT-CMU [4] XFree86-1.0 [5] |
twm (Tab Window Manager) [6] is a window manager for the X Window System. Started in 1987 by Tom LaStrange, it has been the standard window manager for the X Window System since version X11R4. The name originally stood for Tom's Window Manager, but the software was renamed Tab Window Manager by the X Consortium when they adopted it in 1989. twm is a stacking window manager that provides title bars, shaped windows and icon management. It is highly configurable and extensible.
twm was a breakthrough achievement in the early years, but has been superseded by other window managers, which unlike twm, use a widget toolkit rather than a combination of the X Toolkit Intrinsics and XRandR.
Various other window managers—such as vtwm, tvtwm, CTWM, and FVWM—were built on twm's source code.
twm is still standard with X.Org Server, and is available as part of many X Window System implementations.
twm's interface is different from modern common X window managers and desktop environments many of which tend to work similarly to the Apple Macintosh or Microsoft Windows. New users often find twm difficult without reading the manual page. [7]
In the default configuration of twm, the title bar has two buttons:
There is no title bar button to close a window. A left click on the desktop brings up a menu, which includes an option to delete (close) a window. Window close functionality for the titlebar can be configured in the .twmrc
file:
A left click on the title bar brings the window to the top of the window stack; a middle click moves the window; a right click sends the window to the bottom of the window stack.
Window focus follows the mouse pointer (point-to-focus), rather than being on whichever window was clicked last (click-to-focus).
When a new window is created, a 3×3 grid is displayed following the mouse pointer, waiting for the user to click where the window should appear — left-click to appear in that position with that size, middle-click to resize the window before its creation, right-click to appear at that position but long enough vertically to reach the bottom of the screen.
Note that any of the above may be changed with appropriate changes to the configuration file. (The system file is typically /etc/X11/twm/system.twmrc and the user file is typically ~/.twmrc .) [7]
twm was written as a replacement for the uwm window manager by Tom LaStrange while he was working at Evans & Sutherland, which was part of the X Consortium: "I sat down at my monochrome Sun 3/50 and typed vi twm.c
and then opened the X11 documentation. twm was my first X program. About six months later, I convinced my manager to let me send a copy to the comp.windows.x newsgroup for testing." [8] A version for X11R1 was published on the Usenet newsgroup comp.unix.sources on June 13, 1988 [9]
Months later, Jim Fulton of the X Consortium (which was at the time part of MIT) approached Evans and Sutherland and asked them to turn over the code maintenance to the X Consortium and Fulton then made it compliant with the nascent Inter-Client Communication Conventions Manual. Subsequently, twm was released as the standard sample window manager for X11R4, replacing uwm.
According to Fulton, the word "tab" was picked because it conveniently started with 'T' and it put the emphasis on the squeezing feature window title bars, which made them look like folders with tabs.
twm was originally written by Tom LaStrange. Later contributors include Jim Fulton, Keith Packard and Dave Sternlicht, all of whom were employees of the X Consortium.
The X Window System is a windowing system for bitmap displays, common on Unix-like operating systems.
An X window manager is a window manager that runs on top of the X Window System, a windowing system mainly used on Unix-like systems.
In computing, a window is a graphical control element. It consists of a visual area containing some of the graphical user interface of the program it belongs to and is framed by a window decoration. It usually has a rectangular shape that can overlap with the area of other windows. It displays the output of and may allow input to one or more processes.
Openbox is a free, stacking window manager for the X Window System, licensed under the GNU General Public License. Originally derived from Blackbox 0.65.0, Openbox has been completely re-written in the C programming language and since version 3.0 is no longer based upon any code from Blackbox. Since at least 2010, it has been considered feature complete, bug free and a completed project. Occasional maintenance is done to keep it working, but only if needed.
The taskbar is a graphical user interface element that has been part of Microsoft Windows since Windows 95, displaying and facilitating switching between running programs. The taskbar and the associated Start Menu were created and named in 1993 by Daniel Oran, a program manager at Microsoft who had previously collaborated on great ape language research with the behavioral psychologist B.F. Skinner at Harvard.
In a computing graphical user interface (GUI), a component has focus when it is selected to receive input from the user by an event such as a mouse button click or keypress. Moving the focus away from a specific user interface element is known as a blur event in relation to this element. Typically, the focus is withdrawn from an element by giving another element the focus. This means that focus and blur events are virtually simultaneous in relation to different user interface elements, one that becomes focused and one that is "blurred".
A window manager is system software that controls the placement and appearance of windows within a windowing system in a graphical user interface. Most window managers are designed to help provide a desktop environment. They work in conjunction with the underlying graphical system that provides required functionality—support for graphics hardware, pointing devices, and a keyboard—and are often written and created using a widget toolkit.
The Unix Desktop Environment (UDE) is a desktop environment for the X Window System. Given its efficient and lightweight design it can be used on almost any Unix-like operating system, mostly without any porting effort.
In Unix computing, CTWM is a stacking window manager for the X Window System in the twm family of window managers. CTWM was created in 1992 by Claude Lecommandeur of EPFL from the source code for twm, which he extended to allow for virtual desktops, an innovative feature at the time for a window manager; his inspiration was vuewm, an early Unix desktop environment. Later additions and modifications have since changed the original twm codebase significantly, providing for a highly customizable user interface. The project is currently (2024) maintained by Matthew Fuller. CTWM has been the default graphical user interface for NetBSD since 2020, replacing twm.
A menu bar is a graphical control element which contains drop-down menus.
The Ultrix Window Manager (uwm) is a historic standard window manager software for the X Window System from X11R1 through X11R3 releases. In fact, it was the only X11-compatible window manager as of X11R1.
In computing, a tiling window manager is a window manager with an organization of the screen into mutually non-overlapping frames, as opposed to the more common approach of coordinate-based stacking of overlapping objects (windows) that tries to fully emulate the desktop metaphor.
A compositing manager, or compositor, is software that provides applications with an off-screen buffer for each window. The compositing manager composites the window buffers into an image representing the screen and writes the result into the display memory. A compositing window manager is a window manager that is also a compositing manager.
The Windows shell is the graphical user interface for the Microsoft Windows operating system. Its readily identifiable elements consist of the desktop, the taskbar, the Start menu, the task switcher and the AutoPlay feature. On some versions of Windows, it also includes Flip 3D and the charms. In Windows 10, the Windows Shell Experience Host interface drives visuals like the Start Menu, Action Center, Taskbar, and Task View/Timeline. However, the Windows shell also implements a shell namespace that enables computer programs running on Windows to access the computer's resources via the hierarchy of shell objects. "Desktop" is the top object of the hierarchy; below it there are a number of files and folders stored on the disk, as well as a number of special folders whose contents are either virtual or dynamically created. Recycle Bin, Libraries, Control Panel, This PC and Network are examples of such shell objects.
This article details features of the Opera web browser.
olwm was the default stacking window manager for OpenWindows, the original X11 desktop environment included with SunOS and Solaris. Its unique characteristic is its implementation of the OPEN LOOK look and feel.
Microsoft PowerToys is a set of freeware system utilities designed for power users developed by Microsoft for use on the Windows operating system. These programs add or change features to maximize productivity or add more customization. PowerToys are available for Windows 95, Windows XP, Windows 10 and Windows 11. The PowerToys for Windows 10 and Windows 11 are free and open-source software licensed under the MIT License and hosted on GitHub.
In computing, the icon bar is the name of the dock in Acorn's RISC OS operating system, and is fundamental to the OS. Its introduction in 1987 was a new concept in GUIs. It displays icons through which access is provided to all parts of the computer that a typical user will require, from physical devices and system utilities to running applications, and will usually be their starting point for interacting with the system once it has finished booting.
i3 is a tiling window manager designed for X11, inspired by wmii and written in C. It supports tiling, stacking, and tabbing layouts, which are handled manually. Its configuration is achieved via a plain text file and extending i3 is possible using its Unix domain socket and JSON based IPC interface from many programming languages.