This tells the applet where to look for certain file types when it is running on the web-server. In all three cases you should specify a path relative to the HTML file that contains the <applet> or <object> HTML. The default folder is ".", or the same folder as the HTML file.

Note:
Absolute paths beginning with a slash, or even http://, will be accepted, however we recommend you use relative paths.

Determines which folder the BtnPlayer.class and archive files (.cab and .jar) are loaded from. This folder is typically a path relative to the location of the HTML file. The default is ".", or the same folder as the HTML file.

Examples:
The parent folder = ".."
JavaClasses sub-directory = "../JavaClasses"

Determines which folder bitmaps are loaded from. This folder is typically a path relative to the location of the HTML file. The default is ".", or the same folder as the HTML file.

Examples:
The parent folder = ".."
Images sub-directory = "../images"

Determines which folder sounds are loaded from. This folder is typically a path relative to the location of the HTML file. The default is ".", or the same folder as the HTML file.

Examples:
The parent folder = ".."
Audio sub-directory = "../audio"

Identifies the applet when called by JavaScript code. If a single HTML page contains more than one applet, the Applet Name can be used to identify which applet is being called by the script. By default, the applet name is the same as the project name.

See also The Significance of the Applet Name.

Specifies whether to include content used by the applet in a compressed archive file. 1 Cool Button Tool builds two archive files; a Cabinet (.cab) file for use by Internet Explorer, and a Java Archive (.jar) for use by Netscape 4. (Netscape 3 and earlier does not support compressed archive files).

If this option is checked, the archive files will be called projectname.cab and projectname.jar respectively. If this option is not checked, only the BtnPlayer.class file will be included in the archives, and the archive files will be called BtnPlayer.cab and BtnPlayer.jar.

The advantage of using an archive is that the applet and all its content will be downloaded in a single HTTP transaction, which considerably improves the download time for content-heavy applets. In addition, when GIF animation's are restarted, the animation is reloaded from the archive, rather than the server, which would otherwise be the case.

However, applets which use an archive will take longer to start running because the entire archive must be downloaded before the applet can start. Also, if you are running many button applets on the same page (or different pages at the same site), it can be more efficient to not use archives. This is because the common archive file (BtnPlayer.cab/BtnPlayer.jar) can be shared by multiple applets, and will be downloaded once only.

Note 1:
You can only create JAR files if your system has the Java Virtual Machine (JVM) installed. If you do not have the latest JVM, no JAR files will be created. See the FAQ for help on upgrading your JVM.

Note 2:
The .cab and .jar files serve the same purpose as the BtnPlayer.class file. If the .cab and .jar files are not uploaded to your web server, the button applet may not run.