The fliplay applet
The two class files "fliplay.class" and "flickframe.class" are needed.
Then the applet has to be initialized in a html-page. The fliplay applet
allows the usage of several parameters. A typical example is given here:
<APPLET code=fliplay.class width=320 height=200>
<PARAM name=File value=fishix.fli>
<PARAM name=Speed value=30>
<PARAM name=Loops value=10>
<PARAM name=End value=-1>
The width and the height values have to correspond with the size of
the fli/flc-animation. The parameter "File" points to the fli/flc-animation.
The best way is to keep all files together in one directory. The two class
files, the fli/flc-file and the html file. Only the "File" parameter is
obligatory. The following table explains the function of the other parameters:
||Delay time between frames in milliseconds
||Number of loops to be played (-1 = infinite)
||Number of frame, which is displayed when the animation stops after
N loops. Negative number means counted backwards from the end of the fli/flc-animation.
||If "yes", the auto-reverse (Ping-Pong) play is enabled.
||If "yes", the animation is played backwards.
||If "yes", a control panel occurs when the animation is stopped by mouse
||If "yes", then the animation can be controlled interactively by the
||Defines the block height for the internally used patch blocks.
A smaller value may save memory but can slow down the animation.
||If "yes", then internally used boxes are marked and displayed. This
is mainly for control purposes and disturbs the original images.
||If "yes", a lot of internal information is written to the Java console.
||Color of the text. During loading the
first frame is displayed and the number of the currently loaded frame
is written in the lower left corner using the specified color.
||Set the color style for the panel, which appears when the animation
is stopped by mouse click.
||Minimum delay time in milliseconds
||Maximum delay time in milliseconds
||If "yes", the input file is a ZIP file, which contains as first entry
the FLI/FLC file
Back to main page
The applet stores internally images which contain parts of the animation
frames. The border of these images can be made visible by setting the "Box"
parameter to "yes". Routines of the Java library are used to manage the
images. Therefore the images may occupy a large amount of memory depending
on the animation, the browser, the window system and perhaps some version
numbers. When the animation is loaded something like:
"Update Pixels: 419070 (13.0959375 %)"
is written to the Java console. The first integer number indicates the
sum of the pixels of all internally stored images. On true color systems
- using a standard browser - the memory requirement can be four bytes per
stored pixel. Thus, in the given example 1.6 Mbytes are occupied on some
machines to store the images. The size and the number of the internally
used images depends on the "Block" parameter. A lower value typically increases
the number of images but decreases the overall pixel count. Because all
the images have to be processed the animation speed may be reduced, when
the "Block" parameter is reduced. If memory consumption is a problem various
values of "Block" should be tested (below 16 is usually not reasonable).
No problems with colors occur on true color systems. When the fliplay applet
is started on systems in 256 color mode some colors might be distorted.
This depends on the colors used in the FLI animation and on the colors
required for the window system or other applications. If there are not
enough free colors, sometimes the browser/system assigns a spare color
which is close to the disired one. Other browsers/systems dither the images.
However, FLI animations with many colors might have probelms on some systems.
To reduce the transferred data the FLI files can be compressed.
Therefore the FLI file is compressed in a ZIP archive.
Best is to have only one entry in the ZIP archive.
The parameter "ZipFile" indicates, if a normal FLI/FLC file is loaded
or a compressed one.
This option may not work with older browsers, because classes from
a newer Java version are used.