Data Optimization
HTML Executable aims to generate the smallest publication files. This is especially done via file compression.
File compression:
Strong compression algorithms are used in HTML Executable (superior to the standard Zip method used in HTML Executable 3.1). Although these algorithms are pretty fast, compressed source files may take some time before they can be displayed in publications. That's why you can define the level of file compression: it determines how hard the compression algorithms will try to compress your source files.
You can select between three levels: Minimum, Default and Best. The last level is "Disable": in this case there is no compression (files are just stored, uncompressed). The "Best" level will compress the slowest, but the compression ratio will be the highest.
It is up to you to choose the most suitable compression level according to the source files you are going to compile, the configuration of the publication's target computers, etc...
Note: you can disable compression for specific files (especially for compact files like MP3 sounds or zip archives) via the File Properties.
Disable special HTML and text compression method: HTML pages and text-based files are first compressed using a special text compression algorithm, which results in a better compression ratio. However this method is a bit slower than the general compression algorithm. If you prefer to gain speed in compression and decompression, then turn this option on.
Enable fast decompression: turn on this option if you want to increase loading speed on very old machines. No significant changes will happen on recent machines so it is better to leave this option turned off as it will increase your publication .exe file's size.
Enable size optimization: if you really want to save some additional bytes, then turn this option on. But in this case, the initialization of the publication can take more seconds.
Do not compress the search engine data: for very large publications that must be run on old computers, this option may be useful. When it is enabled, the search index is not compressed, but stored. This will of course increase your publication .exe file's size.
Runtime Module
Dedicated topic about runtime modules
Code signing
Dedicated topic about code signing
Map IDs
If you are a programmer, then you can use HTML Executable to compile help files or documentation in HTML format for your applications. You can use the HTML Executable APIs to open help publications, to tell them which help topic should be displayed, to close them when your application is closed, etc... This lets you integrate publications with your own applications.
Instead of specifying the HTML page's filename of the help topic you want to display, you can pass a numeric ID to the API or the command line. In fact, HTML Executable automatically associates a unique ID (page ID) to each HTML page it compiles into a publication.
The list of all of these IDs is called a map. You can configure HTML Executable to export the map to a file (called MAP file) that can be directly integrated into your application's project.
Currently HTML Executable can generate MAP files in Object Pascal (for Borland Delphi), C/C++ (for Borland C++ Builder or Microsoft Visual C++) and in simple text files. Just select the kind of language you want.
The map file is automatically created in the same folder as the output file (if the option is enabled).
You can also add your own custom page IDs (like HTML anchors, HEScript commands) if you want to work with map IDs or the HTML Executable API SDK. They will be automatically exported in the map file. To add a custom page ID, click Add and enter its target. To remove a custom page ID, select it and click Remove.
 | You can also pass map IDs via the command line. |