diff options
| author | Chris McDonough <chrism@agendaless.com> | 2009-07-03 20:15:37 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@agendaless.com> | 2009-07-03 20:15:37 +0000 |
| commit | ba0ffef0f0c4ca484af0077a2c59cab1935fa0d8 (patch) | |
| tree | c0b1816a2e02d98474f3d54364cca85065316d52 | |
| parent | 41fa3e626af1f4670ccc0091013a13ff84337d4b (diff) | |
| download | pyramid-ba0ffef0f0c4ca484af0077a2c59cab1935fa0d8.tar.gz pyramid-ba0ffef0f0c4ca484af0077a2c59cab1935fa0d8.tar.bz2 pyramid-ba0ffef0f0c4ca484af0077a2c59cab1935fa0d8.zip | |
Wording.
| -rw-r--r-- | docs/narr/extending.rst | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/docs/narr/extending.rst b/docs/narr/extending.rst index 128e75b26..2dfc6a927 100644 --- a/docs/narr/extending.rst +++ b/docs/narr/extending.rst @@ -22,12 +22,15 @@ purpose. :term:`ZCML` statements that belong to an application can be "overridden" by integrators as necessary, but decorators cannot. 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 -``configure.zcml`` via ``<include file="otherfile.zcml"/>`` -statements. This way, an integrator can avoid including any ZCML he +"integrators") if the ZCML that composes the configuration for an +application is broken up into separate files which do very specific +things. These more specific ZCML files can be reintegrated within the +application's main ``configure.zcml`` via ``<include +file="otherfile.zcml"/>`` statements. When ZCML files contain sets of +specific statements, an integrator can avoid including any ZCML he does not want by including only the ZCML files which contain the -registrations he needs. +registrations he needs. He is not forced to "accept everything" or +"use nothing". Extending an Existing Application --------------------------------- |