Applet architecture

We offer an applet-version of Terasology for easy review in a light-weight version of the game that'll run in a browser. It won't be quite as easy to interact with saved worlds or use plugins this way, but it is the fastest way to check out the game!

Overview

As of this writing we're using the LWJGL applet loader and signing our jar file so Groovy can do its thing (introspection / reflection) that's a little beyond what a normal applet is allowed within the Java security model. Everything is automated in the Gant build of the application with the right target executed. A source HTML file exists under source control that we use to load the applet.

To get log output from a running applet you have to enable the Java Console at the OS level - in Windows look for the Java item in the Control panel. You also have to enable extra logging under the same Java item.To clear your applet cache (in case the applet is updated and it looks like you're still loading the old version) look under a path similar to

C:\Users\Cervator\AppData\Local\Temp\lwjglcache= (on Windows, anyway)

The logging ends up (on Windows) at a place like:

C:\Users\Cervator\AppData\LocalLow\Sun\Java\Deployment\log

Game data has been changed to save to a path like

C:\Users\Cervator\AppData\Roaming\.terasology

For needed enhancements see the bugtracker

Related Links

• Signed Applets by Oracle
• LWJGL applet loader
• Tutorial page specific to Groovy in an applet
  • Includes instructions for minimizing the size of the Groovy jar
• how to enable the Java Console for applet output if need be