From d66bfb5d1f1aef5cce4941b49740dbd136c95605 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 6 Sep 2009 03:36:59 +0000 Subject: Merge multiview2 branch to HEAD. --- docs/narr/hybrid.rst | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) (limited to 'docs/narr/hybrid.rst') diff --git a/docs/narr/hybrid.rst b/docs/narr/hybrid.rst index 48b2eedfc..34f606a97 100644 --- a/docs/narr/hybrid.rst +++ b/docs/narr/hybrid.rst @@ -259,9 +259,9 @@ application. Let's see what they are. "Global" Views Match Any Route When A More Specific View Doesn't ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Note that views that *don't* mention a ``route_name`` will *also* -match when *any* route matches. For example, the "bazbuz" view below -will be found if the route named "abc" below is matched. +Note that views that don't mention a ``route_name`` will *also* match +when *any* route matches. For example, the "bazbuz" view below will +be found if the route named "abc" below is matched. .. code-block:: xml @@ -323,7 +323,7 @@ name` to try to locate a view callable. A view is registered for a ``route`` either as its default view via the ``view=`` attribute of a ``route`` declaration in ZCML *or* as a standalone ```` declaration (or via the ``@bfg_route`` -decorator) which has a ``route_name`` that matches the route's name). +decorator) which has a ``route_name`` that matches the route's name. At startup time, when such a registration is encountered, the view is registered for the ``context`` type ``None`` (meaning *any* context) and a *special* request type which is dynamically generated. This @@ -463,9 +463,3 @@ statement ordering is very important, because routes are evaluated in a specific order, unlike traversal, which depends on emergent behavior rather than an ordered list of directives. -A ```` Statement *Must* Precede Any ```` Statement Which Mentions It -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -A ```` declaration *must* precede (in XML order) any ```` -declaration which names it as a ``route_name``. If it does not, at -application startup time a ``ConfigurationError`` will be raised. -- cgit v1.2.3