Changes between Version 8 and Version 9 of QuickStart/4:HandlingaForm

Timestamp:

12/02/09 15:42:10 (16 years ago)

Author:

DanWilson (IP: 71.77.43.34)

Comment:

--

QuickStart/4:HandlingaForm

@@ -40 +40 @@
 {{{
 <controller name="MyController" type="translator.controller.Controller">
-    <message-listener message="OnRequestStart" function="OnRequestStart" />
-    <message-listener message="OnRequestEnd" function="OnRequestEnd" />
+    <message-listener message="OnRequestStart" />
+    <message-listener message="OnRequestEnd" />
     <message-listener message="NeedTranslation" function="TranslatePhrase" />
 </controller>
 }}}
+
+(Note: If you do specify a function attribute, when the message is broadcast, it will call that specific function on the controller. If you do not specify a function attribute, Model-Glue will call a function named the same as the value of the message attribute.)
 
 Ok, now try the form. Again.
@@ -68 +70 @@
 }}}
 
-(Note that in prior versions of the framework, the addTraceStatement() function was named trace(), but this was changed in order to support !ColdFusion 9, which was added a native trace() function to CFML.)
+(Note: that in prior versions of the framework, the addTraceStatement() function was named trace(), but this was changed in order to support !ColdFusion 9, which was added a native trace() function to CFML.)
 
 So what does all that do?
 
-First, arguments.event is like the twin sibling of the viewstate variable in a view. It has a getValue() method to get variables from the FORM and URL scopes. However, it also has a setValue() method that can set values into the viewstate, readable in views or later message listener functions.
+If you recall from the last segment, the event object has a getValue() method to get variables from the FORM and URL scopes. The Event object also has a setValue() method that can set values into the event, readable in views or later message listener functions.
 
 Second, it creates an instance of our application's Model CFC:
@@ -95 +97 @@
 
 {{{
-<cfset arguments.event.trace("TranslatePhrase Results", result) />
+<cfset arguments.event.addTraceStatement("TranslatePhrase Results", result) />
 }}}
 
-Last, it sets the results of the translation into the viewstate so that our view templates can display the data:
+Last, it sets the results of the translation into the event object so that our view templates can display the data:
 
 {{{
@@ -108 +110 @@
 As a last step, let's add a view that shows our translated phrase. That'd probably make users happy, because we'll turn the debugging trace off when we deploy this application.
 
-Following the same steps as we did when we built the form, first add a dspPhrase.cfm file to /translator/views. You'll notice that we again use an eXit Event, this time to build a link back to the translation form. To the link, we append the "phrase" value. If you look back at frmPhrase.cfm, the VALUE attribute of our <cfinput> tag was set to viewstate.getValue("phrase"). getValue(), by default, returns an empty string if a value is not defined. By appending the phrase to the URL, we can set the default value of the input box.
+Following the same steps as we did when we built the form, first add a dspPhrase.cfm file to /translator/views. You'll notice that we again use an eXit Event, this time to build a link back to the translation form. To the link, we append the "phrase" value, using the second argument to the event.linkTo() method. If you look back at frmPhrase.cfm, the VALUE attribute of our <cfinput> tag was set to event.getValue("phrase"). getValue(), by default, returns an empty string if a value is not defined. By appending the phrase to the URL, we can set the default value of the input box.
 
 {{{
-<cfset translationForm = viewstate.getValue("myself") & viewstate.getValue("xe.translationForm")
-    & "&phrase=" & viewstate.getValue("phrase") />
-<cfset translatedPhrase = viewstate.getValue("translatedPhrase") />
+<cfset translationForm = event.linkTo( event.getValue("xe.translationForm"), "phrase" ) />
+<cfset translatedPhrase = event.getValue("translatedPhrase") />
 
 <cfoutput>