1.1 --- a/dwm.html	Mon Jul 17 10:09:57 2006 +0200
     1.2 +++ b/dwm.html	Mon Jul 17 11:36:07 2006 +0200
     1.3 @@ -28,58 +28,74 @@
     1.4  		and all this hype about remote control through a 9P service, I only
     1.5  		want to manage my windows in a simple, but dynamic way. wmii never got
     1.6  		finished because I listened to users, who proposed arbitrary ideas I
     1.7 -		considered useful. This resulted in an extreme <a href="http://www.jwz.org/doc/cadt.html">CADT</a>
     1.8 -		development model, which was a mistake. Thus the philosophy of
     1.9 -		dwm is simply <i>to fit my needs</i> (maybe yours as well). That's it.
    1.10 +		considered useful. This resulted in an extreme <a
    1.11 +		href="http://www.jwz.org/doc/cadt.html">CADT</a> development model,
    1.12 +		which was a mistake. Thus the philosophy of dwm is simply <i>to fit my
    1.13 +		needs</i> (maybe yours as well). That's it.
    1.14  		</p>
    1.15 -		<h3>Differences to wmii</h3	
    1.16 +		<h3>Differences to ion, larswm, and wmii</h3>
    1.17  		<p>
    1.18 -		In contrast to wmii, dwm is only a window manager, and nothing else.
    1.19 -		Hence, it is much smaller, faster and simpler.
    1.20 +		In contrast to ion, larswm, and wmii, dwm is much smaller, faster and simpler.
    1.21  		</p>
    1.22  		<ul>
    1.23  			<li>
    1.24 -			dwm has no 9P support, no editable tagbars, no shell-based
    1.25 -			configuration and remote control and comes without any additional
    1.26 -			tools like printing the selection or warping the mouse.
    1.27 +			dwm has no Lua integration, no 9P support, no menu, no editable
    1.28 +			tagbars, no shell-based configuration, no remote control, and comes
    1.29 +			without any additional tools like printing the selection or warping
    1.30 +			the mouse.
    1.31  			</li>
    1.32  			<li>
    1.33  			dwm is only a single binary, it's source code is intended to never
    1.34  			exceed 2000 SLOC.
    1.35  			</li>
    1.36  			<li>
    1.37 -			dwm is customized through editing its source code, that makes it
    1.38 -			extremely fast and secure - it does not process any input data which
    1.39 -			hasn't been known at compile time, except window title names.
    1.40 -			</li>
    1.41 -			<li>
    1.42 -			dwm is based on tagging and dynamic window management (however simpler
    1.43 -			than wmii or larswm).
    1.44 +			dwm is based on tagging and dynamic window management (however
    1.45 +			simpler than ion, wmii or larswm). It manages windows in
    1.46 +			tiling and floating modes. Either mode can be applied dynamically,
    1.47 +			depending on the application in use and the task performed.
    1.48  			</li>
    1.49  			<li>
    1.50  			dwm don't distinguishes between layers, there is no floating or
    1.51 -			managed layer. Wether the clients of currently selected tag are
    1.52 -			managed or not, you can re-arrange all clients on the fly. Popup-
    1.53 -			and fixed-size windows are treated unmanaged. 
    1.54 +			tiled layer. Wether the clients of currently selected tag are in
    1.55 +			tiled mode or not, you can re-arrange all clients on the fly.
    1.56 +			Popup- and fixed-size windows are treated floating, however. 
    1.57 +			</li>
    1.58 +			<li>
    1.59 +			dwm is customized through editing its source code, that makes it
    1.60 +			extremely fast and secure - it does not process any input data
    1.61 +			which hasn't been known at compile time, except window title names
    1.62 +			and status text read from standard input. You don't have to learn
    1.63 +			Lua/sh/ruby or some weird configuration file format (like X
    1.64 +			resource files), beside C to customize it for your needs,
    1.65 +			you <b>only</b> have to learn C.
    1.66 +			</li>
    1.67 +			<li>
    1.68 +			Because dwm is customized through editing its source code, it's
    1.69 +			pointless to make binary packages of it. This keeps its userbase
    1.70 +			small and elitist. No novices asking stupid questions.
    1.71  			</li>
    1.72  			<li>
    1.73  			dwm uses 1-pixel borders to provide the maximum of screen real
    1.74 -			estate to clients. Small titlebars are only drawn in front of unfocused
    1.75 -			clients.
    1.76 +			estate to clients. Small titlebars are only drawn in front of
    1.77 +			unfocused clients.
    1.78  			</li>
    1.79  			<li>
    1.80 -			dwm reads from <b>stdin</b> to print arbitrary status text (like the
    1.81 -			date, load, battery charge). That's much simpler than larsremote,
    1.82 -			wmiir and what not...
    1.83 +			dwm reads from standard input to print arbitrary status text (like
    1.84 +			the date, load, battery charge). That's much simpler than
    1.85 +			larsremote, wmiir and what not...
    1.86  			</li>
    1.87  			<li>
    1.88 -			Anselm <b>does not</b> want any feedback to dwm. If you ask for support,
    1.89 -			feature requests, or if you report bugs, they will be <b>ignored</b>
    1.90 -			with a high chance. dwm is only intended to fit Anselms needs.
    1.91 -			However you are free to download and distribute/relicense it, with the
    1.92 -			conditions of the <a href="http://wmii.de/cgi-bin/hgwebdir.cgi/dwm?f=f10eb1139362;file=LICENSE;style=raw">MIT/X Consortium license</a>.
    1.93 +			dwm is only intended to fit Anselms needs. That means, Anselm
    1.94 +			<b>does not</b> want feedback to dwm. If you ask for support,
    1.95 +			feature requests, or if you report "bugs" (<i>real bugs are welcome
    1.96 +			though</i>), they will be <b>ignored</b> with a high
    1.97 +			chance.  However you are free to download and distribute/relicense
    1.98 +			it, with the conditions of the <a
    1.99 +			href="http://wmii.de/cgi-bin/hgwebdir.cgi/dwm?f=f10eb1139362;file=LICENSE;style=raw">MIT/X Consortium license</a>.
   1.100  			</li>
   1.101  		</ul>
   1.102 +		<h3>Documentation</h3>
   1.103 +		There is a <a href="http://wmii.de/cgi-bin/man/man2html?query=dwm">man page</a>.
   1.104  		<h3>Screenshot</h3>
   1.105  		<p>
   1.106  		<a href="http://wmii.de/shots/dwm-20060714.png">Click here for a screenshot</a> (20060714)