RE: terminology question: pointer vs. cursor

Subject: RE: terminology question: pointer vs. cursor
From: "Hager, Harry (US - East Brunswick)" <hhager -at- dc -dot- com>
To: "'Barb Einarsen'" <barb -dot- einarsen -at- gnnettest -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 25 May 2000 12:41:50 -0700


You said:
>When writing for users who are new to Windows, you should refer them to<
>Windows help or other O/S documentation. The operating system writers are<
>better equiped to instruct the user on their platform.<

If your users are new to Windows, how do you instruct them to use Windows
help without telling them that they need to "click" or "select" the Help
button and then move the "highlight" to the term or phrase they want and
then "double-click" the term they want to see? If they are so new to
Windows, how do you know they know what "click," "highlight," "select," and
"double-click" mean?

You also seem to be saying that in order to use your documentation the user
also needs to have readily at hand a copy of Using Windows or some other
similar book.

I've found that putting a short chapter at the beginning of my book that
explains and shows how to use Windows is the thing to do. I do this as
insurance for my and my readers. That way I know that the Windows
terminology I use in the rest of the book has been defined. After you write
this intro chapter you can copy the chapter, with minor modifications, into
every user document you write. I'm more or less using the same intro chapter
that I wrote about five years ago.

Jim Hager
Hhager -at- dc -dot- com
Deloitte Consulting
Pittsburgh Solution Center

Previous by Author: RE: Query??
Next by Author: Re Word/Weird
Previous by Thread: RE: terminology question: pointer vs. cursor
Next by Thread: Callouts

What this post helpful? Share it with friends and colleagues:

Sponsored Ads