From: richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2>
Date: Tue, 18 Feb 2003 21:10:42 +0000 (+0000)
Subject: added info about structure/not:/path()
X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=3df6e215c7157bc049f8ef16201e47ef05109895;p=roundup.git

added info about structure/not:/path()


git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@1526 57a73879-2fb5-44c3-a270-3262357dd7e2
---

diff --git a/doc/customizing.txt b/doc/customizing.txt
index bcaf3d3..b09e5e7 100644
--- a/doc/customizing.txt
+++ b/doc/customizing.txt
@@ -2,7 +2,7 @@
 Customising Roundup
 ===================
 
-:Version: $Revision: 1.74 $
+:Version: $Revision: 1.75 $
 
 .. This document borrows from the ZopeBook section on ZPT. The original is at:
    http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
@@ -998,6 +998,9 @@ forms:
    ``request/form/foo/value | default`` would simply leave the current HTML
    in place if the "foo" form variable doesn't exist.
 
+   You may use the python function ``path``, as in ``path("item/status")``, to
+   embed path expressions in Python expressions.
+
 **String Expressions** - eg. ``string:hello ${user/name}``
    These expressions are simple string interpolations - though they can be just
    plain strings with no interpolation if you want. The expression in the
@@ -1009,6 +1012,18 @@ forms:
    equivalent to ``item/status/checklist``, assuming that ``checklist`` is
    a method.
 
+Modifiers:
+
+**structure** - eg. ``structure python:msg.content.plain(hyperlink=1)``
+   The result of expressions are normally *escaped* to be safe for HTML
+   display (all "<", ">" and "&" are turned into special entities). The
+   ``structure`` expression modifier turns off this escaping - the result
+   of the expression is now assumed to be HTML structured text.
+
+**not:** - eg. ``not:python:1=1``
+   This simply inverts the logical true/false value of another expression.
+
+
 Template Macros
 ~~~~~~~~~~~~~~~