Features

--------

- The ``Configurator.add_view`` method now accepts an argument named
  ``context``.  This is an alias for the older argument named
  ``for_``; it is preferred over ``for_``, but ``for_`` will continue
  to be supported "forever".

- The ``view`` ZCML directive now accepts an attribute named
  ``context``.  This is an alias for the older attribute named
  ``for``; it is preferred over ``for``, but ``for`` will continue to
  be supported "forever".

- The ``Configurator.add_route`` method now accepts an argument named
  ``view_context``.  This is an alias for the older argument named
  ``view_for``; it is preferred over ``view_for``, but ``view_for``
  will continue to be supported "forever".

- The ``route`` ZCML directive now accepts an attribute named
  ``view_context``.  This is an alias for the older attribute named
  ``view_for``; it is preferred over ``view_for``, but ``view_for``
  will continue to be supported "forever".

Documentation and Paster Templates
----------------------------------

- All uses of the ``Configurator.add_view`` method that used its
  ``for_`` argument now use the ``context``argument instead.

- All uses of the ``Configurator.add_route`` method that used its
  ``view_for`` argument now use the ``view_context``argument instead.

- All uses of the ``view`` ZCML directive that used its ``for``
  attribute now use the ``context`` attribute instead.

- All uses of the ``route`` ZCML directive that used its ``view_for``
  attribute now use the ``view_context`` attribute instead.

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index e4ce4f56d..296589c62 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -655,9 +655,9 @@ administrative interface), you can register a route like ``<route
 name="manage" path="manage/*traverse"/>`` and then associate
 "management" views in your code by using the ``route_name`` argument
 to a ``view`` configuration, e.g. ``<view view=".some.callable"
-for=".some.Model" route_name="manage"/>``.  If you wire things up this
-way someone then walks up to for example, ``/manage/ob1/ob2``, they
-might be presented with a management interface, but walking up to
+context=".some.Model" route_name="manage"/>``.  If you wire things up
+this way someone then walks up to for example, ``/manage/ob1/ob2``,
+they might be presented with a management interface, but walking up to
 ``/ob1/ob2`` would present them with the default object view.  There
 are other tricks you can pull in these hybrid configurations if you're
 clever (and maybe masochistic) too.