diff options
| -rw-r--r-- | docs/narr/extending.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/narr/extending.rst b/docs/narr/extending.rst index 321b43064..cbfaeda6a 100644 --- a/docs/narr/extending.rst +++ b/docs/narr/extending.rst @@ -21,13 +21,6 @@ context. Instead, you must use :term:`ZCML` for this purpose. :term:`ZCML` statements that belong to an application can be "overridden" by integrators as necessary, but decorators cannot. -If you've inherited a :mod:`repoze.bfg` application that you'd like to -extend, but which *does* use ``@bfg_view`` decorators, you'll (at -least) need to change the source code of the original application, -moving the view declarations out of the decorators and into -:term:`ZCML`. Once this is done, you should be able to extend or -modify the application like any other. - It's also often helpful for third party application "extenders" (aka "integrators") if you break your ZCML into separate files which do very specific things, and include them in the application's main @@ -39,6 +32,13 @@ registrations he needs. Extending an Existing Application --------------------------------- +If you've inherited a :mod:`repoze.bfg` application that you'd like to +extend which uses ``@bfg_view`` decorators, you'll unfortunately need +to change the source code of the original application, moving the view +declarations out of the decorators and into :term:`ZCML`. Once this +is done, you should be able to extend or modify the application like +any other. + To extend or change the behavior of an existing application, the only hard-and-fast rule is that you need to write some :term:`ZCML`, and perhaps some implementations of the types of things you'd like to |