Package Camelot :: Package camelot :: Package admin |
[frames] | no frames]

# Package admin

source code

@TODO: rewrite docstring

Admin classes, specify how objects should be rendered in the gui

An admin class has class attributes like 'list_display' which contains the columns that should be displayed in a list view (again, see Django)

So this 'list_display' attribute can be overwritten in the Admin class for each model.

But for the gui generation itself, we don't use the class attributes, but we use methods, like 'getColumns', that way, we can make the gui very specific, on the context

Submodules
Camelot.camelot.admin.application_action Camelot.camelot.admin.application_admin Camelot.camelot.admin.entity_admin Camelot.camelot.admin.form_action: Form actions are objects that can be put in the form_actions list of the object admin interfaces. Those actions then appear on the form and can be executed by the end users. The most convenient method to create custom actions is to subclass FormAction and implement a custom run method Camelot.camelot.admin.list_action Camelot.camelot.admin.not_editable_admin: Class decorator to make all fields visualized with the Admin into read-only fields Camelot.camelot.admin.object_admin: Admin class for Plain Old Python Object Camelot.camelot.admin.section Camelot.camelot.admin.validator: Validator classes validate data before their GUI representation is closed by the user. The validator class also takes care of informing the user where the data is invalid. Camelot.camelot.admin.validator.entity_validator Camelot.camelot.admin.validator.object_validator

Variables
| __package__ = `None` hash(x)