Author: dolander
Date: Fri Sep  9 09:50:27 2005
New Revision: 279815

URL: http://svn.apache.org/viewcvs?rev=279815&view=rev
Log:
Apply a few edits to the tag documents


Modified:
    
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormControls.xml
    
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormRepeating.xml
    
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsOverview.xml

Modified: 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormControls.xml
URL: 
http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormControls.xml?rev=279815&r1=279814&r2=279815&view=diff
==============================================================================
--- 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormControls.xml
 (original)
+++ 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormControls.xml
 Fri Sep  9 09:50:27 2005
@@ -9,7 +9,7 @@
         <section id="Intro">
             <title>Introduction</title>
             <p> 
-                The following table summarizes the two basic NetUI tags which 
render as form controls.  There
+                The following table summarizes the basic NetUI tags which 
render as form controls.  There
                 are basic types, simple controls and group controls.  The 
simple controls map directly
                 to a single HTML element.  The group controls map to more than 
one HTML element, for example
                 the <code>&lt;select></code> and <code>&lt;option></code> 
elements represent a select box.
@@ -53,7 +53,10 @@
                 In the following example the anchor is found inside of the 
<code>&lt;netui:form></code>, which
                 is a requirement for using a anchor to submit a form.  In 
order to submit a form, the
                 <code>formSubmit</code> attribute is set to <code>true</code>. 
 In addition, there
-                is no requirement to set an <code>action</code> or 
<code>href</code> on the anchor.
+                is no requirement to set an <code>action</code> or 
<code>href</code> on the anchor.  It is possible
+                to submit a form when the anchor appears outside of the form.  
This requires setting the
+                <code>getJavaScript</code> attribute on the 
<code>&lt;netui:form></code> tag.  Then you need
+                to add the following code to the anchor 
<code>onClick="anchor_submit_form(name-of-form, action);return false;"</code>.
             </p>
             <p> The anchor does not bind to a <code>dataSource</code> of any 
type.
             </p>
@@ -206,7 +209,7 @@
         </section>
         <section id="FileUpload">
             <title>FileUpload</title>
-            <p> The <code>&lt;fileUpload></code> tag allows a file to be 
uploaded to the server.  By
+            <p> The <code>&lt;netui:fileUpload></code> tag allows a file to be 
uploaded to the server.  By
                 default, this tag is not enabled because multipart request 
handling is disabled.
                 The only supported
                 data type that can be bound to is 
<code>org.apache.struts.upload.FormFile</code>.  If
@@ -468,7 +471,7 @@
                     value from the list to be selected.  The natural data type 
that is bound to is
                     a <code>java.lang.String</code>.
                 </p>
-                <p> In the example below, a select box contains four option.
+                <p> In the example below, a select box contains four options.
                 </p>
                 <source><![CDATA[
 <netui:select dataSource="actionForm.singleSelect">
@@ -574,7 +577,7 @@
                 either <code>text</code> or <code>password</code> by setting 
the <code>type</code> attribute.
                 The default is <code>text</code>.  The natural
                 data type bound to by a text box is 
<code>java.lang.String</code>.  The code below creates
-                a text box and binds it to a propery in the 
<code>actionForm</code>
+                a text box and binds it to a property in the 
<code>actionForm</code>
             </p>
             <source>
 &lt;netui:textBox dataSource="actionForm.textBox" />

Modified: 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormRepeating.xml
URL: 
http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormRepeating.xml?rev=279815&r1=279814&r2=279815&view=diff
==============================================================================
--- 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormRepeating.xml
 (original)
+++ 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsFormRepeating.xml
 Fri Sep  9 09:50:27 2005
@@ -387,8 +387,8 @@
 </source>
                 <p>The page flow controller is a simple controller that 
contains the properties
                     exposing the options and a property that will be set when 
the form is posted.
-                    The options are build in the <code>onCreate</code> method. 
 For the
-                    <code>optionsDataSource</code> each options is defined 
through an instance
+                    The options are built in the <code>onCreate</code> method. 
 For the
+                    <code>optionsDataSource</code> each option is defined 
through an instance
                     of the <code>Options</code> class.
                 </p>
                 <p><strong>Controller.jpf</strong></p>
@@ -402,8 +402,7 @@
 @Jpf.Controller(
     simpleActions={
         @Jpf.SimpleAction(name="begin", path="index.jsp")
-    },
-    multipartHandler=Jpf.MultipartHandler.memory
+    }
 )
 public class Controller extends PageFlowController
 {

Modified: 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsOverview.xml
URL: 
http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsOverview.xml?rev=279815&r1=279814&r2=279815&view=diff
==============================================================================
--- 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsOverview.xml
 (original)
+++ 
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/netui/tagsOverview.xml
 Fri Sep  9 09:50:27 2005
@@ -47,7 +47,7 @@
         </section>
         <section id="RuntimeErrors">
             <title>Runtime Error Reporting</title>
-            <p> The Tag Libraries report runtime errors in a common way.  In 
the page fragment below, a set of
+            <p> The tag libraries report runtime errors in a common way.  In 
the page fragment below, a set of
                 anchors have invalid attribute values.  There is an error 
reported where the tag would normally
                 have rendered HTML.  In addition, there is a table rendered at 
the end of the document that
                 contains the details of the errors.  In many cases, runtime 
errors in the tags result in the
@@ -102,9 +102,9 @@
         <section id="templateTags">
             <title>Template Tags</title>
             <p> The template tags represent a very simple templating system.  
The tags allow for a very simple
-                template page to be created.  Content pages then include their 
template to for the resulting
+                template page to be created.  Content pages then include their 
template to form the resulting
                 rendered page.  The content pages are written as sections of 
content that are inserted into defined
-                points inside the template. For more information on teh 
template tags see the
+                points inside the template. For more information on the 
template tags see the
                 <a href="site:pageflow/tags/pageflow_template">NetUI Template 
Tags</a> topic.
             </p>
         </section>


Reply via email to