The appletviewer command allows you to run applets outside of the context of a World-Wide Web browser.
appletviewer [ options ] urls ...
The appletviewer command connects to the documents or resources designated by urls and displays each applet referenced by the documents in its own window. Note: if the documents referred to by urls do not reference any applets with the APPLET tag, appletviewer does nothing.appletviewer supports the use of native MIPS instructions instead of Java bytecode in order to improve Java runtime performance. The MIPS instructions can be generated on the fly (see the -jit option below) or can be generated ahead of time by javat and read from the .class file (see the -tran option below). Using the -jit and -tran options together causes MIPS code to be read in from .class files where possible, and causes code in other classes to be translated when they are loaded at run time. The default is -jit -tran. For more details, see here.
The following options support the use of native MIPS code generated directly from the Java bytecode:
- -debug
- Starts the applet viewer in the Java debugger - jdb - thus allowing you to debug the applets in the document.
- -J javaoption
- Passes through the string javaoption as a single argument to the Java interpreter which runs the compiler. The argument should not contain spaces. Multiple argument words must all begin with the prefix -J, which is stripped. This is useful for adjusting the applet viewer's execution environment or memory usage. For example, the following command will run the applet viewer with a maximum heap size of 64MB:
% appletviewer -J-mx64m ...
- -jit/-nojit
- Causes/prevents translation of the code for each class when it is loaded. The current default is -jit.
javat