Syntax definition for the CacheMaps Application eXchange files (Cax-files).

Doc version 2

For Cax version 1.1

These Cax-files define how other applications can be started from within CacheMaps. Main purpose is to pass waypoint information to the applications, but that’s not a must. It is possible to start an application without any parameters.

Here’s the syntax.

It’s a little like XML, though its not XML.

Every item in the list starts with a starttag (e.g. <version>) and ends with an endtag with the same name, but with an extra slash (e.g. </version>).

The first four items are default:

<desc>CacheMaps Application definition</desc>

<version>1.1</version>

<author>Bert 'BigBird' Veldman</author>

<email>cachemaps@bigfoot.com</email>

Then the following are (with the values on the three dots):

• Application name as will show in CacheMaps

<appname>...</appname>

• Comment. Will popup when you select this application in the setup-screen. This can be more then one line.

<cmt>...

</cmt>

• Logofile. This logo will show on the button for this application. If no logofile is given or logofile is not found a blue button will be presented. The file given can include a path, fixed or relative to the cax-file path.

<logo>...</logo>

• Application information. Composing the actual application command. Within this application definition, a couple of parameters can be given.

<app>

<app:filename>...</app:filename>

<app:textparam>...</app:textparam>

<app:inputparam>

<app:inputtype>...</app:inputtype>

<app:inputfile>...</app:inputfile>

</app:inputparam>

<app:textparam>...</app:textparam>

</app>

• App:Filename. The file, including path, for the application’s command. The path can be fixed or relative to the CacheMaps path.

When you leave the filename empty, no external application will be called. The inputfiles that you define will however be generated. See Backup.cax for an example of the use.

• App:TextParameter. This text parameter will be added literally.
• App:InputParameter. The parameter defining the waypoint file to input to the application. Consists of two possible entries. Each of these entries can be repeated within the InputParameter block:
• App:InputType. This defines the type of the waypoint file and is used to generate the correct type for the application. This conversion is done using GPSBabel. GPSBabel must therefore be installed. Must contain a reserved value. Reserved values are:

· all values that GPSBabel accepts,

· “geo” or “loc” for geocaching .loc-file,

· “ozi” for OziExplorer wpt-file,

· “ov2” for TomTom POI files

· “gpx” or empty.
The empty InputType assumes that you need a geocaching Gpx file, containing all information of the cache, including the last 5 logs. This can only be generated when you imported the caches using a Gpx-file. This is a different gpx file than the one that will be generated by using “gpx” as InputType.

• App: InputFile. The file, including path, to be inputted to the application. The path can be fixed or relative to the CacheMaps path. If the path contains spaces, the path has to be enclosed by double quotes (“path bla bla”). Mind that not all applications accept these double quotes and thus do not accept path’s with spaces in it!

Example of a valid cax-file:

<desc>CacheMaps Application definition</desc>

<version>1.0</version>

<author>Bert 'BigBird' Veldman</author>

<email>cachemaps@bigfoot.com</email>

<appname>GarTrax</appname>

<cmt>GarTrax parameters will be loaded...

http://www.p-terminator.nl/geocaching

</cmt>

<logo>GarTrax.gif</logo>

<app>

<app:filename>d:\bert\geocache\GarTrax\GarTrax.exe</app:filename>

<app:textparam></app:textparam>

<app:inputparam>

<app:inputtype>geo</app:inputtype>

<app:inputfile>d:\bert\geocache\GarTrax\CMSelection.loc</app:inputfile>

</app:inputparam>

<app:textparam></app:textparam>

</app>

This will generate the following commandline:

d:\bert\geocache\GarTrax\GarTrax.exe “d:\bert\geocache\GarTrax\CMSelection.loc”