- add a ``add_view_mapper`` API to Configurator. This API allows you to add

  a named implementation of a ``pyramid.interfaces.IViewMapperFactory``
  interface.  Its name can be passed as a ``view_mapper`` argument to
  ``config.add_view``.  A view mapper allows objects that are meant to be
  used as view callables to have an arbitrary argument list and an arbitrary
  result.  This feature will be used by Pyramid extension developers, not by
  "civilians".

- New constructor argument to Configurator: ``default_view_mapper``.  Useful
  to create systems that have view callables with alternate default calling
  conventions.

- ``view_mapper`` argument to ``add_view`` should now be a view mapper *name*
  rather than an implementation.

- Add ``view_mapper`` argument to ``view_config`` decorator constructor.

- Remove (non-API) function of config.py named _map_view.

- Fix docstring for ``decorator`` argument to add_view.

- Factor invocation of view mapper into a viewderiver method.

- Promote view rendering and decorating into viewderiver, out of view mapper.

- Make requestonly into a function rather than a method of the default view
  mapper.

1 files changed, 4 insertions, 0 deletions

diff --git a/TODO.txt b/TODO.txt
index 5acc923a1..99944874c 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -16,6 +16,10 @@ Must-Have (before 1.0)
 - Allow ``decorator=`` and ``view_mapper=`` to be passed via ZCML and the
   ``view_config`` decorator.
 
+- Document ``Configurator.add_view_mapper``.
+
+- Consider the ability to defer the choice of view mapper.
+
 Should-Have
 -----------