9.3.10 Getting OmniHelp supporting files in the right place
Before you can use the OmniHelp viewer, all OmniHelp supporting files must be placed in the same folder structure as the HTML or XHTML output files Mif2Go generates from your document. Supporting files include:
After you run Mif2Go, control files and viewer files must be copied from the viewer folder (see §9.2 Setting up OmniHelp viewer control files) to the final distribution folder for your project. Mif2Go can do this for you; see §9.13 Assembling OmniHelp files for viewing.
To view OmniHelp, the view folder must contain the following:
• all files marked Required in column View? in Table 9-1 (including either oh*.htm or ox*.htm, depending on the start-up file type; see §9.3.7 Specifying the start-up file type).
• all files listed in Table 9-2.
Graphics files must be placed either in the same folder as the generated OmniHelp HTML files, or in a subfolder. If your graphics files are located elsewhere, they must be copied to the folder with the HTML files, or to a subfolder. Mif2Go can do this for you. For example:
CopyGraphicsFrom = g:/omnisys/ug/graphics2
§9.13 Assembling OmniHelp files for viewing.
§33.5 Placing graphics files for distribution
A browser loads optional files (marked Optional under View? in Table 9-1), only when you specify the features they support, via configuration settings. Your project might not require all the optional files. For example, if you do not want full-text search, you can omit ohfts.js from the OmniHelp view folder; and if you are not merging OmniHelp projects, you do not need ohmerge*.* in the view folder.
See §9.2 Setting up OmniHelp viewer control files.
> 9 Generating OmniHelp > 9.3 Setting up an OmniHelp project > 9.3.10 Getting OmniHelp supporting files in the right place