Issue #1459606 by haiiro.shimeji, tmsimont, rjay: Backport from D7 to use Google maps API V3 for D6 6.x-2.x-dev.

Fix #703480, patch by dnotes: Brown paper bag fix in gmap_module_invoke: Don't nuke the return value repeatedly when cycling through hook implementers.
Fixes an issue where all the behavior flags disappear.

Move gmap_views_gmap preprocess function to gmap.module to work around caching quirks seen in the wild.

#315236 by Bartezz, Fabianx, NigelCunningham, jcmarco et al. - gmap views that use ajax break when exposed filters are used.

Fix #582934, patch by me, rerolled by pivica and hutch: PHP 5.3 compatibility for hook_gmap(). (Manual backport)

* Add Google Bar to search on map
* Add option for a marker tooltip field on gmap views
* Add option to highlight markers on mouse rollover event
* Add option to center Gmap on marker of node passed as argument in view
* Add option to highlight markers of node passed as argument in view

Fix #676108. Original patch by greenSkin, heavily modified by me to hopefully maximize compatibility.

In theory, this should work in both keys_api and keys now.
(cherry picked from commit 2831abcbe55a2b60dbeaeb52e895d0877ef20615)

(cherry picked from commit 751d05ac637eba7c25155e5e14ed6fd26418314e)

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

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.

#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.

add a class around map bubble contents. you can now set width and height on .gmap-popup in your css and map bubbles will grow to fit it.

#350408 by pillarsdotnet: Selecting "Regenerate marker cache" does not reliably clear and rebuild the marker cache.
Changes:
gmap_regenerate_markers()

    * Pass TRUE to the gmap_get_icondata() function
    * Pass TRUE to the gmap_set_marker_titles() function

gmap_set_marker_titles()

    * Simplify and correct the caching logic

gmap_flush_caches()

    * Add an implementation of hook_flush_caches to ensure that clicking on the "Clear cached data" button from the /admin/settings/performance page also rebuilds the marker cache.

Add shape clickability.

#330343, reported by fabio84 and also by epimeth in irc: Make script url valid again, I forgot that url() returns raw ampersands.

Let people pass map arrays to theme('gmap') without wrapping them in array('#settings' => ...). In theory.

* Remove references to mousewheel.js, clean up variable.
* Add support for Continuous Zoom, enabled by default.
* Add behavior flag for disabling Continuous Zoom.
* Remove workaround from may 2007 (rev 1.1.2.15) that was causing zooming problems.

* Add style keyword to the macro layer.
* Add code to merge styles in properly.
* Allow using references to styles in lines / polys.

Add 'hl' parameter to allow the map to translate itself. (Part of #314777.)

Remove the markerdata hack.
Add a marker file generator and fix markers once and for all.
Add a button to the settings page to regenerate the marker cache.