Hopiu/django-admin2
1
0
Fork 0
mirror of https://github.com/jazzband/django-admin2.git synced 2026-04-23 08:04:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Indexing actions

Browse source
This commit is contained in:
Daniel Greenfeld 2013-07-06 10:03:54 +02:00
parent 0de830abf9
commit 9492c8372a
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/ref/actions.rst
View file

@ -2,6 +2,8 @@
Actions
=======
.. index:: Actions
Actions are defined to work on a single view type. Currently, actions are only implemented against the ``ModelListView``. This view contains the default ``DeleteSelectedAction`` method, which in end functionality mirrors ``django.contrib.admin.delete_selected``.
However, under the hood, django-admin2's actions work very differently. Instead of functions with assigned attributes, they can either be functions or full fledged objects. Which means you can more easily extend them to suit your needs.
@ -39,6 +41,9 @@ The documentation works off a simple set of models, as listed below:
Writing List Actions
-----------------------
.. index::
single: Actions; Writing List Actions
The basic workflow of Django’s admin is, in a nutshell, “select an object, then change it.” This works well for a majority of use cases. However, if you need to make the same change to many objects at once, this workflow can be quite tedious.
In these cases, Django’s admin lets you write and register “actions” – simple functions that get called with a list of objects selected on the change list page.