From 4e46a6f458fa31ca5f252dd31b1229fcb775299d Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 21 Dec 2008 03:33:08 +0000 Subject: Backwards Incompatibilities (Major) - Rather than prepare the "stock" implementations of the ZCML directives from the ``zope.configuration`` package for use under :mod:`repoze.bfg`, :mod:`repoze.bfg` now makes available the implementations of directives from the ``repoze.zcml`` package (see http://static.repoze.org/zcmldocs). As a result, the :mod:`repoze.bfg` package now depends on the ``repoze.zcml`` package, and no longer depends directly on the ``zope.component``, ``zope.configuration``, ``zope.interface``, or ``zope.proxy`` packages. The primary reason for this change is to enable us to eventually reduce the number of inappropriate :mod:`repoze.bfg` Zope package dependencies, as well as to shed features of dependent package directives that don't make sense for :mod:`repoze.bfg`. Note that currently the set of requirements necessary to use bfg has not changed. This is due to inappropriate Zope package requirements in ``chameleon.zpt``, which will hopefully be remedied soon. - BFG applications written prior to this release which expect the "stock" ``zope.component`` ZCML directive implementations (e.g. ``adapter``, ``subscriber``, or ``utility``) to function now must either 1) include the ``meta.zcml`` file from ``zope.component`` manually (e.g. ````) and include the ``zope.security`` package as an ``install_requires`` dependency or 2) change the ZCML in their applications to use the declarations from `repoze.zcml `_ instead of the stock declarations. ``repoze.zcml`` only makes available the ``adapter``, ``subscriber`` and ``utility`` directives. - The ``http://namespaces.repoze.org/bfg`` XML namespace is now the default XML namespace in ZCML for paster-generated applications. - The copies of BFG's ``meta.zcml`` and ``configure.zcml`` were removed from the root of the ``repoze.bfg`` package. In 0.3.6, a new package named ``repoze.bfg.includes`` was added, which contains the "correct" copies of these ZCML files; the ones that were removed were for backwards compatibility purposes. Other - The minimum requirement for ``chameleon.core`` is now 1.0b13. The minimum requirement for ``chameleon.zpt`` is now 1.0b7. The minimum requirement for ``chameleon.genshi`` is now 1.0b2. --- docs/glossary.rst | 4 +-- docs/narr/MyProject/myproject/configure.zcml | 6 ++--- docs/narr/events.rst | 4 +-- docs/narr/security.rst | 2 +- docs/narr/unittesting.rst | 6 ++--- docs/narr/urldispatch.rst | 4 +-- docs/narr/views.rst | 30 +++++++++++----------- .../lxmlgraph/step01/myapp/configure.zcml | 7 +++-- .../lxmlgraph/step02/myapp/configure.zcml | 7 +++-- docs/tutorials/lxmlgraph/step03.rst | 8 +++--- .../lxmlgraph/step03/myapp/configure.zcml | 9 +++---- .../lxmlgraph/step04/myapp/configure.zcml | 7 +++-- 12 files changed, 43 insertions(+), 51 deletions(-) (limited to 'docs') diff --git a/docs/glossary.rst b/docs/glossary.rst index 92286dfb1..c15f94883 100644 --- a/docs/glossary.rst +++ b/docs/glossary.rst @@ -240,7 +240,7 @@ Glossary used by Zope and :mod:`repoze.bfg` to describe associating a view with a model type. ZCML is capable of performing many different registrations and declarations, but its primary purpose in - :mod:`repoze.bfg` is to perform view mappings via the ``bfg:view`` + :mod:`repoze.bfg` is to perform view mappings via the ``view`` declaration. The ``configure.zcml`` file in a :mod:`repoze.bfg` application represents the application's :term:`application registry`. See :term:`repoze.bfg.convention` for an alternative @@ -259,7 +259,7 @@ Glossary or a request object in order to identify that the object is "of a type". Interfaces are used internally by :mod:`repoze.bfg` to perform view lookups and security policy lookups. Interfaces are - exposed to application programmers by the ``bfg:view`` ZCML + exposed to application programmers by the ``view`` ZCML directive in the form of both the ``for_`` attribute and the ``request_type`` attribute. They may be exposed to application developers when using the :term:`event` system as diff --git a/docs/narr/MyProject/myproject/configure.zcml b/docs/narr/MyProject/myproject/configure.zcml index 96f51d3c1..584dee906 100644 --- a/docs/narr/MyProject/myproject/configure.zcml +++ b/docs/narr/MyProject/myproject/configure.zcml @@ -1,11 +1,9 @@ - + - diff --git a/docs/narr/events.rst b/docs/narr/events.rst index c6242c25d..adb0ae7b0 100644 --- a/docs/narr/events.rst +++ b/docs/narr/events.rst @@ -152,13 +152,13 @@ the same model object. /> - - diff --git a/docs/narr/security.rst b/docs/narr/security.rst index 041fff89d..87eaeae0a 100644 --- a/docs/narr/security.rst +++ b/docs/narr/security.rst @@ -50,7 +50,7 @@ For example, the following declaration protects the view named .. code-block:: xml :linenos: - @@ -115,7 +115,7 @@ the special ``*`` character in the ``for`` attribute: .. code-block:: xml :linenos: - + - + - diff --git a/docs/tutorials/lxmlgraph/step02/myapp/configure.zcml b/docs/tutorials/lxmlgraph/step02/myapp/configure.zcml index d299dc883..2414ae6b2 100644 --- a/docs/tutorials/lxmlgraph/step02/myapp/configure.zcml +++ b/docs/tutorials/lxmlgraph/step02/myapp/configure.zcml @@ -1,9 +1,8 @@ - + - + - diff --git a/docs/tutorials/lxmlgraph/step03.rst b/docs/tutorials/lxmlgraph/step03.rst index 0f54f8761..ce88b78c8 100644 --- a/docs/tutorials/lxmlgraph/step03.rst +++ b/docs/tutorials/lxmlgraph/step03.rst @@ -20,14 +20,12 @@ Change your project's ``configure.zcml`` so that it looks like this: .. code-block:: xml - + - + - diff --git a/docs/tutorials/lxmlgraph/step03/myapp/configure.zcml b/docs/tutorials/lxmlgraph/step03/myapp/configure.zcml index 83d83ab61..43b766cfb 100644 --- a/docs/tutorials/lxmlgraph/step03/myapp/configure.zcml +++ b/docs/tutorials/lxmlgraph/step03/myapp/configure.zcml @@ -1,14 +1,13 @@ - + - + - - + - + - -- cgit v1.2.3