summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2010-11-01 00:43:43 -0400
committerChris McDonough <chrism@plope.com>2010-11-01 00:43:43 -0400
commitf5fa3f9e2a754ce199386e3f20735cd2dfbbc3fc (patch)
tree2c53687d943aad9e28a116453a20fbc80c329406 /docs
parent6f1973b325cba5600eb91ff6982baf68b4567336 (diff)
downloadpyramid-f5fa3f9e2a754ce199386e3f20735cd2dfbbc3fc.tar.gz
pyramid-f5fa3f9e2a754ce199386e3f20735cd2dfbbc3fc.tar.bz2
pyramid-f5fa3f9e2a754ce199386e3f20735cd2dfbbc3fc.zip
for performance reasons (to avoid unnecessary ZCA lookups), pass the helper object itself to a renderer rather than a dictionary derivation)
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/views.rst16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index 7e3dfebf1..e1983222d 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -739,8 +739,8 @@ following interface:
class RendererFactory:
def __init__(self, info):
- """ Constructor: ``info`` will be a dictionary containing
- the following keys: ``name`` (the renderer name), ``package``
+ """ Constructor: ``info`` will be an object having the
+ the following attributes: ``name`` (the renderer name), ``package``
(the package that was 'current' at the time the renderer was
registered), ``type`` (the renderer type name), ``registry``
(the current application registry) and ``settings`` (the
@@ -757,14 +757,14 @@ following interface:
There are essentially two different kinds of renderer factories:
- A renderer factory which expects to accept a :term:`resource specification`
- or an absolute path as the ``name`` value in the ``info`` value fed to its
- constructor. These renderer factories are registered with a ``name`` value
- that begins with a dot (``.``). These types of renderer factories usually
- relate to a file on the filesystem, such as a template.
+ or an absolute path as the ``name`` attribute of the ``info`` object fed to
+ its constructor. These renderer factories are registered with a ``name``
+ value that begins with a dot (``.``). These types of renderer factories
+ usually relate to a file on the filesystem, such as a template.
- A renderer factory which expects to accept a token that does not represent a
- filesystem path or a resource specification in the ``name`` value of the
- ``info`` dict fed to its constructor. These renderer factories are
+ filesystem path or a resource specification in the ``name`` attribute of the
+ ``info`` object fed to its constructor. These renderer factories are
registered with a ``name`` value that does not begin with a dot. These
renderer factories are typically object serializers.