The Applicet Framework for Applets and Applications gives full support for running applets as applications, just by by replacing java.applet.Applet
as superclass by be.arci.applet.Applicet
"But I can do this myself!"
It is popular belief that all you have to do to run an applet as application is to add a main()
method calling init()
on your applet instance. But why then are there so few applets that run as an application as well? The answer is simple: while the simple main()
method might be enough for very basic applets, it is not at all the case for most (if not all) usefull applets. About anything an applet needs (apart from it's own canvas to draw on), it'll have to ask for from it's AppletStub
and it's AppletContext
. For that is what Applet's methods do.
You need the Applicet Framework
The Applicet Framework gives Applicet applications the necessary implementations of the java.applet.AppletStub
interfaces that are needed to run an applet as application without changing any code, and without having to branch on switches you maintain to distinguish between both execution environments.
In addition, using the Applicet Framework gives you a set of convenience methods every Applet programmer needs. It also still allows you to display HTML pages when needed. Further the Applicet Framework gives uniform support across application environments for retrieving resources as Image
. You can use all packaging options with Web browsers like MS IExplorer and Netscape Communicator, like all jarred, all unjarred, or mixed to have volatile resources unjarred. And last but not least, the Applicet Framework makes internationalization of your applet/application trivial.