Since the 0.7.0 release a simpler method for deploying applications has been integrated into LG3D. Previously, only those classes built as part of the incubator project, or configured into the sources of the cvs release could be easily added to lg3d. With this change all that is required is to jar the file correctly and put it in the ext/app directory. When a correctly configured jar file is found in the ${LG3DHOME}/ext/app directory it is added to the taskbar.
The process is as follows:
${LG3DHOME}/ext/app directory for any jar files and adds these to the classpath. This means that the applications and any resources are made available to LG3D.${LG3DHOME}/ext/app directory are then processed to determine the configuration of the application. This processing occurs by examining the Manifest file within the jar file. From the information in the jar file a standard configuration event is created and passed to the lg3d event system, resulting in an appropriate launcher being added to the taskbarManifest files provide a range of meta information about a jar file. This information can be used by java programs to determine certain characteristics, and help load environment variables required by the application within the jar file for successful execution. More information about manifest files can be read on at http://java.sun.com/docs/books/tutorial/jar/manifest/index.html.
LG3D uses/defines the following application parameters:
CLASSPATH. LG3D automatically adds the jar files in ext/app to the CLASSPATH therefore any resources bundled with the jar are accessible.
For examples on deploying applications via this method please visit the LG3D Tutorials at: https://lg3d-core.dev.java.net/tutorial.