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: Building Help in Windows From:Niall Johnson <niallj -at- CI -dot- COM -dot- AU> Date:Fri, 19 Aug 1994 09:00:35 +1000
Terry McNich allegedly wrote:
> Building Help in Windows
> What is the best way to go?
> I need to build on-line help for a Windows application
> that will be distributed without cost to federal, state,
> and local public agencies, schools and universities.
> Is WinHelp the only way to go or are there other options?
> We can not count on the users having MS Word
> or some other wordprocessor that runs the help system.(Lke some
> of the packages I saw at the STC in Minn., when I didn't pay
> close enough attention those help systems because I didn't expext
> to be doing any of this!!!)
> Any clues and experiences will be helpful.
Mmm. The Windows Help Compiler is readily available.
However from what I've seen HDK (Help Developer's Kit) is better. Allows
full hyperlinking and multi-media usage. Relatively easy to use, develop
help and maintain help. Uses the WinHelp 'engine' to run the help you develop.
You can sort of create 'pages' in WinWord and then annotate them with HDK.
Users will NOT need WinWord - runs using the WinHelp engine which is part
of basic Windows.