Applet Panel Shared Border Controls

Shared Borders Potential Problem Description
If you insert a FrontLook Java Effects applet into a shared border, it will likely work just fine until you attempt to view a page that is in a subdirectory off the root of the web. When viewing this page, you will likely note the applet area appears as a gray box. After putting your cursor in the applet area, you will note a "class file not found error" in the status bar of the browser. This is caused by relative references to the _frontlook directory where the applet support files are usually located. Since there is no _frontlook folder in the subdirectory, the files, including the java class file cannot be found. Several solutions are possible.

Solution 1
The easiest solution to use is to use a feature in the Java Effects product to support applet insertions into the shared borders. When inserting a FrontLook Java Effects applet into a shared border, remember to check the "Absolute reference for shared borders" checkbox on the Applet panel. This will make all the file references point to the _frontlook directory in the root of the web. This solution may not work when using sub webs, you will know this if you receive security access violation in the status bar of the browser when putting the cursor inside the applet.

When editing a disk web, two additional radio buttons appear under the "Absolute references..." check box. Because of Java Security, the applet will not preview on both the local disk web and the published the web to the server. A gray box will appear when the applet does not have access to its class files.

Special Options when editing a Disk Web

Therefore an option has been added so you can preview the applet locally for testing purposes and then set "Absolute references..." check box to Server Preview mode for when the web is published.

Note: The component will not preview on both the local disk web and the published the web to the server. During testing locally, select the "Local Preview" button so that the component can be viewed. Once testing is completed, select the "Server Preview" button so that when you publish the web, the component will operate properly. If you publish the component with the "Local Preview" button selected, the component will not operate properly.

Solution 2
In the case where solution one doesn't work, one can work around the problem in the following way. Uncheck the "Absolute reference for shared borders" checkbox on the Applet panel. Then bring up ONE page in each directory, double-click the applet in the shared border and them press ok. This will create a "_frontlook" folder with the proper support files in the directory.