RE: Identifying window components in SW apps

["Combs, Richard" <richard -dot- combs -at- Polycom -dot- com>]

Michelle Vina-Baltsas wrote: 

> For those writers who document software applications, when 
> you are describing a window/screen, do you identify every 
> part of the window/screen or do you only specify the parts 
> that aren't obvious? We typically identify all parts and 
> pieces, but I'm wondering if this is over kill.  I know this 
> answer will be partly based on the audience, but I want to 
> know what others consider in making this decision. 

The only people who need to learn the names of all the parts of the user
interface are user interface designers. Everyone else just wants to know
what to enter, check, and click in what order to accomplish their task. 

Richard 


------
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------




 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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/archive%40web.techwr-l.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-  Visit
http://www.techwr-l.com/ for more resources and info.