Difference between revisions of "Developing new JASigning Apps"
John.Glauert (talk | contribs) (Initial version.) |
John.Glauert (talk | contribs) |
||
| Line 17: | Line 17: | ||
The classes in <code>use-jarp</code> create GUIs for the apps and then accept SiGML data on a socket, or play SiGML files specified by URLs. By copying and modifying an existing class, new apps can be built with access to the main methods used by apps and applets. | The classes in <code>use-jarp</code> create GUIs for the apps and then accept SiGML data on a socket, or play SiGML files specified by URLs. By copying and modifying an existing class, new apps can be built with access to the main methods used by apps and applets. | ||
| − | Assuming that the installation is in a directory <code>loc2015</code> the | + | Assuming that the installation is in a directory <code>loc2015</code> the Netbeans project is <code>loc2015/JASApp</code>. Netbeans will create |
<code>loc2015/JASApp/dist/JASApp.jar</code>. To use the application outside Netbeans, a command such as: | <code>loc2015/JASApp/dist/JASApp.jar</code>. To use the application outside Netbeans, a command such as: | ||
java -Djava.library.path=jas-libs -Dlog4j.configurationFile=../log4j2.xml -jar dist/JASApp.jar \ | java -Djava.library.path=jas-libs -Dlog4j.configurationFile=../log4j2.xml -jar dist/JASApp.jar \ | ||
Revision as of 16:36, 26 May 2015
Developing new JASigning Apps
The standard JASigning installation at JASigning Current Release provides access to Javadoc files for some of the key
modules of the avatar signing system. It also provides access to the source code for use-jarp which contains classes
for the main example applications and applets.
Downloading and Building Freestanding JASigning Apps
A version of the JASigning installation configured for a server running on localhost is documented at JASigning Local Installation with instructions for downloading and installation.
Within the installation is a NetBeans project JASApp containing the use-jarp sources and configured to access the jar files containing the main JASigning classes. A few project properties may need to be adjusted to build the project on a user's system. The code is compiled using Java 1.7. It should be possible to make a clean build of the project and run the SiGMLPlayer app.
Developing new Apps
The classes in use-jarp create GUIs for the apps and then accept SiGML data on a socket, or play SiGML files specified by URLs. By copying and modifying an existing class, new apps can be built with access to the main methods used by apps and applets.
Assuming that the installation is in a directory loc2015 the Netbeans project is loc2015/JASApp. Netbeans will create
loc2015/JASApp/dist/JASApp.jar. To use the application outside Netbeans, a command such as:
java -Djava.library.path=jas-libs -Dlog4j.configurationFile=../log4j2.xml -jar dist/JASApp.jar \ -session file:../SiGMLPlayer -ja.version.tag=loc2015 -ja.remote.base.url=file:../../loc2015/
can be used from the JASApp directory. For information on arguments see Passing Arguments to JASigning Apps.
Implementation Details
The following information from the JASigning installation directory is used when building apps in the NetBeans project:
jarfiles from thejarsfolderjarfiles from thejoglfolder
When run from the JASApp directory with the parameters shown above, the following data is accessed
from the installation directory:
- Avatar definitions from the
avatarsfolder - Application properties from the installation directory
- Logging configuration from the installation directory
JASApp.jar and the lib folder containing runtime jar files could be placed elsewhere as long as suitable parameters are provided to locate data files. Note that URLs can be used so data for the standard release can be accessed.