-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the geonode
project type maintained?
#9
Comments
Hi @cwygoda, A preliminary note, this repository is still in development and unstable. We are working to adapt mapstore project to this kind of structure but the development is not complete yet.
The If you are using the stable branch of GeoNode 3.2.x the official suggested methods to customize the client are listed in the README. There are two level of customization:
While if you are working on GeoNode master we are exploring the possibility to use the mapstore extension as mechanism to add new plugins to the different MapStore container. The MapStoreExtension should allow to create a custom plugins and configure them with a json file. This should be the expected structure in a geonode-project
where:
{% extends 'geonode-mapstore-client/_geonode_config.html' %}
{% block override_local_config %}
<script>
window.__GEONODE_CONFIG__.overrideLocalConfig = function(localConfig, _) {
localConfig.plugins.map_embed.push({ name: 'SampleExtension' });
return localConfig;
};
</script>
{% endblock %} Now the /map/{pk}/emebed path should show the new plugin
We cannot remove all the code right now because we still need it in a specific context but maybe we could stop the creation of geonode project via script with a message. It could be helpfull if you could test the Extension approach described above. I just opened an issue on the geonode-mapstore-client repo to keep track of feedback and comments. GeoNode/geonode-mapstore-client#225 Thanks for your feedback! |
Hi,
trying to set up a customized mapstore for Geonode I thought I might be able to keep it DRY by using this with the
geonode
type. The following tells me I might be chasing a dead end:master
as a valid dependency version in package.json!)standard
is listed in the READMEIf
geonode
project type is not maintained, please remove the dead code. And would be wonderful to document how to properly customize a current mapstore with current geonode. Happy to help!Cheers,
Christian
The text was updated successfully, but these errors were encountered: