Stop confusing the marker system by blindly wrapping marker.text in a div, even
if it didn't exist.

Add a way to bind controls that we aren't able to set the id/classes on from the Drupal side.

This lets us work around the fact that gmap_widget_setup() completely fails to work on CCK fields.

Example:
<code>
  $remap = array(
    'edit-field-latitude-0-value' => array('classes' => array('gmap-locpick_latitude'), 'id' => 'gmap-loc0-locpick_latitude0'),
    'edit-field-longitude-0-value' => array('classes' => array('gmap-locpick_longitude'), 'id' => 'gmap-loc0-locpick_longitude0'),
    'edit-field-address-0-value' => array('classes' => array('gmap-locpick_address'), 'id' => 'gmap-loc0-locpick_address0'),
  );
  drupal_add_js(array('gmap_remap_widgets' => $remap), 'setting');

  /* ... stuff copied from gmap_set_location(), etc... */
</code>

HOPEFULLY it will work okay.
The reason I was reluctant to change this is the interactions between drupal_add_js()
and hook_filter(), described at
http://mostrey.be/hookfilter-versus-drupaladdjs

If anyone has troubles with macros after this change, I will have to revisit gmap's filter
stuff.

Also, fix a warning caused by neglecting to give the row plugin a chance to query.
Additionally, ensure that views knows we are capable of doing grouping.
The fix is based on the changes presented in #619884 for views.

Usability: Don't show a JS error when attempting to display a map before the API key has been configured.

This should help when visiting the settings page for the first time, etc. The immediate JS error isn't very nice.

GPolygon.fromEncoded() and GPolyline.fromEncoded() don't take style arguments the same way as the regular constructors--styles have to be attributes of the encoded polyline/polygon object, rather than being arguments to the constructor

This fixes the annoying jerky / flashing marker when using locpick, and makes the whole thing feel a lot smoother.

Fix issue when bootstrapping multiple maps, jquery's each was calling the callback with a parameter and it was attempting to use it as a settings array.

Fixed it by isolating the callback.

Rename permissions:
"show node map" -> "view node map"
"show user map" -> "view user map"
"user locations" -> "view user location details"

Remove 'set user location' permission, it's a leftover from the days that GMap used to be responsible for user locations.

Hopefully fix #371134: warning: Invalid argument supplied for foreach()...gmap_plugin_style_gmap.inc on line 172.

#397986, reported by VeryMisunderstood: Fixing php notice / serious performance issue in marker titles.

Fix #155104 by Scott Falconer: Add "Zoom to cluster area" support.

Allow falling back to the default Clusterer marker if desired.

Allow entering larger numbers in some marker manager settings.

Allow choosing between the original and the new "zoom to marker area" behavior on Clusterer.

http://groups.google.com/group/Google-Maps-API/msg/33df59945c139afe?dmode=source

This file needs some serious work still, it will definately need the most work before dynamic bootstrapping works.

(Header changes only.)

== -> === changes.
Remove unused variable.
Dot notation.

(Header changes only.)

== -> === changes.
Remove unused variable.

== -> === changes.

Remove unused variables.