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, 8 insertions, 8 deletions

diff --git a/docs/glossary.rst b/docs/glossary.rst
index e649b3498..c8c07ebb4 100644
--- a/docs/glossary.rst
+++ b/docs/glossary.rst
@@ -409,16 +409,16 @@ Glossary
      internally by :mod:`repoze.bfg` to perform view lookups and other
      policy lookups.  The ability to make use of an interface is
      exposed to an application programmers during :term:`view
-     configuration` via the ``for`` argument, the ``request_type``
+     configuration` via the ``context`` argument, the ``request_type``
      argument and the ``containment`` argument.  Interfaces are also
      exposed to application developers when they make use of the
-     :term:`event` system. Fundamentally, :mod:`repoze.bfg` programmers
-     can think of an interface as something that they can attach to an
-     object that stamps it with a "type" unrelated to its underlying
-     Python type.  Interfaces can also be used to describe the behavior
-     of an object (its methods and attributes), but unless they choose
-     to, :mod:`repoze.bfg` programmers do not need to understand or use
-     this feature of interfaces.
+     :term:`event` system. Fundamentally, :mod:`repoze.bfg`
+     programmers can think of an interface as something that they can
+     attach to an object that stamps it with a "type" unrelated to its
+     underlying Python type.  Interfaces can also be used to describe
+     the behavior of an object (its methods and attributes), but
+     unless they choose to, :mod:`repoze.bfg` programmers do not need
+     to understand or use this feature of interfaces.
 
    event
      An object broadcast to zero or more :term:`subscriber` callables