If you wish to convert your applet code to a .js link, the Encoder will create this if you check [] Generate JS/HTML when finished encoding. The Encoder will generate the .js include and a web page that includes both the link to that .js file and an applet reflecting standard parameters.



If you have a .js link that you wish to embed in a custom page, you will need to link to the .js file from the page where you wish the video or audio clip to appear.

1. Upload your .js file to your webserver and take note of its URL location.
2. Open up the code for the target page where you want the video to appear.
3. Write or copy this line of code, replacing the [URL of your .js file] with the location where you uploaded the .js file:
   
   <SCRIPT LANGUAGE="JavaScript" SRC="[URL of your .js file]"></script>
   
4. Save and upload.
   
   When you view the page in your browser it should display as if you had the applet normally pasted in the page.
   
   
   NOTE: Since this requires javascript enabled, any browsers that do not enable it will not see this.

In 2006 Microsoft was required by a legal judgment to remove embedded media functionality from its Internet Explorer browser. This meant that any video or audio that was embedded in a web page -- when viewed using IE -- could not be played unless the user clicked on the interface twice. Before that, buttonsets such as play or pause or stop would work with a single click. Other browsers (Firefox, Opera, Safari) were not affected by this judgment. Including applets as .js links, however, brings back the single-click functionality.

Embedding the Clipstream™ content as a .js link also is simpler and more elegant in the page code than including the entire applet.

You may include both the applet and the .js link if all of the parameters match and if you are concerned that someone has enabled Java but not Javascript. If you do not have that concern, we suggest eliminating the applet code and keeping the .js link and the .js file.

You must make sure that the parameters in the .js and the applet file matches. Modern browsers will read the .js first and then ignore the applet. If you find the changes you make are not reflected in the browser, it is probably because you did not also make the changes in either the .js or the applet.

The applet will load normally but a box will appear around it. The user can press space-bar or right click to enable the applet. Then the applet will be allowed to function normally.

-or-

The user can click on the button panel *twice* and it will play.

If the applet is set to autoplay, then the applet will play normally as this does not require user activation.