From 84e1a85ce732ba870f9b984b8deaf37c34d4d238 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 21 Sep 2008 20:32:10 +0000 Subject: Add actions chapter. --- docs/tutorials/cmf/actions.rst | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/tutorials/cmf/actions.rst (limited to 'docs/tutorials/cmf/actions.rst') diff --git a/docs/tutorials/cmf/actions.rst b/docs/tutorials/cmf/actions.rst new file mode 100644 index 000000000..7e66f3236 --- /dev/null +++ b/docs/tutorials/cmf/actions.rst @@ -0,0 +1,25 @@ +.. _actions_chapter: + +======= +Actions +======= + +In CMF, the "actions tool" along with "action providers" create an +extensible mechanism to show links in the CMF management UI that +invoke a particular behavior or which show a particular template. + +:mod:`repoze.bfg` itself has no such concept, and no package provides +a direct replacement. Actions are such a generic concept that it's +simple to reimplement action-like navigation in a different way within +any given application. For example, a module-scope global dictionary +which has keys that are action names, and values which are tuples of +(permission, link). Take that concept and expand on it, and you'll +have some passable actions tool replacement within a single application. + +The `repoze.bfg.viewgroup +` package provides +some functionality for creating "view groups". Each view in a +viewgroup can provide some snippet of HTML (e.g. a single "tab"), and +views (tabs) which cannot be displayed to the user due to the user's +lack of permissions will be omitted from the group. + -- cgit v1.2.3