Closed (fixed)
Project:
Openlayers
Version:
6.x-2.x-dev
Component:
OpenLayers Filters
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
23 Dec 2009 at 17:07 UTC
Updated:
20 Jan 2010 at 22:00 UTC
It seems like usage of OpenLayers filters is very low and the concept is weak; there are a lot of places (like referring to a preset which gets removed or is temporary) where it falls apart. Also, the module is very minimal and could be maintained as an external instead of part of the core OpenLayers module project; we could split it out and look for a maintainer so that the core of OpenLayers can become stable.
Unless there are any serious objections, I think it makes sense to remove filters soon from the 2.x branch.
Comments
Comment #1
zzolo commentedI am not sure how you can tell the usage of it. And I am not sure how the concept is weak (maybe more explanation here).
* It is simple, and my guess is that it is probably not used too often, but I have no evidence of that.
* Is it very hard to just put the default map if something doesnt exist
* It offers the same functionality that GMap does, allowing people to switch to open layers.
* The code is so minimal, I don't see the burden of maintaining the module.
* I think moving it to a separate module is an annoyance for drupal.org and just puts more small modules into the module soup.
* If this is really holding up 2.x becoming stable, I will be happy to upgrade it (the whole 30 minutes it would take).
Unless you can give a better argument here, I don't see any reason to remove it.
Comment #2
tmcw commentedHey,
Sounds good - you want to take charge in porting openlayers_filters to 2.x? I'm going to be working on openlayers_cck whenever I get free moments - these are basically the two submodules that haven't gotten much love and definitely block general consumption of the OpenLayers module.
Comment #3
zzolo commentedOn it.
Comment #4
zzolo commentedUpgraded: http://drupal.org/cvs?commit=310842
I have to fix some other bugs to fully test.