X-Git-Url: https://jasonwoof.com/gitweb/?p=dwm.git;a=blobdiff_plain;f=dwm.html;h=32c0eaeab7b66f87afc8d863b1d830418cfc14f0;hp=b617c8c2c25b0994765fdb4c62eac2a654a8e451;hb=1f9614f82e14fa3a46e0db05346b41d6be611f88;hpb=650a1fb4e1a798aca48a53739f5bb2649191bc1c diff --git a/dwm.html b/dwm.html index b617c8c..32c0eae 100644 --- a/dwm.html +++ b/dwm.html @@ -8,70 +8,111 @@ body { color: #000000; font-family: sans-serif; + margin: 20px 20px 20px 20px; } -

dynamic window manager

- -

Description

+ +

Description

dwm is a dynamic window manager for X11.

Differences to wmii

- In contrast to wmii, dwm is only a window manager, and nothing else. - Hence, it is much smaller, faster and simpler. dwm does - not include following features wmii provides: -

9P support
status bar
menu
editable tagbars
shell-based config/control file
small tools (selection printer, mouse warper)

- dwm is only a single binary, it's source code is intended to never - exceed 2000 SLOC. -

- dwm is customized through editing its source code, that makes it - extremely fast and secure - it does not process any input data which - hasn't been known at compile time, except window title names. -

Philosophy

- dwm is based on tagging and dynamic window management (however simpler - than wmii or larswm). + As founder and main developer of wmii I came to the conclusion that + wmii is too clunky for my needs. I don't need so many funky features + and all this hype about remote control through a 9P service, I only + want to manage my windows in a simple, but dynamic way. wmii never got + finished because I listened to users, who proposed arbitrary ideas I + considered useful. This resulted in an extreme CADT development model, + which was a mistake. Thus the philosophy of dwm is simply to fit my + needs (maybe yours as well). That's it.

Differences to ion, larswm, and wmii

- dwm don't distinguishes between layers, there is no floating or managed - layer. Wether the clients of currently selected tag are managed or not - managed, you can re-arrange all clients on the fly. Popup- and - fixed-size windows are treated unmanaged. -

- dwm uses 1-pixel borders to provide the maximum of screen real - estate to clients. Small titlebars are only drawn in front of unfocused - clients. + In contrast to ion, larswm, and wmii, dwm is much smaller, faster and simpler.

+ dwm has no Lua integration, no 9P support, no menu, no editable + tagbars, no shell-based configuration, no remote control, and comes + without any additional tools like printing the selection or warping + the mouse. +
+ dwm is only a single binary, it's source code is intended to never + exceed 2000 SLOC. +
+ dwm is based on tagging and dynamic window management (however + simpler than ion, wmii or larswm). It manages windows in + tiling and floating modes. Either mode can be applied dynamically, + depending on the application in use and the task performed. +
+ dwm don't distinguishes between layers, there is no floating or + tiled layer. Wether the clients of currently selected tag are in + tiled mode or not, you can re-arrange all clients on the fly. + Popup- and fixed-size windows are treated floating, however. +
+ dwm is customized through editing its source code, that makes it + extremely fast and secure - it does not process any input data + which hasn't been known at compile time, except window title names + and status text read from standard input. You don't have to learn + Lua/sh/ruby or some weird configuration file format (like X + resource files), beside C to customize it for your needs, + you only have to learn C. +
+ Because dwm is customized through editing its source code, it's + pointless to make binary packages of it. This keeps its userbase + small and elitist. No novices asking stupid questions. +
+ dwm uses 1-pixel borders to provide the maximum of screen real + estate to clients. Small titlebars are only drawn in front of + unfocused clients. +
+ dwm reads from standard input to print arbitrary status text (like + the date, load, battery charge). That's much simpler than + larsremote, wmiir and what not... +
+ It can be downloaded and distributed under the conditions + of the MIT/X Consortium license. +

Development

- garbeam don't wants any feedback to dwm. If you ask for support, - feature requests or if you report bugs, they will be ignored - with a high chance. dwm is only intended to fit garbeam's needs, - however you are free to download and distribute/relicense it, with the - conditions of the MIT/X Consortium license. + dwm is actively developed in parallel to wmii. You can browse its source code repository or get a copy using Mercurial with following command:

Development

- dwm is actively developed in parallel to wmii. You can browse its source code repository or get a copy using Mercurial with following command: + hg clone http://10kloc.org/cgi-bin/hgwebdir.cgi/dwm

Download

dwm 0.2 (13kb) (20060717)

Miscellaneous

- hg clone http://wmii.de/cgi-bin/hgwebdir.cgi/dwm + You can purchase this tricot + if you like dwm and the dwm logo, which has been designed by Anselm.

--Anselm

--Anselm (20060714)

dynamic window manager

Description

Description

Differences to wmii

Philosophy

Differences to ion, larswm, and wmii

Links

Development

Development

Download

Miscellaneous