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: When to use modular help From:Lorraine Kiewiet <lorraine -at- EZ-DATA -dot- COM> Date:Wed, 4 Feb 1998 14:03:40 -0700
I wasn't in at the beginning of this, but be sure your developers are in
synch with you on this.
I have the master HLP, let's say Mammals.hlp. Then along came the optional
product Cats. To get the Keyword index entries for Mammals and Cats
together, you must have a master CNT and Index.
However, the context-sensitive topics (the ones I wanted users to get when
they pressed the Help button in a dialog) for the topics in Cats.hlp were
unreachable until they added code to the CPP file. Our application calls
one Help file only--Mammals.hlp.
Now the references to new optional HLPs are pretty simple and so I can
maintain it myself. Whenever I have to add an ID for a topic in something
other than Mammals, I must enter the ID number in two places instead of one
in the CPP file. I don't know if everyone works this way, if this is a
Visual C++ sort of thing, or just my own developers, but just be aware of
it.
--Lorraine
