X-Git-Url: https://jasonwoof.com/gitweb/?a=blobdiff_plain;f=dwm.html;h=491daebdce2622785e9b8b027efde69e8738ca32;hb=1e7e57dad3e3ac750421795f60867f65b4ff0f67;hp=7e39f157c6fade0b825d149f884558683a5b8c6c;hpb=0e5c8198bc5a69e87b0114b81d6569188828edfa;p=dwm.git diff --git a/dwm.html b/dwm.html index 7e39f15..491daeb 100644 --- a/dwm.html +++ b/dwm.html @@ -28,63 +28,78 @@ 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. + 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 wmii

Differences to ion, larswm, and wmii

- In contrast to wmii, dwm is only a window manager, and nothing else. - Hence, it is much smaller, faster and simpler. + In contrast to ion, larswm, and wmii, dwm is much smaller, faster and simpler.

- dwm has no 9P support, no menu, no editable tagbars, - no shell-based configuration and remote control and comes without - any additional tools like printing the selection or warping the - mouse. + 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 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. + 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 is based on tagging and dynamic window management (however simpler - than wmii or larswm). + 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 don't distinguishes between layers, there is no floating or - managed layer. Wether the clients of currently selected tag are - managed or not, you can re-arrange all clients on the fly. Popup- - and fixed-size windows are treated unmanaged. + 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. + estate to clients. Small titlebars are only drawn in front of + unfocused clients.
- dwm reads from stdin to print arbitrary status text (like the - date, load, battery charge). That's much simpler than larsremote, - wmiir and what not... + 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...
- garbeam does not want 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 garbeams needs. - However you are free to download and distribute/relicense it, with the - conditions of the MIT/X Consortium license. + Anselm does not wants stupid feedback to dwm. If you ask for + support, feature requests, or if you report "bugs" (real bugs + are welcome though), they will be ignored with a high + chance. However you are free to download and distribute/relicense + it, with the conditions of the MIT/X Consortium license.

Screenshot

- Click here for a screenshot (20060714) -

Documentation

Man page
Screenshot (20060714)
Mailing List: dwm at wmii dot de (Archives)
IRC channel: #dwm at irc.oftc.net

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: @@ -93,11 +108,13 @@ hg clone http://wmii.de/cgi-bin/hgwebdir.cgi/dwm

Download

There is no release yet.

dwm 0.2 (13kb) (20060717)

Miscellaneous

You can purchase this tricot - if you like dwm and the dwm logo, which has been designed by garbeam. + if you like dwm and the dwm logo, which has been designed by Anselm.

--Anselm (20060714)