Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 261.1
edited by Ravi Mendis
on 2009/07/16 09:52
Change comment: There is no comment for this version
To version 264.1
edited by Ravi Mendis
on 2009/07/17 01:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,7 @@
9 9  * 'Organic' support for Prototype and Scriptaculous in WebObjects.
10 10  * Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
11 11  * Pseudo-stateless ajax responses
12 -* No custom Prototype extensions
12 +* No custom extension or patches to Prototype
13 13  * A set of widgets in the Prototype + Scriptaculous family.
14 14  
15 15  ==== Unobtrusive Javascript in ERPrototaculous ====
... ... @@ -60,10 +60,10 @@
60 60  1. Form submits can be the form of a:
61 61  
62 62  *
63 -** Static ##<button>##
64 -** WOSubmitButton (if the result is to update whole page/app.
63 +** Static ##<button>##.
64 +** WOSubmitButton (if the result is to update whole page/app).
65 65  ** AjaxUpdaterButton (to update a **container**). Or
66 -** AjaxRequestButton (for a background ajax request)
66 +** AjaxRequestButton (for a **background** ajax request).
67 67  
68 68  == Ajax Page Caching in ERPrototaculous ==
69 69  
... ... @@ -70,7 +70,7 @@
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 72  
73 -Instead of returning a new context, an ajax update or action is in fact the same instance.
73 +Instead of returning a fresh response, an ajax update or action is in fact the same instance.
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 fresh response 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 of the update or action is all that is necessary.