In the “Output Path” field, please provide the full path to the final publication file (directory+filename). It is an executable file (.exe extension).
HTML Executable requires a title to use in message boxes and window title bars. The publication title consists of a short and descriptive phrase, such as ”My wonderful site” or ”Demonstration for E=mc²”. This title will finally appear in the Windows taskbar and task manager.
As ISBN identifies books, the publication GUID allows runtime modules to manage settings related to the publication on the end user's computer (see below). To generate a new GUID, you can press the right button.
Note that you should not change a GUID once your project is started.
If you want to share the same settings between different publications, give them the same GUID.
A publication stores its settings (user window preferences, favorites, trial information…) as local information on the user computer. If you test your publication on your own computer, you may want to remove or reset these settings: just click Reset Settings and answer Yes.
If you test your publication on different computers, you may need to remove the traces left by the latter. This button lets you generate a small cleanup program that will do this job. This program works exactly like the Reset settings option described above.
You can place this program (which is portable: no installation is needed) on a USB disk and run it on any computer that you want to remove the settings left by the publication from.
The generated program is for the current loaded project only: it does not remove traces left by another publication. Of course, this program shall not be distributed to others: it is for your personal use only, as it can even reset trial periods.
Shortcuts for launching the compilation
You have several ways to launch the compilation of your package:
About archive caching
When building a publication, HTML Executable first compresses the files into a single archive file which is then merged into the publication .exe file. The file compression is the operation that takes the most compilation time.
That's why HTML Executable stores a newly created archive into a temporary folder: we say it “caches” the archive. As long as you do not modify the source file list or compression options, HTML Executable will use this cached archive when building your publication instead of compressing all files again.
It works exactly like caches of Web browsers (places of temporary Internet files).