This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| wmii | |
|---|---|
| Name | wmii |
| Developer | Roberto J. Flores, Tomas S. L. M., community contributors |
| Released | 2006 |
| Latest release | 3.5 (example) |
| Programming language | C (programming language), Lua (programming language) |
| Operating system | Linux, FreeBSD |
| Genre | Window manager |
| License | GNU General Public License |
wmii
wmii is a dynamic tiling window manager originally created for the X Window System that emphasizes keyboard-driven workflows, extensibility and minimalism. It integrates a composable layout model with a virtual filesystem interface and a small configuration language to enable deep customization. wmii influenced later projects in the tiling window manager ecosystem and is notable for bridging ideas from stacking, tiling and manual window managers.
wmii presents a lightweight, scriptable environment for users seeking fine-grained control over their X Window System sessions. Its design draws on principles familiar to users of acme (programming environment), Plan 9, and UNIX-style composability, exposing state via a virtual filesystem to tools such as sed, awk, Perl, Python (programming language), and Lua (programming language). wmii's minimal core and extensible userland encouraged contributions from communities around Debian, Arch Linux, Gentoo, and other distributions that package window management software.
wmii combines tiling, stacking and floating paradigms with a tag-based workspace model similar to approaches used in Rob Pike-inspired tools and later seen in dwm and i3 (window manager). Key features include: - A virtual filesystem exposing runtime state accessible from shell utilities like bash, zsh, and fish (shell), enabling automation with cron or session scripts. - Tagging semantics akin to those popularized by 9wm successors and present in XMonad and dwm (window manager), permitting flexible grouping of windows. - A small control protocol usable by clients and scripts, paralleling the philosophies behind Plan 9 services and Wayland's compositors. - Lightweight footprint, written in C (programming language) with optional Lua scripting for user logic, enabling deployment on resource-constrained systems such as machines running Debian GNU/Linux, Ubuntu (operating system), or Arch Linux.
Configuration in wmii centers on a handful of plaintext files and a runtime control interface; users often write scripts in Shell (computing), Perl, Python (programming language), or Lua (programming language) to manipulate behavior. Common patterns mirror techniques from Plan 9 from Bell Labs utilities and editors like acme (programming environment), using the virtual filesystem to read window events and send commands. Distributions package example configs that demonstrate integration with session managers such as systemd, display servers like X.Org, and desktop components including xfce4-session or simple status bars like dmenu.
Window arrangement in wmii uses a columnar and master-stack metaphor, similar in spirit to XMonad's layouts but implemented via a succinct control model. It supports: - Tiled layouts with a resizable master area, influenced by layouts from dwm (window manager) and StumpWM. - Floating windows for dialogs and specialized applications like Firefox or Thunderbird (software). - Tag-based workspace switching comparable to wmii's contemporaries such as ratpoison and herbstluftwm, enabling rapid movement of clients with keyboard bindings inspired by emacs and vi modal editing conventions. - Dynamic retiling and manual rearrangement via keyboard or scripts, permitting integration with compositors like compton or window rules employed by devilspie.
wmii originated in the mid-2000s with contributions from a small core team and an active community that included maintainers and packagers for Debian, Gentoo, and Arch Linux. Its architecture reflected influences from Plan 9, acme (programming environment), and earlier X11 window managers such as 9wm and twm. Over time, forks and experiments engendered features that propagated into projects like i3 (window manager), dwm (window manager), and XMonad libraries. Development was distributed across mailing lists, Git (software) repositories, and patches submitted to package maintainers in various distributions.
wmii attracted enthusiasts who valued minimalism and scriptability, earning mentions in community discussions on Stack Overflow, the Arch Linux (software), Gentoo forums, and blogs maintained by contributors to Unix-like toolchains. Reviewers often compared it favorably to dwm (window manager) and XMonad for its pragmatic balance of control and simplicity, while critics pointed to a steeper learning curve than that of desktop environments like KDE or GNOME (desktop environment). Its influence is visible in educational materials for advanced X11 users and in configuration examples shared on platforms such as GitHub and GitLab.
wmii is frequently compared with tiling managers including dwm (window manager), XMonad, i3 (window manager), herbstluftwm, and awesome (window manager). Comparisons focus on configuration mechanisms—textfile-driven in wmii versus Haskell in XMonad or C in dwm (window manager)—and runtime control interfaces similar to those in i3 (window manager). Several forks and derivative projects experimented with alternative scripting backends, additional layout engines, or Wayland ports, spawning community efforts that targeted compatibility with Wayland compositors and integration with modern display stacks like sway (window manager).
Category:Window managers