RE: Documenting a wizard-based task

[david -dot- locke -at- amd -dot- com]

Wizards are used to simplify any complex configuration task not just
installations. And, not the programmers don't provide more direction on the
wizard than they would on a dialog. The general rule is that the complex
configuration task should use standard dialogs accessible from the menu, but
programmers take shortcuts by only providing a wizard. The problem with
wizards goes into how the wizard is put together. A wizard will consist of a
window and several panels. Any context-sensitive help calls have to use the
context IDs of the panels rather than the wizard (window) that is making the
call. Programmer must hard code the call functionality, and they must
provide unique IDs for the use context of the panel rather than the panel
itself, because the panel may be reused in some other use context. They may
have to do some coding to support use context identification.

David



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

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

Sponsored by Information Mapping, Inc., a professional services firm
specializing in Knowledge Management and e-content solutions. See
http://www.infomap.com or 800-463-6627 for more about our solutions.

---
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.