geonode.base
Subpackages
Submodules
- geonode.base.admin
- geonode.base.auth
- geonode.base.bbox_utils
- geonode.base.enumerations
- geonode.base.fields
- geonode.base.forms
- geonode.base.middleware
- geonode.base.models
- geonode.base.populate_test_data
- geonode.base.tests
- geonode.base.translation
- geonode.base.urls
- geonode.base.utils
- geonode.base.views
- geonode.base.widgets
Attributes
Classes
Base class for AppConfig notifications setup |
|
Base class for AppConfig notifications setup |
Functions
|
Decorator on views, which will register url event |
|
Wrapper function to be used inside views to collect event and resource |
|
Process request to geoserver proxy. Extract layer and ows type |
Package Contents
- class geonode.base.NotificationsAppConfigBase[source]
Bases:
django.apps.AppConfigBase class for AppConfig notifications setup
You should subclass it and provide list of notifications in NOTIFICATIONS attribute to automatically register to post_migrate signal.
- NOTIFICATIONS
- class geonode.base.BaseAppConfig[source]
Bases:
geonode.notifications_helper.NotificationsAppConfigBaseBase class for AppConfig notifications setup
You should subclass it and provide list of notifications in NOTIFICATIONS attribute to automatically register to post_migrate signal.
- geonode.base.register_url_event(event_type=None)[source]
Decorator on views, which will register url event
usage:
>>> register_url_event()(TemplateView.view_as_view())
- geonode.base.register_event(request, event_type, resource)[source]
Wrapper function to be used inside views to collect event and resource
- Parameters:
request – Request object
event_type – name of event type
resource – string (then resource type will be url) or Resource instance
>>> from geonode.base import register_event >>> def view(request): register_event(request, 'view', layer)