Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 192.1
edited by Ravi Mendis
on 2009/07/17 06:21
Change comment: There is no comment for this version
To version 193.1
edited by Ravi Mendis
on 2009/07/17 06:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -87,7 +87,7 @@
87 87  In ERPrototaculous you may still have typical WebObjects forms (i.e WOForm) as well as use ajax forms (i.e **AjaxUpdaterForm**).
88 88  They behave differently in that an AjaxUpdaterForm will update the contents of a container as opposed to the entire page.
89 89  
90 -== Ajax Page Caching in ERPrototaculous ==
90 +== Ajax Response Handling in ERPrototaculous ==
91 91  
92 92  One notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
93 93  In ERPrototaculous, updates and actions break with "The WebObjects Way" by being pseudo-stateless.
... ... @@ -100,7 +100,7 @@
100 100  
101 101  So for ajax, the current state of the page fragment component is all that is necessary.
102 102  
103 -== Actions in ERPrototaculous ==
103 +== Ajax Actions in ERPrototaculous ==
104 104  
105 105  Typically, in a WebObjects application, an action would return the contents of the entire page.
106 106  
... ... @@ -121,3 +121,5 @@
121 121  Perhaps the only real similarity to Ajax.framework is the ajax update container.
122 122  **WXGenericContainer** is the ERPrototaculous update container.
123 123  It is similar to an AjaxUpdateContainer when it has the binding ##ajax = true##, otherwise it's pretty much like **WOGenericContainer**.
124 +
125 +It has been implemented as a utility or //convenience// for Prototype's ##Ajax.Updater##.