EverJ's director applets tech summary.
director0. The simpliest single-frame, history-unsafe director applet.
File arrangement.
Put somewhere a HTML document file, containing the following
tag(missing terms explained below):
<applet width=2 height=2 codebase="classes_path" code="director0.class">...</applet>.
Put "director0.class" file somewhere on the same host
as the HTML file. If you put it to the same directory as the document,
don't use codebase parameter in the <applet..> tag, otherwise register
class location using codebase, where classes_path points to the class file's
directory path, absolute or relative to the document base. Note: if you
test it on the local computer only the first variant is acceptable.
The tag.
<applet width=2 height=2 codebase="classes_path"
code="director0.class">
<param name=frame value="the_frame">
<param name=location value="the_document_location">
</applet>.
width - applet's width;
height - applet's height;
codebase - applet class location, relative to the document location
or absolute;
code - applet class file name;
the_frame - the name of the browser's frame to load into, special
words (_self , _top , _parent , _blanc) are acceptable;
the_document_location - the document to load.
Usage.
By standard hiperlink mechanism the browser loads a single document
in a single frame when some lik is clicked on. When this applet is embedded
into a page, the Java-enabled browser performs double loading - the first
document as defined in <a href..> tag and the second
as defined in the first document in director's <applet..>
tag. Using the chaining, one can define the multiple loading.
Another usage of this applet is to distinguish Java-enabled browsers from
others, as it was done in owr home page.
Important. This applet locks the browser's previous history (that is, once
having loaded this applet, the user couldn't come to any earlier loaded
documents by simple pressing browser's "Back" button).
File arrangement.
Put somewhere a HTML document file, containing the following
tag(missing terms explained below):
<applet width=2 height=2 codebase="classes_path" code="director1.class">...</applet>.
Put the "director1.class" file somewhere
on the same host as the HTML file. If you put it to the same directory
as the document, don't use codebase parameter in the <applet..> tag,
otherwise register class location using codebase, where classes_path points
to the class file's directory path, absolute or relative to the document
base. Note: if you test it on the local computer only the first variant
is acceptable.
The tag.
<applet width=2 height=2 codebase="classes_path"
code="director1.class">
<param name=frames value="frame1,frame2,...,frameN">
<param name=frame1 value="the_document1_location">
<param name=frame2 value="the_document2_location">
..................................................
<param name=frameN value="the_documentN_location">
</applet>.
width - applet's width;
height - applet's height;
codebase - applet class location, relative to the document location
or absolute;
code - applet class file name;
"frame1,frame2,...frameN" - the list of the frames to
load into, special words (_self , _top , _parent , _blanc)
are acceptable;
the_documentX_location - the document to load in frameX frame.
Usage.
By standard hiperlink mechanism the browser loads a single document
in a single frame when some lik is clicked on. When this applet is embedded
into a page, the Java-enabled browser performs multiple loading - the first
document as defined in <a href..> tag and the others
as defined in the first document in director's <applet..>
tag.
Another usage of this applet is to distinguish Java-enabled browsers from
others, as it was done in owr home page.
Important. This applet locks the browser's previous history (that is, once
having loaded this applet, the user couldn't come to any earlier loaded
documents by simple pressing browser's "Back" button).
File arrangement.
This applet usage involves at least two HTML document files,
containing the following tags(missing terms explained below):
The first:
<applet width=2 height=2 codebase="classes_path" code="director2.class">
<param name=next value="second_document_location">
......................
</applet>
and the second:
<applet width=2 height=2 codebase="classes_path" code="director2.class">
......................
</applet>
Put "director2.class" file somewhere
on the same host as the HTML files. If you put it to the same directory
as the document, don't use codebase parameter in the <applet..>
tag, otherwise register class location using codebase, where classes_path
points to the class file's directory path, absolute or relative to the
document base. Note: if you test it on the local computer only the first
variant is acceptable.
The tag.
<applet width=... height=... codebase="classes_path"
code="director1.class">
<param name=next value="next_document_location">
<param name=frames value="frame1,frame2,...,frameN">
<param name=frame1 value="the_document1_location">
<param name=frame2 value="the_document2_location">
.................................................
<param name=frameN value="the_documentN_location">
</applet>.
next_document_location - this parameter registers the next document
location relatively to current document;
width - applet's width;
height - applet's height;
codebase - applet class location, relative to the document location
or absolute;
code - applet class file name;
"frame1,frame2,...frameN" - the list of the frames to
load into, special words (_self , _top , _parent , _blanc)
are acceptable;
the_documentX_location - the document to load in frameX frame.
Usage.
To avoid the locking of the browser's previous history the mechanism
of preliminary registering is used. This means that the forwarding is performed
only if the current page location was preliminary registered (using the
'next' parameter) by the last of previous pages,
containing this applet.
In the rest the usage the same as in director1 applet.