In computing, a tiling window manager is a window manager with the organization of the screen often dependent on mathematical formulas to organise the windows into a non-overlapping frame. This is opposed to the more common approach used by stacking window managers, which allow the user to drag windows around, instead of windows snapping into a position. This allows for a different style of organization, although it departs from the traditional desktop metaphor.
History
Xerox PARC The first Xerox Star system (released in 1981) tiled application windows, but allowed dialog boxes and property windows to overlap. Later, Xerox PARC also developed CEDAR (released in 1982), the first windowing system using a tiled window manager.
Various vendors Next in 1983 came Andrew WM, a complete tiled windowing system later replaced by X11. Microsoft's Windows 1.0 (released in 1985) also used tiling (see sections below). In 1986 came Digital Research's GEM 2.0, a windowing system for the CP/M which used tiling by default. One of the early (created in 1988) tiling WMs was Siemens' RTL, up to today a textbook example because of its algorithms of automated window scaling, placement, and arrangement, and (de)iconification. RTL ran on X11R2 and R3, mainly on the "native" Siemens systems, e.g., SINIX. Its features are described by its promotional video. The Andrew Project (AP or tAP) was a desktop client system (like early GNOME) for X with a tiling and overlapping window manager. MacOS X 10.11 El Capitan released in September 2015 introduces new window management features such as creating a full-screen split view limited to two app windows side-by-side in full screen by holding down the full-screen button in the upper-left corner of a window.
Dynamic window manager In computing, a dynamic window manager is a tiling window manager where windows are tiled based on preset layouts between which the user can switch. Layouts typically have a main area and a secondary area. The main area usually shows one window, but one can also change the number of windows in this area. Its purpose is to reserve more space for the more important window(s). The secondary area shows the other windows. Tiling window managers that don't use layouts are called manual tiling window managers. They let the user decide where windows should be placed.
Tiling window managers
Microsoft Windows
The first version (Windows 1.0) featured a tiling window manager, partly because of litigation by Apple claiming ownership of the overlapping window desktop metaphor. But due to complaints, the next version (Windows 2.0) followed the desktop metaphor. All later versions of the operating system stuck to this approach as the default behaviour. The built-in Microsoft Windows window manager has, since Windows 2.0, followed the traditional stacking approach by default. It can also act as a rudimentary tiling window manager. To tile windows, the user selects them in the taskbar and uses the context menu choice Tile Vertically or Tile Horizontally. Choosing Tile Vertically will cause the windows to tile horizontally but take on a vertical shape, while choosing Tile Horizontally will cause the windows to tile vertically but take on a horizontal shape. These options were later changed in Windows Vista to Show Windows Side by Side and Show Windows Stacked, respectively. Windows 7 added "Aero Snap" which adds the ability to drag windows to either side of the screen to create a simple side-by-side tiled layout, or to the top of the screen to maximize. Windows 8 introduced Windows Store apps; unlike desktop applications, they did not operate in a window, and could only run in full screen, or "snapped" as a sidebar alongside another app, or the desktop environment. Along with allowing Windows Store apps to run in a traditional window, Windows 10 enhanced the snapping features introduced in Windows 7 by allowing windows to be tiled into screen quadrants by dragging them to the corner, and adding "Snap Assist" — which prompts the user to select the application they want to occupy the other half of the screen when they snap a window to one half of the screen, and allows the user to automatically resize both windows at once by dragging a handle in the center of the screen. Windows 10 also supports FancyZones, a more complete tiling window manager facility allowing customized tiling zones and greater user control, configured through Microsoft PowerToys. Windows 11 added more built-in tiling options, activated by hovering the mouse pointer over the maximize button.
3rd-party replacements AquaSnap - made by Nurgo Software. Freeware, with an optional "Professional" license. Amethyst for windows - dynamic tiling window manager along the lines of amethyst for MacOS. bug.n – open source, configurable tiling window manager built as an AutoHotKey script and licensed under the GNU GPL. MaxTo — customizable grid, global hotkeys. Works with elevated applications, 32-bit and 64-bit applications, and multiple monitors. WS Grid+ – move and/or resize window's using a grid selection system combining benefits of floating, stacking, and tiling. It provides keyboard/mouse shortcuts to instantly move and resize a window. Stack – customizable grid (XAML), global hotkeys and/or middle mouse button. Supports HiDPI and multiple monitors. Plumb — lightweight tiling manager with support for multiple versions of Windows. Supports HiDPI monitors, keyboard hotkeys, and customization of hotkeys (XAML). workspacer — an MIT-licensed tiling window manager for Windows 10 that aims to be fast and compatible. Written and configurable using C#. dwm-win32 — port of dwm's general functionality to win32. Is MIT-licensed and is configured by editing a config header in the same style as dwm. GlazeWM — a tiling window manager for Windows inspired by i3 and Polybar. Komorebi — a window manager for Microsoft Windows SO written in Rust. Like bspwm it does not handle key-binding on its own, so users have to use AHK or WHKD to manage the shortcuts. Komorebi also has a GUI User Friendly version called Komorebi UI. Whim -- dynamic window manager that is built using WinUI 3 and the .NET framework.
… excerpt ends here. Continue reading the full article.






