#### 16.2.3 Launching a Help viewer from the Project Manager

When you use the DITA2Go Project Manager to run a conversion, you can view the output immediately with the View Output button on the Run Project tab, provided both of the following are true:

- the key output file for the Help system is located in the wrap directory
- if a command is needed to launch the viewer, you have specified that command.

For OmniHelp, HTML Help, and WinHelp, you do not have to supply a command to start the viewer at the default topic, as long as the name of the key file (for OmniHelp) or the compiled system is located in the wrap directory. This is equivalent to specifying the default value (blank):

    [HelpOptions] or [OmniHelpOptions] or [MSHtmlHelpOptions]
    ; ViewOutputCommand = path\to\viewer, default none
    ViewOutputCommand =

For JavaHelp, Oracle Help, and Eclipse Help systems you will need to provide a command the Project Manager can launch to run the viewer.

    [JavaHelpOptions] or [OracleHelpOptions] or [EclipseHelpOptions]
    ViewOutputCommand = path\to\viewer

You can specify an absolute path or a path relative to the wrap directory. For example:

    [JavaHelpOptions]
    ViewOutputCommand = java -jar D:\JH2\demos\bin\hsviewer.jar -helpset

For Oracle Help, the command can be quite long, and must be all on the same line, even if it does not look that way here:

    [OracleHelpOptions]
    ViewOutputCommand = java -classpath "d:\ohj\ohj427\help4.jar;
    d:\ohj\ohj427\help4-demo.jar;d:\ohj\ohj427\ohj-jewt.jar;
    d:\ohj\ohj427\;d:\ohj\ohj427\oracle_ice.jar" oracle.help.demo.ChoiceDemo

For Eclipse Help, you are on your own.

See §1.3.7 Establish system-wide configuration settings.

Previous Topic: 16.2.2 Compiling and distributing Help systems

Next Topic: 16.3 Producing contents and index for Help systems

Parent Topic: 16.2 Completing Help system construction

Sibling Topics:

16.2.1 Specifying additional processing after conversion

16.2.2 Compiling and distributing Help systems