gps.receiver.url: the connection string for your GPS device. The MIDlet doesn't attempt Bluetooth service-discovery because my device isn't discoverable. (Also in principle there is no reason which this has to be a Bluetooth URL: if your device is accessible over TCP/IP you could use a
gps.channels: the number of satellite signals your GPS device can receive simultaneously.
gps.midlet.maps: the directory on your MIDP device in which to store downloaded maps. (This implies you have JSR75, the file-connection API; if you do not, you must modify the MIDlet to use the
RmsMapCacheclass instead of
gps.coordinate.mapper: the class which maps coordinates into, er, maps. (Currently only Googler2 makes sense, the original mapper no longer applying. Consider writing one for another map provider, or even Google's satellite images.)
build.xml, assumes the existence of a package repository in which the above packages reside. The root of this repository is determined from the environment variable,
PACKAGES. (It also contains targets for building various Personal Profile programs, which use the code here but are not released under an Open Source license. More information about these programs may be found here.)
org.syzygy.gpspackage contains beans and interfaces common to both platforms while the
org.syzygy.gps.midppackage contains MIDlet-specific code to display the information on a Limited, Connected Device's screen.
All code is distributed under the terms of the GNU GPL.
FileMapCache: if your target device has the file-connection API you are in luck, this is the default cache used in the MIDlet.
RmsMapCache: this cache uses the basic Record Management System of CLDC. To use this (which you should only do as a last resort) you must edit
WhereMIDlet.javaand instantiate it instead of
Unfortunately the Gudermannian requires transcendental functions which
aren't available in CLDC's
java.lang.Math so power-series
approximations are provided, which I am amazed I remembered from College.