Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 189.1
edited by Ravi Mendis
on 2009/07/17 06:24
Change comment: There is no comment for this version
To version 186.1
edited by Ravi Mendis
on 2009/07/17 06:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -104,7 +104,7 @@
104 104  
105 105  Typically, in a WebObjects application, an action would return the contents of the entire page.
106 106  
107 -Ajax responses are mostly page fragments or just part of a page.
107 +Ajax responses are typically page fragments or part of a page.
108 108  So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
109 109  This breaks with WO-tradition, so this is where you need to be careful.
110 110  
... ... @@ -121,5 +121,3 @@
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##.