Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 188.1
edited by Ravi Mendis
on 2009/07/17 06:19
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.
... ... @@ -96,15 +96,15 @@
96 96  
97 97  In a typical WebObjects application, when a user clicks on the back button and clicks on a link in on that page in the browser history, WebObjects needs to remember how to handle that action and to return the correct page. This is no longer true for ajax.
98 98  The reason is a user never travels backwards or forwards through the ajax application history.
99 -(i.e there is no forward/back buttons in a 100% ajax app - as there isn't in desktop app).
99 +(i.e there is no forward/back buttons in a 100% ajax app - as there aren't in desktop apps).
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  
107 -Ajax responses are typically page fragments or part of a page.
107 +Ajax responses are mostly page fragments or just 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,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##.