<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Writing&gt;Documentation&gt;Screen Captures</title>	<link>http://tc.eserver.org/dir/Articles/Writing/Documentation/Screen-Captures</link>
	<description>A listing of the most recently indexed works about Articles and Writing and Documentation and Screen Captures in the field of technical communication (and technical writing).</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Writing&gt;Documentation&gt;Screen Captures</title>
		<link>http://tc.eserver.org/dir/Articles/Writing/Documentation/Screen-Captures</link>
	</image>
	<item>
		<title>Brokedown Palace, Part 1: Why User Guides Don&apos;t Work</title>
		<link>http://tc.eserver.org/13566.html</link>
		<guid>http://tc.eserver.org/13566.html</guid>
		<description>Software user guides use up an awful lot of space with screen shots. But I know what the screen looks like -- it&apos;s right in front of me. Any decent GUI design is self-documenting to some extent, at least. No matter how much we complain about them, GUIs have gotten pretty good. Children have them figured out in minutes. And then they start asking questions like, &apos;How do I make my stick man move around?&apos; Computers are toasters or drawing pads to them. That&apos;s another reason user guides don&apos;t work: the average user doesn&apos;t need one anymore.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Writing/Documentation/Screen-Captures.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>