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:WinHelp 4.0 is a pain From:Matthew Danda <dandam -at- 1STNET -dot- NET> Date:Tue, 27 Aug 1996 16:26:35 -0500
Is it just me, or do you think that the "new and improved" WinHelp 4.0 is
much more difficult to design than WinHelp for Win3.1?
I mean, now you have to deal with a Contents file, multiple window
interfaces, additional What's This? Help...sure, the end result may be
better (of course, that is debatable, too), but development seems to require
a much more technical mind-set, more planning and organization, and much
For instance, rather than designing your own Contents screen as in Windows
3.1, you now have to use the Microsoft Contents format, and design and link
the Contents using a separate application. Whats the term for this
concept--is it "FatWare?"
Sorry, but I just spent all day trying to make sense of .h, .hm, and .hh
files in order to implement the supposedly simple What's This Help for our
system. Read all the Help manuals at least 3 times, tried a thousand
variations of topic names, recompiled and tested the Help file dozens of
times, recompiled and edited the Visual C++ source code several times, and
still no luck.
St. Louis, MO
dandam -at- 1stnet -dot- net
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-