diff options
Diffstat (limited to 'docs/narr/extending.rst')
| -rw-r--r-- | docs/narr/extending.rst | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/docs/narr/extending.rst b/docs/narr/extending.rst index c757dde99..0f9bc433d 100644 --- a/docs/narr/extending.rst +++ b/docs/narr/extending.rst @@ -10,6 +10,9 @@ source code that makes up the application. The behavior of a :mod:`repoze.bfg` application that obeys these constraints can be *overridden* or *extended* without modification. +.. index:: + triple: building; extensible; application + Rules for Building An Extensible Application -------------------------------------------- @@ -41,6 +44,9 @@ declarations made using the ZCML ``<view>`` directive (or the repoze bfg using the :term:`pkg_resources` API such as static files and templates. +.. index:: + pair: ZCML; granularity + ZCML Granularity ~~~~~~~~~~~~~~~~ @@ -70,6 +76,9 @@ disuse *all* your ZCML, choosing instead to copy and paste it into his own package, if necessary. However, doing so is considerate, and allows for the best reusability. +.. index:: + pair: extending existing; application + Extending an Existing Application --------------------------------- @@ -163,6 +172,9 @@ something like this: ``configure.zcml`` file. See :ref:`environment_chapter` for more information about this setting. +.. index:: + pair: overriding; views + .. _overriding_views: Overriding Views @@ -188,6 +200,9 @@ A similar pattern can be used to *extend* the application with existing model type and make sure the URLs it implies are available on some other page rendering. +.. index:: + pair: overriding; routes + .. _overriding_routes: Overriding Routes @@ -202,6 +217,9 @@ declarations when performing an override. Typically, this means and changing them as necessary. Then disinclude any ZCML from the original application which contains the original declarations. +.. index:: + pair: overriding; resources + .. _overriding_resources: Overriding Resources @@ -216,6 +234,9 @@ other resources by using :term:`ZCML` ``<resource>`` declarations. Add such ``<resource>`` declarations to your override package's ``configure.zcml`` to perform overrides. +.. index:: + pair: ZCML; inclusion + Dealing With ZCML Inclusions ---------------------------- |