Documentation

Customization kit

The kit main purpose is to allow build custom version of JumpLoader. It is possible to alter resource files (images, properties) on build phase.

Environment requirements

In order to build custom version you need to install:

Java Development Kit (JDK) 1.4 or newer.
Apache Ant 1.6 or newer.

File structure

bin	Contains original applet files (classes, resources). It's content should not be altered.
images	Contains applet original images
jmaster	Contains applet binary files (compiled java classes)
view	Contains GUI configuration property files
gui.properties	Top level GUI property file (contains include directives)
gui_applet.properties	Applet specific GUI properties
gui_common.properties	Common GUI elements definition
gui_localfiles.properties	GUI properties for local file system tree view
gui_main.properties	GUI properties for main view
gui_upload.properties	GUI properties for upload view
build	The build directory
custom	Custom resources directory
jumploader_z.jar	The build product (will be created when build finished)
app_custom.bat	Execute JumpLoader application using custom resource files
app_default.bat	Execute JumpLoader application using original files
app_jar.bat	Execute JumpLoader application from JAR file
build.properties	Build properties file (need to alter, see below)
build.xml	Build script (do not alter)
make.bat	Build executable

Build process

Please install JDK and Apache Ant before building. Ensure that bin folders of JDK and Ant are registered in the PATH variable.

The build process flow is quiet simple, just type make command in the kit root directory and following steps will be executed:

build directory cleanup.
Copy original files (from bin) to the build directory.
Copy custom files (override original) to the build directory.
Create JAR from build directory.
Sign JAR.

If build was succesfull BUILD SUCCESSFUL message will be present and jumploader_z.jar file generated.

If build fails, BUILD FAILED message will be present, read previous console messages for error cause.

Last step (JAR signing) requires that certificate is present in the local keystore. Please read "How to Sign Applets Using RSA" for detailed information.

When you have proper certificate stored, it is necessary to alter build.properties file — set appropriate values for certificate alias and storepass properties:

alias=mykey
storepass=123456

Customization

The customize particular image, property or GUI appearance it is necessary to put altered resource file to proper location under custom directory.

It is not recommended to alter original files just because compare original resource to altered could be a good opportunity.

Assume it is necessary to build custom JAR that:

Use russian user interface lanuage.
Upload images to http://myserver/upload.
Alter "start upload" button image.

So, it is necessary to:

Put russian language messages.properties file to the custom directory.
Create file custom/UploaderConfig.properties and specify there: uploadUrl=http://myserver/upload.
This could be most complicated step here, because actually there are 4 images for "start upload" button: default, hover, pressed and disabled. Original image files located under bin/images directory and have names start_normal.png, start_hover.png, start_pressed.png and start_disabled.png correspondingly. So, it is necessary to create 4 images for mentioned states (they don't have to be same size as original image size) and put them to custom/images using appropriate file names.

NB! It is not eligible to customize JumpLoader free version logo image!

It is possible (at some extent) to change GUI appearance, for example fonts, colors, borders etc. by altering gui*.properties files. Although this feature is not documented, this could be not much complicated.

It is possible to configure applet behaviour without parameters by altering AppletConfig.properties, UploaderConfig.properties and ViewConfig.properties, see Applet configuration section.