You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by jk...@apache.org on 2006/10/15 01:43:12 UTC

svn commit: r464065 [3/3] - in /tapestry/tapestry4/trunk/src/site: ./ apt/UsersGuide/ apt/ajax/ apt/javascript/ apt/usersguide/ fml/ resources/css/ xdoc/ xdoc/QuickStart/ xdoc/UsersGuide/ xdoc/components/ xdoc/components/dojo/ xdoc/components/form/ xdo...

Copied: tapestry/tapestry4/trunk/src/site/xdoc/quickstart/forms.xml (from r464062, tapestry/tapestry4/trunk/src/site/xdoc/QuickStart/forms.xml)
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/quickstart/forms.xml?view=diff&rev=464065&p1=tapestry/tapestry4/trunk/src/site/xdoc/QuickStart/forms.xml&r1=464062&p2=tapestry/tapestry4/trunk/src/site/xdoc/quickstart/forms.xml&r2=464065
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/QuickStart/forms.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/quickstart/forms.xml Sat Oct 14 16:43:08 2006
@@ -76,7 +76,7 @@
 
             <p>
                 We've introduced another handy component,
-                <a href="site:Shell">Shell</a>
+                <a href="../components/general/shell.html">Shell</a>
                 . This component is just a convienience for generating the &lt;html&gt;,
                 &lt;head&gt;, and &lt;title&gt; tags (though it has quite a few other tricks up its
                 sleeve).
@@ -313,33 +313,33 @@
 
                 <ul>
                     <li>
-                        <a href="site:Body">Body</a>
+                        <a href="../components/general/body.html">Body</a>
                         -- organizes the JavaScript generated for the page (needed to use the
-                        <a href="site:DatePicker">DatePicker</a>
+                        <a href="../components/form/datepicker.html">DatePicker</a>
                         )
                     </li>
                     <li>
-                        <a href="site:Form">Form</a>
+                        <a href="../components/form/form.html">Form</a>
                         -- generates an HTML form and controls the submit behavior
                     </li>
                     <li>
-                        <a href="site:TextField">TextField</a>
+                        <a href="../components/form/textfield.html">TextField</a>
                         -- creates a text field (&lt;input type="text"/&gt;) used to
                         <em>edit</em>
                         (read and update) a property of the page
                     </li>
                     <li>
-                        <a href="site:TextArea">TextArea</a>
+                        <a href="../components/form/textarea.html">TextArea</a>
                         -- as with
-                        <a href="site:TextField">TextField</a>
+                        <a href="../components/form/textfield.html">TextField</a>
                         , but generates a multi-line &lt;textarea&gt;
                     </li>
                     <li>
-                        <a href="site:DatePicker">DatePicker</a>
+                        <a href="../components/form/datepicker.html">DatePicker</a>
                         -- a JavaScript popup calendar
                     </li>
                     <li>
-                        <a href="site:Checkbox">Checkbox</a>
+                        <a href="../components/form/checkbox.html">Checkbox</a>
                         -- edits a
                         <em>boolean</em>
                         property of the page
@@ -348,30 +348,30 @@
 
                 <p>
                     The
-                    <a href="site:Form">Form</a>
+                    <a href="../components/form/form.html">Form</a>
                     's success parameter is linked to a listener method. It is invoked only when
                     there are no validation errors. We'll discuss validation in a later tutorial.
                 </p>
 
                 <p>
                     The
-                    <a href="site:Body">Body</a>
+                    <a href="../components/general/body.html">Body</a>
                     component plays a crucial role in Tapestry; it organizes all the JavaScript
                     generated when a page renders. It assists components with generated unique names
                     for client-side variables and functions, and organizes all the JavaScript
                     generated by all the component within the page into two large blocks (one at the
                     top of the page, one at the bottom). The
-                    <a href="site:DatePicker">DatePicker</a>
+                    <a href="../components/form/datepicker.html">DatePicker</a>
                     component will not operate unless it is enclosed by a
-                    <a href="site:Body">Body</a>
+                    <a href="../components/general/body.html">Body</a>
                     component.
                 </p>
 
                 <p>
                     The
-                    <a href="site:TextField">TextField</a>
+                    <a href="../components/form/textfield.html">TextField</a>
                     and
-                    <a href="site:TextArea">TextArea</a>
+                    <a href="../components/form/textarea.html">TextArea</a>
                     components edit properties of the page. Because the value parameter is an
                     <a href="http://www.ognl.org">OGNL</a>
                     expression, it is not limited to editting properties directly exposed by the
@@ -441,7 +441,7 @@
                 <p>
                     What we need to do is create an instance of ProjectRelease and store it into the
                     property so that the
-                    <a href="site:TextField">TextField</a>
+                    <a href="../components/form/textfield.html">TextField</a>
                     components can edit it. We have to be careful because in a live application,
                     pages will be pooled and reused constantly.
                 </p>
@@ -532,7 +532,7 @@
                 <p>
                     So ... how did the ProjectRelease object stick around? Shouldn't we have gotten
                     a NullPointerException again, when the form submitted and the
-                    <a href="site:TextField">TextField</a>
+                    <a href="../components/form/textfield.html">TextField</a>
                     component updated property project.name? What actually happened is that the
                     ProjectRelease object was discarded ... but when a form is submitted on a page,
                     the PageBeginRender interface is triggered again, just like for a form render.

Copied: tapestry/tapestry4/trunk/src/site/xdoc/quickstart/helloworld.xml (from r464062, tapestry/tapestry4/trunk/src/site/xdoc/QuickStart/helloworld.xml)
URL: http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/xdoc/quickstart/helloworld.xml?view=diff&rev=464065&p1=tapestry/tapestry4/trunk/src/site/xdoc/QuickStart/helloworld.xml&r1=464062&p2=tapestry/tapestry4/trunk/src/site/xdoc/quickstart/helloworld.xml&r2=464065
==============================================================================
--- tapestry/tapestry4/trunk/src/site/xdoc/QuickStart/helloworld.xml (original)
+++ tapestry/tapestry4/trunk/src/site/xdoc/quickstart/helloworld.xml Sat Oct 14 16:43:08 2006
@@ -182,7 +182,7 @@
 
             <p>
                 The "@Insert" value for the jwcid attribute can be thought of as "instance of the
-                <a href="site:Insert">Insert</a>
+                <a href="../components/general/insert.html">Insert</a>
                 component". Insert is one of many built-in Tapestry components. This isn't quite the
                 Java class; it is a component type, which is used by Tapestry to find out about the
                 component, such as what parameters can be configured and what Java class contains
@@ -330,7 +330,7 @@
 
             <p>
                 Again, anything dynamic in Tapestry is going to involve a component; here it's the
-                <a href="site:PageLink">PageLink</a>
+                <a href="../components/link/pagelink.html">PageLink</a>
                 component, one of a family of components that generate callback links into a
                 Tapestry application.
             </p>