google-code-export / marinemap

Automatically exported from code.google.com/p/marinemap
Other
1 stars 2 forks source link

Remove MPA and Array from lingcod #473

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Remove the lingcod.mpa and lingcod.array modules. This will require refactoring 
the many apps which relied on that convienience:

kmlapp (see other ticket)
staticmap (lots of assumptions about the mpa-array relationship that may 
require major overhaul)
common
sharing (?)

In addition, we should probably implement a suitable replacement as 
example_project.mlpa.mpa and example_project.mlpa.array

Original issue reported on code.google.com by perrygeo...@gmail.com on 27 Jan 2011 at 5:25

GoogleCodeExporter commented 9 years ago
lingcod.mpa and lingcod.array have been removed. All of the critical code 
removes references to get_mpa_class and the like. 

Still need to do:
kmlapp, staticmap and heatmap all need to be ported over to a CMS approach.
implement mpa/array in example project (would make a great test/canonical 
example)

Original comment by perrygeo...@gmail.com on 3 Feb 2011 at 3:30

GoogleCodeExporter commented 9 years ago
kmlapp is MPA/Array free
mpas and arrays are implemented in the test project

still need to fix up staticmap and heatmap

Original comment by perrygeo...@gmail.com on 11 Feb 2011 at 12:19

GoogleCodeExporter commented 9 years ago
staticmap is a ticket in and of itself - fairly major overhaul
heatmap is not critical so we can put off until 2.1 ? Assuming yes, I'm closing 
out this ticket and starting two new ones.

Original comment by perrygeo...@gmail.com on 14 Feb 2011 at 8:18

GoogleCodeExporter commented 9 years ago
Lack of staticmap support would need to be dealt with prior to upgrading OMM to 
3.0.

Original comment by underbluewaters on 14 Feb 2011 at 8:48