File Properties - Dependencies

You are editing the Dependencies properties of an HTML page that is compiled in a publication with HTML Executable.

If an HTML page contains active objects like Flash, Java applets or other ActiveX controls, they may require additional resource files (like JPEG picture files, FLV video files, CLASS files). In some cases, an ActiveX control does not automatically request these files and thus it will not work properly because these files are missing.

For instance, in HTML Viewer publications, if you have a Flash movie (SWF) that requires a video file (FLV), the Flash Player does not request that video file itself and your Flash movie will not play your video.

The solution is to tell the runtime module that some resource files are required when an HTML page is displayed: these resource files are called dependencies of the HTML page.

When the HTML page is loaded, the runtime module:

  • extracts all dependencies to a temporary folder, and thus they can be found by the ActiveX control (HTML Viewer publications).

  • OR delivers them through HTTP thanks to the built-in server if it is enabled (IE publications).

Example

You have a Flash player control embedded in an HTML page named “player.html”. This Flash player should play a Flash video named “loco.flv”.

In HTML Executable, choose File Manager, select “player.html” and click “Properties” in the toolbar. In the “Dependencies” tab, click Add File(s) and select “loco.flv” in the displayed list. You should get this result:

On this screenshot, we already have two dependencies for “player.html”: “loco.flv” and “loco.jpg”. The jpeg file is used by the FLV player (front picture). When the HTML Viewer loads “player.html”, it will automatically unpack “loco.flv” and “loco.jpg” too. Thus, the Flash player will be able to read them and play the video.

You can manage dependencies for any HTML page: see a screencast about how to add dependencies for an HTML page.

Virtualization

HTML Executable uses virtualization to protect your files. Instead of unpacking dependencies to the hard disk, the runtime module keeps them in memory: it creates virtual files. Thus, end users cannot find your unpacked files on their hard disk and copy them.

By default, virtualization is turned off, but you can enable it if you want thanks to two ways:

  • right click on a file in the “Dependencies” list, and choose “Force Virtualization for this File“:

  • in the Application Behavior => Content Filetypes page, add the file extension and choose “virtual file” as the availability method.

© G.D.G. Software 2015. All rights reserved.