Changeset 2

Timestamp:

09/23/05 08:50:25 (3 years ago)

Author:

kevin

Message:

adding third party dependencies

Files:

• trunk (modified) (1 prop)
• trunk/docs/docs/gettingstarted.html (modified) (3 diffs)
• trunk/docs/docs/index.html (modified) (2 diffs)
• trunk/docs/docs/wiki20/index.html (modified) (1 diff)
• trunk/docs/download/dltemplate.pyc (modified) (previous)
• trunk/docs/newfile.html (moved) (moved from trunk/newfile.html)
• trunk/setup.cfg (modified) (1 diff)

trunk/docs/docs/gettingstarted.html

@@ -246 +246 @@
-        return dict(newvalue=value*2)
-    
-
+self, 
-        # do something intelligent based on which method
-        # failed
-</textarea>
-
-http://www.turbogears.org/docs/
+
-    
-    <p>If the validation fails, a method called validation_error (if present) will get called instead of the original target method. The first argument is a string with the name of the method that failed validation. You can use this to pick an appropriate template to render, for example. The second argument is the dictionary of arguments that was passed into the original method. The final argument is a list of Invalid exceptions that were raised.</p>
@@ -263 +263 @@
-    <h2><a name="templatechoice"></a>How a view template is chosen</h2>
-    
-
+
+
+
+
+
+
+
+
+
-    
-    <h2><a name="kid"></a>Brief introduction to Kid templates</h2>
-    
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-    
-    <h2><a name="predefined"></a>Template variables you get for free</h2>
-    
+    <p>All templates that get rendered by TurboGears have access to some basic variables automatically. The variables are defined in the stdvars function in turbogears.view. They provide conveniences for identifying the user's browser, plus common template tasks. See the <a href="api/turbogears.view-module.html#stdvars">stdvars documentation</a> for the complete list.</p>
+    
+    <p>In order to avoid name collisions with your own template variables, all of the predefined variables are found in "std". For example, the user agent is found in std.useragent.</p>
+    
+    <p>One in particular that's worth noting is std.ipeek, which lets you look at the first item of an iterator without actually consuming it from the iterator. This comes in handy when you have an iterator that <em>might</em> be empty. If it is empty, you may not display a whole block from your template. Here's an example:</p>
+    
+    <textarea name="code" class="xhtml"><![CDATA[
+<?python items=std.ipeek(shoppingcart) ?>
+<div py:if="items">
+    <p>Your cart contains:</p>
+    <ul>
+        <li py:for="item in items" py:content="item">Watermelon</li>
+    </ul>
+</div>
+<div py:if="not items">
+    <p>Your cart is empty</p>
+</div>
+]]></textarea>
+    
+    <p>When you have a list, you don't need to use std.ipeek. But, when all you have is an iterator, this is a handy tool.</p>
+    
+    <p>If you have site-wide variables that you would like available in your templates, you can add a callable to <a href="api/turbogears.view-module.html#variableProviders">turbogears.view.variableProviders</a>. This will be called with a dictionary that is already set up with the TurboGears standard variables. If you want the current time available in all of your templates, you can just add this to a module:</p>
+    
+    <textarea name="code" class="py"><![CDATA[
+import time
+from turbogears import view
+
+def addtimevar(variables):
+    variables["currenttime"] = time.ctime()
+
+view.variableProviders.append(addtimevar)
+]]></textarea>
+    
-    <h2><a name="json"></a>JSON output</h2>
-    
-
+
+
+
+
+
+
+
+
+
-    
-    <h2><a name="mochikit"></a>Brief introduction to MochiKit</h2>
@@ -289 +464 @@
-    <script src="../../sh/shCore.js" py:attrs="src=root+'sh/shCore.js'"></script>
-    <script src="../../sh/shBrushPython.js" py:attrs="src=root+'sh/shBrushPython.js'"></script>
+    <script src="../../sh/shBrushXml.js" py:attrs="src=root+'sh/shBrushXml.js'"></script>
-    <script language="javascript">
-        dp.SyntaxHighlighter.HighlightAll('code');

trunk/docs/docs/index.html

@@ -14 +14 @@
-    <ul>
-        <li><a href="api/index.html">TurboGears Python API</a></li>
-2
-3
+4
+4
-        <li><a href="http://www.mochikit.com/doc/html/MochiKit/index.html">MochiKit JavaScript Library</a></li>
-
+ (one note about this doc: the warning at the top is inaccurate. The current language is expected to be blessed as 1.0.)
-        <li><a href="http://docs.python.org/lib/lib.html">Python Standard Library</a></li>
-    </ul>
@@ -23 +23 @@
-    <h2>Manuals</h2>
-    <ul>
-1
+3
-        <li><a href="contributing.html">Contributing to TurboGears</a> &#8212; coming soon, expected 9/30/2005.</li>
-        <li><a href="deployment.html">Deploying TurboGears applications</a></li>

trunk/docs/docs/wiki20/index.html

@@ -24 +24 @@
-    
-    <ol>
+        <li>docutils 0.3.9, which is used for formatting. You could get away with not having docutils, but it's not as much fun. <code>easy_install.py docutils</code> should get you what you need.</li>
-        <li>A web browser</li>
-        <li>Your favorite editor</li>
-        <li>Two command line windows (you only <em>need</em> one, but two is nicer.)</li>
-        <li>A database. If you don't have one, your best bet is sqlite 3.2+ with pysqlite 2.0+.</li>
-        <li>docutils, which is used for formatting. You could get away with not having docutils, but it's not as much fun. <code>easy_install.py docutils</code> should get you what you need.</li>
-    </ol>
-    

trunk/setup.cfg

@@ -4 +4 @@
-[docs]
-templates=content=docs/template.html,printable=docs/printable.html
-
+docs/wiki20/20MinuteWiki.mov=../../Documents/TurboGears/20MinuteWiki.mov, 
-