| Java menu knowledge base
Putting an applet in a webpage
How to insert the applet into your HTML page.
When putting applets into web pages, it's best to use a
direct HTML code editor that allows you to view and edit
the HTML directly.
Start off by copying and pasting the following into
your HTML. Place this at the point where you wish to
have your applet.
<applet code="[nameOfApplet].class" width=600 height=24 mayscript viewastext>
<param name=copyright value="Image Intelligence Ltd. (www.imint.com)">
<param name=licencee value="[as delivered]">
<param name=cabbase value="[nameOfApplet].cab">
<param name=escapepage value="non_java_menu.html">
.....
<param name=archive value="[nameOfApplet].jar">
</applet >
CODE: the name of the applet file may vary from version to version.
If you are not sure what the applet is called, then look carefully at
the HTML source code of the sample in your delivery package and copy
the CODE attribute from there.
For your interest, this is how we generally name our applets:
imint.com applet filenames have a prefix specifying the
applet range (e.g. "is" = iSlide), an alphanumeric infix specifying
the level (e.g. "p" = pro),
another alphanumeric infix specifying
the applet name (e.g. "ss" = synchro-slide menu), and a suffix with
the version number (e.g. "650" = version 6.50). Do NOT
try to enter a path in the CODE attribute - just the filename.
HEIGHT / WIDTH: they determine the
height and width of the applet. Check out our support area
if you want to use page-proportional sizing.
COPYRIGHT / LICENCEE: the copyright and licencee information
must also be entered exactly as delivered - otherwise the applet won't work.
Free and trial applets won't need licencee information. Some free applets
may have a slightly older version of the copyright string than that shown
above - look carefully at the HTML source of your delivery package.
CABBASE: the cab file is a compressed version of
the applet for use with Microsoft java interpreters.
Set the CABBASE parameter to point to the CAB file in your delivery package, if there is one. CAB files are normally only delivered with release versions of Pro/Pro-X applets.
ARCHIVE: the jar file is a compressed version of
the applet for use with non-Microsoft java interpreters.
Set the ARCHIVE parameter to point to the JAR file in your delivery package, if there is one. JAR files are normally only delivered with release versions of Pro/Pro-X applets.
MAYSCRIPT: many of our applets are able to fire
your own javascripts. However to enable the applet to do this, you
must include "mayscript" in the applet tag as shown in the example.
ESCAPEPAGE: set this to point to your non-java menu. Don't forget to write a non-java menu page and read the information in the online advice centre about using escape pages. You should only put in the escapepage after
you have finished designing and testing your menu implementation, because if
there is an escapepage, the very useful error-reporting system is deactivated.
APPLET: the applet tag is not the only way to put applets
into pages, and some people complain that it is old-fashioned. However the
truth is that the APPLET tag is (at the time of writing - Dec 2001) the
only universal way and the simplest way to do it.
PLUG-INS: if you see claims that Microsoft
browsers might work better if a "java plug-in" is used (together with code
for using this plug-in), please realise that such claims originate from
vested interests and may not be objective.
As the vast majority of web users use Microsoft browsers and Microsoft
java interpreters, we take this into account when programming our software
and ensure that our applets work excellently in Microsoft-only environments.
|
|
