Deploy TouchRAM as packaged application for Mac OS and Windows

[Matthias Schoettle]

TouchRAM should be deployed as a packaged application, mostly for Mac OS and Windows.

For Mac OS, this would allow to include the Java 1.6 JRE so even if a user has Java 7 installed, it does not interfere. Furthermore, this will make it easier to provide the app icons. There exists an ANT task (called appbundler) that allows to do this.

For Windows, it would just be convenient, although the provided .bat file is sufficient, but not as nice of course.

[Matthias Schoettle]

For Java 7, Oracle provides an ANT task appbundler: http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/packagingAppsForMac.html

Due to the inconsistencies with JOGL we still use Java 1.6, which (I believe) means we can't use appbundler. There is, however, another task called JarBundler (http://informagen.com/JarBundler/), which should probably be working fine. This post could also be interesting: http://stackoverflow.com/a/10246251

[Céline Bensoussan]

Resolved issue #183: Placed bundler in build folder (same as jar)

→ <<cset 5ee538123ee7>>

[Matthias Schoettle]

There are two problems:

• When packaging the app I get the following error:

BUILD FAILED
.../git/touchram/ca.mcgill.sel.ram.gui/build.xml:211: java.lang.UnsupportedClassVersionError: net/sourceforge/jarbundler/JarBundler : Unsupported major.minor version 52.0

I tried JarBundler 2.2.0 and that one worked, not sure if 2.3.0 or so would work.

• The default models directory is TouchCORE.app/Contents/Resources/Java/, we should either use the actual models directory located outside of the app, or put the model libraries into that folder.

[Matthias Schoettle]

Also, the Settings.txt should be inside the bundle (and the README should mention this fact) :)

[Céline Bensoussan]

References issue #183: Models and Settings.txt placed in Java file, README updated

→ <<cset 97b83e1b28f9>>

[Matthias Schoettle]

The last commit resolved this issue again.

However, we need a proper way of dealing with models at different locations. We don't want the user to save own models inside the app.

Several things could be done:

• We could only show the models folder when reusing a concern
• The file browser could have shortcuts for user models and reusable concern library (instead of just models)
• Maybe the user should be able to somewhere specify where the user models directory is located at