Create A Basic WinHelp 3.1 Project File

What is a Windows® help project file? Why do I need one? How do I create one? These questions are answered on this and subsequent pages. The last WEB page in this series contains an example help project file with common entries. Added to the definitions are recommendations based on my own experience. After all, if you are new to help authoring, what you are looking for is not just what goes where, but what works best where!

A Windows Project File (*.hpj) is a specially formatted ASCII text file, and is similar to the common Windows *.ini file. The information in a project file tells the help compiler which options to use, and how those options should be applied.

At the basic level the project file contains file locations, window names, sizes and colors, and copyright and compression options. It also links the *rtf files context strings to the application's context numbers to establish context sensitive help. At a higher level, the project file may contain complex macros interspersed with application program interfaces (APIs), and reference third party tools. Such entries expand WinHelp's flexibility, which allows the help author to open and close applications, delete or add button bars, display animation, play sounds, and other amazing things.

The project file must contain a minimum of three sections: [OPTIONS], [FILES] and [WINDOWS]. There are six other sections that can be used: [BUILDTAGS], [CONFIG], [BITMAPS], [MAP], [ALIAS], and [BAGGAGE].

Note: The differences between a Windows 3.1 help project file and a Windows 95/NT (WinHelp 4.0) project file are mentioned throughout this paper, but not explained in detailed.

Continued on Next Page

The Freelance Story Teller

Voice: 405 720 7995

Fax: 405 720 7995

11808 Silvermoon Drive, Oklahoma City, OK 73162