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.
> Does anyone out there have other clever ways to lead the user
> through functional branching? I've sought better ways in the
> Journal and in textbooks, but we've yet to find anything that
> isn't just a refinement of these two basic approaches.
*Must* the full branching be described? Perhaps in your paper doc, you can
provide a generic/typical task flow to illustrate the software's intended
functionality, with a proviso that the users' results are affected by their
choices, and may be different from the example. However, your on-line help
should be thorough and context-sensitive for all possibilities.
Cheers!
Marta Cepek
marta -at- m3isystems -dot- qc -dot- ca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net
