svn commit: r572687 - in /tapestry/tapestry5/trunk: tapestry-core/src/site/apt/guide/appstate.apt tapestry-tutorial1/src/site/apt/hilo.apt

[hl...@apache.org]

Author: hlship
Date: Tue Sep  4 07:01:57 2007
New Revision: 572687

URL: http://svn.apache.org/viewvc?rev=572687&view=rev
Log:
Make some minor corrections to the documentation.

Modified:
    tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/appstate.apt
    tapestry/tapestry5/trunk/tapestry-tutorial1/src/site/apt/hilo.apt

Modified: tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/appstate.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/appstate.apt?rev=572687&r1=572686&r2=572687&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/appstate.apt (original)
+++ tapestry/tapestry5/trunk/tapestry-core/src/site/apt/guide/appstate.apt Tue Sep  4 07:01:57 2007
@@ -43,9 +43,9 @@
 Check for Creation
 
   Scalable web applications do not create the server-side session needlessly. If you can avoid creating the session, especially on first
-  access to your web application, you will be able to handle an order of magnatude more users. So, if you can avoid creating the ASO, you should do so.
+  access to your web application, you will be able to handle an order of magnitude more users. So, if you can avoid creating the ASO, you should do so.
   
-  But how to avoid creating it?  Simply checkng ("_myState != null") will force the creation of the ASO and the session to store it in.
+  But how to avoid creating it?  Simply checking ("_myState != null") will force the creation of the ASO and the session to store it in.
   
   Instead, create a second field:
   

Modified: tapestry/tapestry5/trunk/tapestry-tutorial1/src/site/apt/hilo.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-tutorial1/src/site/apt/hilo.apt?rev=572687&r1=572686&r2=572687&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/tapestry-tutorial1/src/site/apt/hilo.apt (original)
+++ tapestry/tapestry5/trunk/tapestry-tutorial1/src/site/apt/hilo.apt Tue Sep  4 07:01:57 2007
@@ -280,7 +280,7 @@
   <p>Make a guess between one and ten:</p>
   
     <t:loop source="1..10" value="guess">
-      <t:actionlink t:id="guess" context="guess">${guess}</t:actionlink>
+      <t:actionlink t:id="link" context="guess">${guess}</t:actionlink>
     </t:loop>
 
   </body>
@@ -341,10 +341,24 @@
     return null;
   }
 ---  
+
+
+  
   
   Here's the big news: Tapestry will convert the number from the URL back into
   an integer automatically, so that it can pass it in to this method as a parameter.
   We can then compare the guess from the user to the secret target number.
+  
+
+  We need to update the Guess page to actually display the message; this is done by adding the following:
+  
+---
+  <p>${message}</p>
+---
+
+  This is truly bare bones and, when message is null, will output an empty \<p\> element.  A real application
+  would dress this up a bit more (using CSS and the like to make it prettier).
+  
   
   We do need a basic GameOver page.