svn commit: r971329 - in /websites/production/tapestry/content: cache/main.pageCache exploring-the-project.html

[bu...@apache.org]

Author: buildbot
Date: Wed Nov  4 14:19:53 2015
New Revision: 971329

Log:
Production update by buildbot for tapestry

Modified:
    websites/production/tapestry/content/cache/main.pageCache
    websites/production/tapestry/content/exploring-the-project.html

Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/tapestry/content/exploring-the-project.html
==============================================================================
--- websites/production/tapestry/content/exploring-the-project.html (original)
+++ websites/production/tapestry/content/exploring-the-project.html Wed Nov  4 14:19:53 2015
@@ -228,18 +228,18 @@ public class Index
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">&lt;html t:type="layout" title="tutorial1 Index"
       t:sidebarTitle="Framework Version" ...
 </pre>
-</div></div><p>This binds two parameters, <code>title</code> and <code>sidebarTitle</code>, of the Layout component to the literal strings "tutorial1 Index" and "Current Time", respectively.</p><p>The Layout component will actually provide the bulk of the HTML ultimately sent to the browser; we'll look at its template in a later chapter. The point is, the page's template is integrated into the Layout component's template. The following diagram shows how parameters passed to the Layout component end up rendered in the final page:</p><p>    
+</div></div><p>This binds two parameters, <code>title</code> and <code>sidebarTitle</code>, of the Layout component to the literal strings "tutorial1 Index" and "Framework Version", respectively.</p><p>The Layout component will actually provide the bulk of the HTML ultimately sent to the browser; we'll look at its template in a later chapter. The point is, the page's template is integrated into the Layout component's template. The following diagram shows how parameters passed to the Layout component end up rendered in the final page:</p><p>    
 
 
 
 
-<span class="gliffy-container" id="gliffy-container-24346949-9182" data-fullwidth="913" data-ceoid="24188263" data-edit="${diagramEditLink.getLinkUrl()}" data-full="${diagramZoomLink.getLinkUrl()}" data-filename="Templates and Parameters">
+<span class="gliffy-container" id="gliffy-container-24346949-7589" data-fullwidth="913" data-ceoid="24188263" data-edit="${diagramEditLink.getLinkUrl()}" data-full="${diagramZoomLink.getLinkUrl()}" data-filename="Templates and Parameters">
 
-    <map id="gliffy-map-24346949-4085" name="gliffy-map-24346949-4085"></map>
+    <map id="gliffy-map-24346949-8786" name="gliffy-map-24346949-8786"></map>
 
-    <img class="gliffy-image gliffy-image-border" id="gliffy-image-24346949-9182" width="304" height="300" data-full-width="913" data-full-height="901" src="https://cwiki.apache.org/confluence/download/attachments/24188263/Templates%20and%20Parameters.png?version=2&amp;modificationDate=1371888025000&amp;api=v2" alt="Templates and Parameters" usemap="#gliffy-map-24346949-4085">
+    <img class="gliffy-image gliffy-image-border" id="gliffy-image-24346949-7589" width="304" height="300" data-full-width="913" data-full-height="901" src="https://cwiki.apache.org/confluence/download/attachments/24188263/Templates%20and%20Parameters.png?version=2&amp;modificationDate=1371888025000&amp;api=v2" alt="Templates and Parameters" usemap="#gliffy-map-24346949-8786">
 
-    <map class="gliffy-dynamic" id="gliffy-dynamic-map-24346949-9182" name="gliffy-dynamic-map-24346949-9182"></map>
+    <map class="gliffy-dynamic" id="gliffy-dynamic-map-24346949-7589" name="gliffy-dynamic-map-24346949-7589"></map>
 </span>