Prune is available to download either as compiled jar (just the runnable code) or as source code (the entire java source) if you want to compile it yourself. The latest released version is version 11.1, from August 2010.
Runnable code (636 kb) |
Source code (284 kb) |
Update: For those who need or want a version of Prune without the exif reading libraries included, there is now such a version available on request. However it then does require a separate version of libmetadata-extractor both to compile Prune and to run it. (This was done for Debian so that they can reuse the libmetadata-extractor from the existing package.)
For special linux packages for OpenSuse, Mandriva, Debian, Ubuntu and Arch, see the details below.
There is no installation. Simply download the jar file to your machine.
If you have associated jar files with java already, then you can just double-click on the jar file to run it. If not, you can right-click on the jar file and select "open with..." and then "Java platform" (or something similar).
Alternatively you can use the command line to launch the jar, like this:
java -jar prune_11.1.jar
But remember you must include the whole path to the Prune jar file. To make it easier, you can create a shortcut on your desktop or menu to call the above command. Or you can set up a bash script to call it (see below), so you just have to type "prune" to run it.
Prune should automatically select the language based on your system settings - but remember that only the languages CZ, EN, DE, DE_ch, ES, FR, IT, JA, NL, PL, PT and ZH are currently supported. Also RO, ID and AF are partially supported. If you want to override these settings and select the language yourself, you can do this with an extra parameter:
java -jar prune_11.1.jar --lang=DE
If you have an RPM-based linux system, like Opensuse or Fedora or Mandriva, you may want to have a look at the OpenSuse build service - they have kindly prepared an rpm (called prune-10-1.2.noarch.rpm) which is installable like any other package. This package saves the prune jar file in /opt/share/prune/ so it's available for all users, and even provides a menu entry to launch Prune wth a click. Or from the command line just run prune.
In theory this rpm should make it easier for the linux distributions to include it in their own repositories, making it much simpler to find and install, but I haven't heard of any such plans yet. The latest news is that prune is on its way into the "Contrib" repository of OpenSuse, but it's not clear how long this will take. However, the rpm from the build service installs fine on OpenSuse 11.2 using the OpenJDK.
There is now a package of Prune for Debian linux. Version 10 is now available in Squeeze (testing) and version 11 in Unstable. The package is called gpsprune. This can be easily installed either in Debian or in Ubuntu (tested with Lucid Lynx 10.04). Just install the dependencies first using the universe repository (or the testing repository for Debian) - you'll need a java runtime such as sun-java6-jre or OpenJDK, and libmetadata-extractor-java. You can also get libjava3d-java if you want. Then download the gpsprune deb file and install it either with gdebi or dpkg. Now that it's in testing it should be even easier to install just using aptitude.
Once it's installed, you get a menu entry for "gpsprune" in the "Science" menu, or you can launch it from a console with gpsprune.
This also works if you're running Elive, just download the above packages from Debian's testing repository and install them with dpkg.
For the forthcoming "Maverick" release of Ubuntu, there is also a gpsprune package, currently taken from Debian's version 10 package but hopefully soon to be updated to version 11.
There is apparently also a package of Prune for Arch linux, but I haven't had chance to test it yet. It seems to be just a wrapper around the binary jar file, including a desktop file. If you're interested, see the Arch User Repository.
Also for BSD users there is a package of Prune at freshports.org, currently at version 10. I haven't had chance to test this one either.
The only changes since version 11 are minor bugfixes:
The following features are among the changes added since version 10:
If you're on a linux or mac system, you can make it easier to run Prune by setting up a bash script to launch it. This is what the RPM version does (see above), by saving the prune jar in /opt/share/prune/prune_11.1.jar and saving a launch script in /usr/bin/prune similar to the following:
#! /bin/sh java -jar /opt/share/prune/prune_11.1.jar "$@"
Then, when any user wants to run Prune, they can just type prune from a console, or to set parameters, they can just type for example prune --lang=de to get Prune in German.
The RPM version above also adds a menu entry with a little icon, which makes it even easier to launch, but of course doesn't allow you to specify additional start options.
Volunteers provide most of the language translations for Prune, and every time a version of Prune is released, the latest version of the translations is taken and included in the jar file. If the translations are improved after Prune has been released, these can be made available in a separate text file, and then specified in the command used to launch Prune.
There are no language packs for Prune version 11.1 yet, as all the translations are already inside the jars.
See the dependencies page for how to get the additional bits of software to extend Prune's functionality. These include the Java runtime, the Java3d libraries for real-time 3d display, Povray for rendering of 3d images, Exiftool for saving coordinates to exif information of jpegs, GPSBabel for communicating with GPS receivers, and gnuplot for drawing charts of altitudes, speeds etc.
See the history page for details of previous versions of Prune and the history of development, or the old screenshots for how Prune used to look.
There are several additional features planned which have not yet been implemented. The current status of development is shown in the development page and user suggestions are listed in the wishlist.
Of course any suggestions or contributions, especially multi-lingual translation expertise, would be very gratefully received! Please see the translation wiki for details on how to help with this.