Contents - Cultural View

Java applet 35
}
}
g.drawString("Hello, world!", 20,10);
More simple applets are available at Wikiversity [23] .
For compilation, this code is saved on a plain-ASCII file with the same name as the class and .java extension, i.e.
HelloWorld.java. The resulting HelloWorld.class applet should be installed on the web server and is
invoked within an HTML page by using an or an tag. For example:
HelloWorld_example.html
A Java applet example
Here it is:
This is where HelloWorld.class runs.
Displaying the HelloWorld_example.html page from a Web server, the result should look as this:
A Java applet example
Here it is: Hello, world!
To minimize download time, applets are usually delivered in a form of compressed zip archive (having jar
extension). If all needed classes (only one in our case) are placed in compressed archive example.jar, the embedding
code would look differently:
Here it is:
This is where HelloWorld.class runs.
Applet inclusion is described in detail in Sun's official page about the APPLET tag. [24]
Advantages
A Java applet can have any or all of the following advantages:
• It is simple to make it work on Linux, Microsoft Windows and Mac OS X i.e. to make it cross platform. Applets
are supported by most web browsers.
• The same applet can work on "all" installed versions of Java at the same time, rather than just the latest plug-in
version only. However, if an applet requires a later version of the Java Runtime Environment (JRE) the client will
be forced to wait during the large download.
• Most web browsers cache applets, so will be quick to load when returning to a web page. Applets also improve
with use: after a first applet is run, the JVM is already running and starts quickly (the JVM will need to restart
each time the browser starts afresh).
• It can move the work from the server to the client, making a web solution more scalable with the number of
users/clients.