-
Notifications
You must be signed in to change notification settings - Fork 1.1k
GNIP 40 Use Standard GeoExplorer (vs custom geonode client)
Currently GeoNode comes with GeoNode-client, which is an adapted version of a few years old version of GeoExplorer. This makes it hard to take in the new features that GeoExplorer has gotten in these past years. So the purpose of this GNIP is to use a standard version of GeoExplorer, and only make a small amount of necessary changes in a separate class GeoNode.Composer. As many changes as possible should go into the underlying libraries / projects. Ultimately we want to take in a zip file with the static files of GeoExplorer and build upon that in GeoNode. It would be good to have an integration / staging server where we can always test against the latest GeoExplorer.
Bart van den Eijnden
2.0
Complete in master. Thanks @bartvde for the integration work at the Utrecht Sprint and @ingenieroariel for the packaging of django-geoexplorer. @mweisman, looking forward to the next suite release.
Reduce the amount of custom code in GeoNode, by building upon a general component such as GeoExplorer. Make sure that GeoExplorer has as many extension points as needed by GeoNode.
Remove geonode-client in GeoNode. Take in the static files of GeoExplorer, and build upon that code by implementing a GeoNode.Composer class that inherits from GeoExplorer.Composer.
Currently the pull request includes the static resources from GeoExplorer. We need to setup the build in such a way that these files are removed and that we take in static zip file (or war file and extract it) from GeoExplorer.
Integration tests should continue to pass. User testing of the map composer and other map related pages.
Do nothing.
Complete in Master. Tested on http://beta.dev.geonode.org/
+1 Jeffrey Johnson