#238 Autopopulate paths

[Christopher Smart]

To help lower the bar for entry, it would be great if Xena could auto populate the locations of external utils like readpst, tesseract and flac. We already ship them with the binary, so we know the location. It might also work relative to the location of xena.jar, which makes it easier in case someone does a custom location install.

We don't ship OOo, but perhaps we can still look for it and populate it if we find it, else prompt the user on first run?

I'd also like to pre-set the xena output and log location if possible (if it doesn't exist, create it).

[Justin Waddell]

This has been implemented. The file etc/default-preferences.properties contains the default preferences for xena and its plugins. This file is loaded on startup, and if any of the preferences in the file have not been previously stored, they will be used.
Might need more discussion if anything further is required code-wise, or if we'll just handle it during the build.

[Justin Waddell]

Implementation was in Xena 4.3.5, testing branch.

[Michael Carden]

Please test and close if okay.

[Allan Cunliffe]

Tested in Texting Branch of Xena 5.0.1 and Xena installer in Ubuntu Linux 9.10 and Windows 7 (64-bit).

Justin has created a *default-preferences.properties* file which provides this capability.

Current behaviour is as follows:

* If Xena Preferences and Xena Plugin Preferences have previously been set, Xena reads these values.
* If Xena Preferences have not been previously set, they are set automatically (Xena Destination Directory and Xena Log), according to the *default-preferences.properties* file (see below for the contents of this file).
* If Xena Plugin Preferences have not been previously set, they are not automatically populated. Location values depend on the installation location.

More work would be required to enable auto-population of Xena Plugin Preferences. I'll keep this open in case this can be done.

The *default-preferences.properties* file is as follows:

# These properties will only be used if there is no existing value.

# Separate property path and property name with //.
# // cannot occur in the path for Java Preferences so is a good separator.

# As we are dealing with paths and paths are totally different on different systems..
# thank you Windows.. we have some variables (tags/tokens) we can use to make these
# properties non-system specific.
# {homedir} - is the System.getProperty("user.dir")
# e.g. /home/<user> on linux or C:\documents... on Windows.
# {sep} - is the System.getProperty("file.seperator")
# e.g. '/' on linux and '\' on windows.

# Xena properties
au/gov/naa/digipres/xena/litegui//dir/xenadest={homedir}{sep}Xena{sep}Destination
au/gov/naa/digipres/xena/litegui//dir/xenalog={homedir}{sep}Xena{sep}Logs{sep}xena-%g.log

# Plugin properties
au/gov/naa/digipres/xena/kernel/properties//Image/Tesseract\ Executable\ Location=
au/gov/naa/digipres/xena/kernel/properties//Office/Office\ Location=
au/gov/naa/digipres/xena/kernel/properties//Audio/Flac\ Executable\ Location=
au/gov/naa/digipres/xena/kernel/properties//Email/Readpst\ Executable\ Location=