Omni Systems, Inc.

  

Mif2Go User's Guide, Version 55

  

Valid HTML 4.01!

 

Made with Mif2Go

10 Generating OmniHelp > 10.13 Assembling OmniHelp files for viewing


10.13 Assembling OmniHelp files for viewing

By default, Mif2Go copies all files with the following extensions from the project directory to the wrap directory (see §35.2 Activating and logging production of deliverables):

*.htm *.css *.js *.gif *.jpg *.png

You can change the list of files to be copied; see §35.6 Assembling files for distribution. Mif2Go automatically copies the necessary OmniHelp viewer files from the viewer-control directory to the wrap directory, according to the value of OHViewPath:

[OmniHelpOptions]

; OHViewPath = path to dir containing the OH viewer files

See §10.2.2 Making OmniHelp viewer control files available. By default, OHViewPath references the OmniHelp viewer files in one of the following directories:

%OMSYSHOME%\common\system\omnihelp\ohvhtm (for HTML output)

%OMSYSHOME%\common\system\omnihelp\ohvxml (for XHTML output)

If you put the viewer-control files somewhere else, you must specify the path (preferably absolute) to that location as the value of OHViewPath. Do not place the viewer-control files under the wrap directory. Mif2Go copies the files listed in Table 10-5 from the directory designated by OHViewPath to the directory designated by WrapPath, if specified, otherwise to the project directory.

Table 10-5 OmniHelp viewer files copied from OHViewPath to WrapPath

Start-up file type

OmniHelp viewer files copied to wrap directory by default

HTML

oh*.*

XHTML

ox*.htm ox*.js oh*.css oh*.js

The start-up file type (HTML or XHTML) determines which set of files will be copied; see §10.2.1 Choosing XHTML vs. HTML OmniHelp control files.

To have Mif2Go copy additional files to the wrap directory:

[OmniHelpOptions]

; OHVFiles = list of files to copy from OHViewPath (the viewer files).

OHVFiles = oh*.* some\other\files yet\more\files ...

The file specifications you assign to OHVFiles must be separated by spaces, and no spaces are allowed within a file specification. You can use wildcards in file specifications, and include absolute or relative paths to indicate where viewer files should be copied from. Relative paths are relative to the wrap directory.

The files you list for OHVFiles will be copied in addition to the files listed in Table 10-5. If you are not adding any special files of your own, there is no need to include a setting for OHVFiles. When you do not provide a setting for OHVFiles, the default value is based on the setting for OHProjFileXhtml; see §10.2.1 Choosing XHTML vs. HTML OmniHelp control files.

See also:

§7.2.4 Compiling and distributing Help systems

§35.6 Assembling files for distribution



10 Generating OmniHelp > 10.13 Assembling OmniHelp files for viewing