|
Application Programming: Providing Online Help For Your Application |
|
If you prefer not to use IDL's cross-platform help viewer, you can use the ONLINE_HELP procedure to display help files in other formats. The type of help file or files you choose to create will depend on the platforms on which your IDL application will be used, and on your own preferences.
There are currently two Windows online help formats in wide use: WinHelp and HTML Help. WinHelp is the older of the two, and many applications still provide help in this format, which can be distinguished by the file extension ".hlp". HTML Help is the newer format, and provides (among other things) the ability to include links to documents in various formats, both local and network-based. HTML Help files use the file extension ".chm". Viewers for both types of online help are included in all relatively current versions of Windows, and IDL's ONLINE_HELP procedure will invoke the correct viewer for either type of file.
Microsoft Windows help files are relatively easy to create. Files in a specified format (the Rich Text Format, (RTF) for WinHelp, or a wider variety of formats for HTML Help) are compiled with a help compiler from Microsoft. The help compiler is part of the Windows Software Developer's Kit, and is now included in several Microsoft programming products, including the Visual C++ development environment. The help compiler may also be available from the Microsoft Web site or other Microsoft online software libraries at little or no cost.
It is beyond the scope of this manual to discuss the preparation and compilation of Windows help files. Microsoft provides useful information about its help-system products as part of the Microsoft Developer's Network; try searching the MSDN site at http://msdn.microsoft.com with the search term "HTML Help" or "WinHelp". There are also numerous third-party books on creating Windows help systems available.
To call a Windows help file of either type from within IDL, use the ONLINE_HELP procedure. Specify the name of your help file using the BOOK keyword, and optionally specify a search term in the Value argument. Alternatively, you can specify a context number in the Value argument and include the CONTEXT keyword. See ONLINE_HELP for details.
Depending on where your application and its help files are installed, you may also need to specify the full path to the file and the FULL_PATH keyword.
Suppose you have created an HTML Help file named myapp.chm to accompany your IDL application. Use the following call to open the HTML Help viewer and load the search term "controls" into the Index dialog:
ONLINE_HELP, 'controls', BOOK='path\myapp.chm', /FULL_PATH
where path is the full path to the file myapp.chm.
Suppose you have created a WinHelp file named myapp.hlp and placed it in the Help subdirectory of your IDL installation. If you know that the context number of the topic you wish to display is 250, use the following call to open the WinHelp viewer to the correct topic:
ONLINE_HELP, 250, BOOK='myapp', /CONTEXT
If no file extension is included in the value of the BOOK keyword, IDL will search each directory in !HELP_PATH until it finds a matching file with one of the following file extensions, in this order: .chm (Windows only), .hlp (Windows only), .pdf, .html, .htm. See Paths for Help Files for details on setting the help path.
Windows help files (of either format) are viewable only on Microsoft Windows platforms. If your IDL application will be available on UNIX platforms as well as Microsoft Windows platforms, you have several options:
You can use the ONLINE_HELP procedure to display a PDF file on any system that has a PDF-display application installed.
| Note IDL launches a stand-alone version of the PDF viewing application. Files are not displayed in the Windows help viewer or any other browser application. |
To create PDF files for use with IDL's online help system, you will need an application that allows you to author PDF files or convert files in other formats to PDF. Most commonly, source files are created with a text-editor, word-processor, or other document-production program, printed to a PostScript file, and run through a program that distills the PostScript into PDF. Adobe's commercial Acrobat package includes the Acrobat Distiller, which provides a convenient GUI interface to the distillation process. Other third-party software to distill PostScript files into PDF is also available; GhostScript (www.ghostscript.com) is one freely available alternative.
It is beyond the scope of this manual to discuss creation of PDF files in detail; consult the documentation for your PDF authoring system or distilling software for details.
To call a PDF help file from within IDL, use the ONLINE_HELP procedure. Specify the name of your PDF file using the BOOK keyword. Depending on where your application and its help files are installed, you may also need to specify the full path to the file and the FULL_PATH keyword.
See ONLINE_HELP for details.
Suppose you have created a PDF file named myapp.pdf to accompany your IDL application. Use the following call to open the PDF viewer and display the first page of the file:
ONLINE_HELP, BOOK='path\myapp.pdf', /FULL_PATH
where path is the full path to the file myapp.pdf.
If the myapp.pdf file is located in one of the directories included in IDL's !HELP_PATH system variable, you do not need to include either the .pdf extension or the FULL_PATH keyword:
ONLINE_HELP, BOOK='myapp'
If no file extension is included in the value of the BOOK keyword, IDL will search each directory in !HELP_PATH until it finds a matching file with one of the following file extensions, in this order: .chm (Windows only), .hlp (Windows only), .pdf, .html, .htm. See Paths for Help Files for details on setting the help path.
If you intend to use PDF files to supply online help for your cross-platform application, you should caution your users that they must have a the appropriate PDF viewing application installed in order to use your help file. In addition, UNIX users must ensure that the viewing application is properly configured for use by IDL, as described in Displaying HTML and PDF Files under UNIX under ONLINE_HELP.
You can use the ONLINE_HELP procedure to display an HTML file on any system that has a Web-browser installed. On UNIX systems, the browser's executable file must also be in a directory included in the PATH environment variable.
It is beyond the scope of this manual to discuss HTML authoring in detail. Use any technique you are comfortable with to create HTML files for display in a normal Web browser.
| Note You can use the MK_HTML_HELP procedure to create HTML-formatted documentation for your application from standard IDL documentation headers. See MK_HTML_HELP for details. |
To call an HTML file from within IDL, use the ONLINE_HELP procedure. Specify the name of your HTML file using the BOOK keyword. Depending on where your application and its help files are installed, you may also need to specify the full path to the file and the FULL_PATH keyword.
See ONLINE_HELP for details.
Suppose you have created an HTML file named myapp.html to accompany your IDL application. Use the following call to open the default Web browser and display the file, positioned to the HTML anchor tag anchor1:
ONLINE_HELP, 'anchor1', BOOK='path\myapp.html', /FULL_PATH
where path is the full path to the file myapp.html.
If the myapp.html file is located in one of the directories included in IDL's !HELP_PATH system variable, you do not need to include the .html extension or the FULL_PATH keyword:
ONLINE_HELP, BOOK='myapp'
If no file extension is included in the value of the BOOK keyword, IDL will search each directory in !HELP_PATH until it finds a matching file with one of the following file extensions, in this order: .chm (Windows only), .hlp (Windows only), .pdf, .html, .htm. See Paths for Help Files for details on setting the help path.
If you intend to use HTML files to supply online help for your cross-platform application, keep the following things in mind:
IDL Online Help (March 06, 2007)