@Pol and I have been discussing moving the Openlayers widget code into the 3.x branch of the Openlayers module. I started work on it yesterday, and realized that there's a bit more code in it than I realized, and that if we move to OL, we would probably have to introduce a soft dependency of geoPHP to Openlayers (only a soft dependency because it would only be present in the geofield-related code).

In an effort to prevent weird dependency issues, I suggest that we create a new geofield/openlayers integration module to hold the widget code. I don't have a strong opinion of where it should live yet, so opening this up as a bikeshed issue. The obvious options seem to be either a submodule in geofield, submodule in openlayers, or a standalone project. A standalone module would be nice if somebody wants to champion it, otherwise it'll probably get more attention as a submodule.

For Geofield users, this will likely mean that once you update to 2.x, you'll need to enable this new module as a part of an upgrade. Once we get the details down, I'll make sure there's a decent upgrade path.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Pol’s picture

I'm ok with this approach, and create a submodule.

Brandonian’s picture

Status: Active » Needs review
FileSize
28.97 KB

Attached is a patch that completely removes Openlayers integration from the 7.x-2.x branch. Once our companion issue (#1957630: Transfer Geofield integration code into Openlayers submodule) is committed, a verison of this patch will also be committed. No upgrade path yet.

Pol’s picture

Good stuff, can't wait for the next :-)