RE: Documenting Wizards

[France Baril <Barilf -at- ixiasoft -dot- com>]

It depends if you are documenting how to use the wizard or how to choose
between the many options offered by the wizard. For example, if the wizard
helps the user set security, you may want to document the consequences of
choosing one security level over the other.

-----Original Message-----
From: Gordon Meyer [mailto:gordonmeyer -at- mac -dot- com]
Sent: 14 mai, 2003 12:25
To: TECHWR-L
Subject: Re: Documenting Wizards



If a "wizard" requires documentation, I suggest putting the time and 
energy into improving the wizard. Wizards are essentially 
self-disclosing and interactive instructions, so having Help for a 
wizard is sort of like having a manual for the manual. (Which, of 
course, is sometimes done. Ugh.)


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

Robohelp X3, from eHelp, lets you quickly and easily create 
professional Help systems for all your Windows and Web-based 
applications, including Net. 

Order RoboHelp X3 in May and receive a $100 mail-in rebate, PLUS
free RoboScreenCapture and WebHelp Merge Module. 
 
Order RoboHelp today: http://www.ehelp.com/techwr-l

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.