Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 244.1
edited by Ravi Mendis
on 2009/07/16 09:50
Change comment: There is no comment for this version
To version 245.1
edited by Ravi Mendis
on 2009/07/16 09:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,10 +7,10 @@
7 7  Features include:
8 8  
9 9  * 'Organic' support for Prototype and Scriptaculous in WebObjects.
10 -* Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
11 -* Pseudo-stateless ajax responses
12 12  * No custom Prototype extensions
13 13  * A set of widgets in the Prototype + Scriptaculous family.
12 +* Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
13 +* Pseudo-stateless ajax responses
14 14  
15 15  ==== Unobtrusive Javascript in ERPrototaculous ====
16 16  
... ... @@ -65,7 +65,7 @@
65 65  ** AjaxUpdaterButton (to update a **container**). Or
66 66  ** AjaxRequestButton (for a background ajax request)
67 67  
68 -== Ajax Page Caching in ERPrototaculous ==
68 +== Page Caching Ajax in ERPrototaculous ==
69 69  
70 70  One notable difference in the ERPrototaculous and Ajax.framework is in the ajax responses.
71 71  ERPrototaculous updates and actions break with "The WebObjects Way" by being pseudo-stateless.
... ... @@ -72,5 +72,4 @@
72 72  
73 73  Instead of returning a new context, an ajax update or action is in fact the same.
74 74  
75 -The reason returning a new context is not necessary is because a client never travels back or forwards through an ajax application unlike in a typical WebObjects app.
76 -Here the current state (or context) of the update or action is all that is necessary.
75 +The reason returning a new context is not necessary is because a client never travels back or forwards through an ajax application unlike in a typical WebObjects app. Here the current state (or context) of the update or action is all that is necessary.