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: my bad displays habit From:Keith Hood <klhra -at- yahoo -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com, dvora -at- tech-challenged -dot- com Date:Sat, 27 Feb 2010 13:39:08 -0800 (PST)
Specifying the window/feature that is supposed to appear next could be thought of as a fault-isolation measure. Suppose somebody clicks on a button and he has been told the X window is supposed to open, but the Y window opens instead. At this point he has a sign that something went wrong somewhere. I think that would actually be a useful thing in UIs for software where getting things right is *really* important, like the software used to calculate dosages in nuclear medicine treatments.
Of course, it would be best if there is no need to consider specifying what window opens next. In a perfect world the UI and the software would be constructed so there is no need for long sequences with a chain of one window after another. But when will that ever happen?
> From: Deborah Hemstreet <dvora -at- tech-challenged -dot- com>
> Subject: Re: my bad displays habit
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Date: Saturday, February 27, 2010, 3:55 PM
> Actually, I think some of us would be
> surprised. I still meet people, on a regular basis, who
> aren't sure which button to click on their mouse.
> At the end of the day it is going to depend on your
> audience. IF you know you are writing for the under 20s
> group, you can assume they know... for the most part (if
> they aren't brought up in Ethiopia without a computer).
> Some people click and get a screen and loose all ability to
> read or think about what they see.
> At the end of the day it boils down to: Know Your
> While we all agree with this, it is amazing how much we are
> prone to assume, but as my Mom used to say: Assume is
> Happy Saturday!
> On 02/26/2010 6:05 PM, Gene Kim-Eng wrote:
> > I wrote user docs like that 25 years ago when half my
> readers were likely to be people who were staring at the
> first GUI they'd ever seen, but is there anyone left today
> who's surprised when clicking on something brings up a
> window, or even contemplates the possibility that they've
> gotten the wrong one?
> > Gene Kim-Eng
> -----Inline Attachment Follows-----
> Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML
> produce desktop, Web, or print deliverables. Just write (or
> and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
> Explore CAREER options and paths related to Technical
> learn to create SOFTWARE REQUIREMENTS documents, and
> get tips on FUNCTIONAL SPECIFICATION best practices. Free
> You are currently subscribed to TECHWR-L as klhra -at- yahoo -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit http://lists.techwr-l.com/mailman/options/techwr-l/klhra%40yahoo.com
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot-
>http://www.techwr-l.com/ for more resources and info.
> Please move off-topic discussions to the Chat list, at:
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-