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.
Subject:Re: Browse Sequences From:Mike Toogood <miket -at- KTGROUP -dot- CO -dot- UK> Date:Thu, 19 Feb 1998 14:45:36 +0000
>... Browse sequences are considered unnecessary? Are they not helpful?
They're very useful, one way that they can be used is to link all the help
topics for one application menu in a parallel way rather than in a
hierarchy - giving a "booky" feel to browsing. The help user can quickly
browse all of the sub-menu help topics. You can use different browse
sequence IDs for each set of menu topics (giving "chapters" to the "booky"
There's no need use numbered browse footnotes if you can just make sure
that your topics are in the correct order in the RTF file; use the same
string in the topic footnotes for each topic in that browse sequence, or
"chapter". The user will only be able to browse topics with the same browse
ID - unless they use a hotspot or search to jump to another topic with a
different "chapter" browse sequence ID string.