-
Notifications
You must be signed in to change notification settings - Fork 60
Planning_12_April_2016
Divorce configuration from the code more cleanly. Allow the demo and the code to be installed with less dependence.
In GeoMoose versions before 3.0, there were many files in many locations that defined templates for how to display data. The creates a large set of files across many directories in seemingly different languages. This could be simplified by moving template functionality to XML/Javascript and inlining the templates with map-source and service definitions.
Move away from the custom PHP scripts using Mapscript to parse and return custom HTML/XML. Instead use WMS and WFS to their fuller potential.
A. Update back end libraries to branches which are under active development (e.g. OpenLayers 3). B. GeoMoose's code code should be installable using bower and/or npm.
Any library chosen for 3.0 must support mobile browsers.