Changes between Version 7 and Version 8 of QuickStart/3:BuildingaForm

Timestamp:

12/21/09 20:49:46 (16 years ago)

Author:

cfgrok (IP: 64.30.223.5)

Comment:

Updates to Quickstart Section

QuickStart/3:BuildingaForm

@@ -11 +11 @@
 
 {{{
-<cfset submit = event.linkTo( event.getValue("xe.translate") ) />
+<cfset submit = event.linkTo( event.getValue("xe_translate") ) />
 
 <cfform action="#submit#">
@@ -19 +19 @@
 }}}
 
-Ok - what's with this "event" stuff?
+OK - what's with this "event" stuff?
 
-Whenever you're writing a .CFM view, there are two variables always available: "event" and "viewcollection." We'll get to viewcollection in a bit, but here's the rundown on event:
- Event::
-  An event object contains all the variables FORM and URL scopes as well as any other values added by the framework.
+Whenever you're writing a .CFM view, there are two variables always available: "event" and "viewcollection". We'll get to viewcollection in a bit, but here's the rundown on event:
+
+Event:
+  An event object contains all the variables in the FORM and URL scopes as well as any other values added by the framework.
+
 The event object contains data like a query from a database or (big surprise) the translated version of the phrase that we're asking the user to enter.
 
@@ -35 +37 @@
   * "eventValue" is the name of the URL variable that contains the current event. Don't worry about this one much, either.
 
-Therefore, the first line in that frmPhrase.cfm says "make me a link please, and use the value in the event object for 'xe.translate' as the name of the event."
+Therefore, the first line in that frmPhrase.cfm says "make me a link please, and use the value in the event object for 'xe_translate' as the name of the event."
 
-So what's with this "xe.translate" value? "XE" stands for "eXit Event," and has emerged as a best practice in Model-Glue applications (because it's taken from a best practice in Fusebox!). It lets us reuse this view in multiple places because we determine the action page of the form at runtime, instead of hard coding it into our .CFM template.
+So what's with this "xe_translate" value? "XE" stands for "eXit Event," and has emerged as a best practice in Model-Glue applications (because it's taken from a best practice in Fusebox!). It lets us reuse this view in multiple places because we determine the action page of the form at runtime, instead of hard coding it into our .CFM template.
 
-So where does the value of xe.translate come from? It's time to learn a bit of Model-Glue XML. (Don't worry! I just wrote the entire tag reference, and it's only sixteen tags! And about five of them are just placeholders that contain other tags!)
+So where does the value of xe_translate come from? It's time to learn a bit of Model-Glue XML. (Don't worry! I just wrote the entire tag reference, and it's only sixteen tags! And about five of them are just placeholders that contain other tags!)
 
 To create the actual event handler to display the form, do the following:
@@ -70 +72 @@
 }}}
 
-Now, we need to provide the value for "xe.translate." We do this with the (very aptly named!) <value> tag:
+Now, we need to provide the value for "xe_translate." We do this with the (very aptly named!) <value> tag:
 
 {{{
@@ -77 +79 @@
         <views>
             <include name="body" template="frmPhrase.cfm">
-                <value name="xe.translate" value="translationFormAction" />
+                <value name="xe_translate" value="translationFormAction" />
             </include>
         </views>
@@ -86 +88 @@
 }}}
 
-Finally, run the page by visiting http://localhost/translator/index.cfm?event=translationForm . You should see your form. Viewing its source, you'll see that its action page is index.cfm?event=translationFormAction.
+Finally, run the page by visiting http://localhost/translator/index.cfm?event=translationForm. You should see your form. Viewing its source, you'll see that its action page is index.cfm?event=translationFormAction.
 
 You've just learned about a quarter of the Model-Glue framework. Not too bad, eh?
+
 ----
 
-Back [wiki:QuickStart/2:ModellingourApplication#Quickstart2:ModelingourApplication Quickstart 2: Modeling our Application]
+Back [wiki:QuickStart/2:ModellingourApplication Quickstart 2: Modeling our Application]
 
-Next [wiki:QuickStart/4:HandlingaForm#Quickstart4:HandlingaForm Quickstart 4: Handling a Form]
+Next [wiki:QuickStart/4:HandlingaForm Quickstart 4: Handling a Form]