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/index.rst | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) (limited to 'docs/tutorials/cmf/index.rst') diff --git a/docs/tutorials/cmf/index.rst b/docs/tutorials/cmf/index.rst index fd393e3b0..b9e837a21 100644 --- a/docs/tutorials/cmf/index.rst +++ b/docs/tutorials/cmf/index.rst @@ -7,12 +7,26 @@ The Zope `Content Management Framework websites. It's reasonably easy to convert a modern Zope/CMF application to :mod:`repoze.bfg`. +The main difference between CMF and :mod:`repoze.bfg` is that +:mod:`repoze.bfg` does not advertise itself as a system into which you +can plug arbitrary "packages" that extend a system-supplied management +user interface. For those sorts of high-extensibility, +highly-regularized-UI systems, CMF is still the better choice. + +:mod:`repoze.bfg` (and other more lightweight systems) are often a +better choice when you're building the a user interface from scratch, +which often happens when the paradigms of the system-provided user +interface don't match the requirements of an application very closely. +Despite the mismatch, a good number of developers tend to use CMF even +when the UI requirements aren't a very good fit, because it happens to +provide other helpful services, such as types and skins; this tutorial +is for those sorts of developers. + Missing: templates.rst forms.rst workflow.rst - actions.rst membership.rst discussions.rst syndication.rst @@ -24,5 +38,6 @@ Missing: content.rst catalog.rst skins.rst + actions.rst -- cgit v1.2.3