TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Including Screen Captures From:Averil Strauss <averil -at- LEGENDCOMM -dot- COM> Date:Thu, 23 May 1996 22:41:58 -0400
>I use screen shots in my manuals....not full screens but for any dialog =
>box that requires the customer to choose an option or type information =
>in a field. When I tried to leave them out, the engineers and the =
>customers (we do custom telephony software) raised one heck of a ruckus. =
>Their point was that the user needs to see what the screen OUGHT to look =
>like, just in case theirs has some problem. I don't necessarily agree, =
>but now I leave them in. It does break up the text nicely and, as one =
>customer told me, it helps keep him oriented as to where he is in the =
>program.
Orientation is really important. Put yourself in the place of someone who
just looked up the page by using the index...
Averil
Legend Communications, Inc.
Developers of PostScript Software
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
