Hi zzolo - would you mind giving some context/background on this. Is it completely separate from OpenLayers / other efforts? Are you starting with D7 or on D6 (i guess D6 since you mention Ctools?)

Edited as comment #9: Added documentation page at https://drupal.org/node/2072765 it has an overview of how Mapping works, what it offers, and differences from other modules.

Comments

zzolo’s picture

zzolo commented
Title: Context Background » Context Background and Overview

Hi Ronald. That was quick :)

It seems like its hard for me to describe this so people get it. But here is my initial thread to see what people thought about my idea:
http://groups.drupal.org/node/91114

It is Drupal 7. There is work being done on porting CTools, and as my goal is to only really use the plugin architecture, it should not change much (especially since it is just a port).
http://github.com/sdboyer/ctools

Overall, the idea is to abstract out the CTools plugin definitions, the UI framework, and specific integration points, like possibly Views, so that all mapping modules, like OpenLayers, and the CloudMade and Polymaps modules I have started can reuse a lot of code.

The idea came about because as I was working on the CloudMade module and thinking about the Polymaps module, it made sense to reuse a lot of code, and the parts for building a map are pretty basic and shared amongst the libraries. But it is important to point out that this is not a Mapstraction sort of thing, its about building a framework/architecture for mapping modules to build from.

I don't think OpenLayers will be affected for some time, but hopefully it would switch to this, as it is very much based off those ideas.

ronald_istos’s picture

ronald_istos commented

thanks for the update - caught up on things now after reading comments in group as well. fwiw think this is great and hope to be able to help as things develop. will be checking out what you checked in :-) as soon as I get a chance.

phayes’s picture

phayes commented

A++! This is a great idea. How usable is it at the moment?

I'm thinking of building a basic google-earth api and was wondering if this is in a state that is workable?

zzolo’s picture

zzolo commented

Thanks, @phayes. I think most of the storage API parts are there. The (very little) JS parts are not quite there; this is meant to be just a little bit to bring together the parts and kick off the library. There is a very basic Google v3 example in there.

There is no UI yet.

I would suggest giving it a go or at least checking out the code. I can give you commit access if you want, and we can talk more in person or IRC if you want to know more.

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented

hey zzolo, interesting!

would, and if so how would this support drupal wax integration? http://mapbox.com/wax/

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
commented

i just worked a bit on the views integration for the leaflet module #1338326: Added support for views and some configuration options

maybe it would be a good idea to merge openlayers, gmap, leaflet, *mapmodule's views integration into this mapping api?

zzolo’s picture

zzolo commented

Hey @dasjo. That's the idea. Though I very much want to move to GeoJSON based Views integration, probably using the http://drupal.org/project/views_geojson module.

mac_weber’s picture

mac_weber commented
Status: Active » Fixed

Added first documentation page: https://drupal.org/node/2072765

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Answered with documentation page.