Added a note about how to link directly to Google Maps if I should want
to do that.
This is the first change in mobile.js in an effort to use Google Maps
directly.  I can open the map page.  What I need to do now is to get
latitude and longitude to Google.  I'm going to place them into globals.
Added getters & setters for longitude and latitude and everything works.
Now the call to Google maps passes a latitude and longitude.  what I
need is to get the latitude and longitude from elsewhere.
I've commented the call to google maps so I can trace the events that
lead up to that statement.
The call to navigator.getLocation fetches latitude and longitude in
locSuccess.  Now to get them into globals.
Can set latitude in globals.  I had neglected to make latitude and
longitude variables in globals after I regressed to an earlier commit.
Now that I've done that I may have more progress.
Can set longitude in locSuccess.
Moved the call to google Maps to locSuccess.  I shouldn't even need to
put latitude and longitude into globals any more.
I can pass one set of coordinates to Google Maps.  Now I need to get the
lat/long of the trailId to get a routing.
I have both my location lat/long and destination lat/long in locSuccess.
Now to pass them to Google Maps.
Now I can get voice navigation to a destination.  I should test this by
going on a driving test.  After that I can removed ***lots*** of the
code that is in here.
I don't need my current location because Google Maps navigator will get
that.  Thus, I don't need to call
navigator.geolocation.GetCurrentLocation().  Thus I can invoke Google
Maps from the event handler for the Maps button, so I've moved the call
to Google Maps from locSuccess() to googleMaps.live.click.  I can remove
lots and lots of code at this point.
Added an alert to tell how to return to the trail instructions after
using Google Maps navigation.