@loubabe, please explain why this doesn't violate the no duplicate modules rule by providing an explanation of how this differs from the existing Google Maps modules and pointing to the issues under those modules where you tried to get this functionality incorporated. The current description suggests it very much does violate that rule.

Comments

thebuckst0p’s picture

thebuckst0p commented

What's the status of this module? I have my own lightweight GMap3 implementation for Drupal that I'm going to put on GitHub, but I'd be curious to see yours.
Regarding the issue of duplicating GMap, I for one think a fresh start for GMaps API v3 is better than porting the already-overly-bloated GMap module to the new version. I tried working with GMap.module for months, trying to get it to do things that at the API level are very simple, and finally decided it wasn't worth it. The no-duplicates rule has drawbacks.

levelos’s picture

levelos commented

@thebuckst0p - Mostly still in the planning phases. In my recent geo projects, I first used Mapstraction, took over, and created a new branch of that module. Overall, MXN works great, but I wanted a module that could take advantage of some features unique to gmap3. Been side tracked with a couple open layers projects, but I am planning on returning to this. Some of the features I'm considering:

  • Adding KML and GeoJSON layers
  • Clustering support
  • Static map support
  • Custom styles
  • API based architecture, with sub modules to provide specific features to keep it lightweight.

I'd be happy to collaborate if our visions align.

levelos’s picture

levelos commented
Status: Active » Closed (fixed)

@sreynen while I appreciate the importance of the no duplicate modules rule, I want to create something fundamentally different from the GMap module, which, while excellent for many use cases, falls short for others. It's also making no moves towards moving to v3 of Google Maps, which is the current recommended version to use.

sreynen’s picture

sreynen commented
Title: Duplicate, no? » Document module purpose
Status: Closed (fixed) » Needs work

Please note I opened this as a documentation issue. I didn't say the module is a duplicate; I asked for documentation of why it is not a duplicate. You've hinted at differences here, but haven't really spelled them out, and the project page doesn't provide any indication there even is a difference. It's ultimately your issue queue to manage; I just wanted to make sure you understand the point of the issue before you close it.

Sohodojo Jim’s picture

Sohodojo Jim commented

To Anyone Interested in PHP access to Google Maps JS API v3,

I've been in email communication with both Lev (owner of this module) and Ben (the Buck) and understand their on-going interest in this module's domain. But they are both happily busy on many things in addition to this.

While it may never see the light of day as a Drupal.org contributed module (and may wind up somehow incorporated into whatever this placeholder module becomes), I have scratched this itch a bit for my own needs at www.DropaBalm.com.

My GoogleMapAPIv3 module is available here: www.sohodojo.biz/blogs/jims-tech-blog/googlemapapiv3-module-drupal and may be of use to folks needing or wanting API v3 features now rather than in the future sometime. Note: This is strictly a developer-oriented module which is an API for incorporating Javascript generation of Google maps based on the v3 API. There is no Views, Panels, CCK or any other end-user access or functionality. Basically you simply install the module and use it to create or extend your own modules or themes.

This is essentially a Drupal-friendly wrapper on Brad Wedell's PHP GoogleMapAPI class with Javascript V.3 support. See the article referenced above for any additinal detail.

Hope this might help others' scratch their itches,
--Sohodojo Jim--
AKA DropaBalm Jambo