Skip to Content

Changes for page ERPrototaculous

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

Summary

Details

Page properties
Content
... ... @@ -7,11 +7,9 @@
7 7  Features include:
8 8  
9 9  * 'Organic' support for Prototype and Scriptaculous in WebObjects.
10 -** Light-weight dynamic WebObjects elements to support Prototype
11 -** No custom patches to Prototype
12 -** Sans custom Prototype extensions
13 13  * Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
14 14  * Pseudo-stateless ajax responses
12 +* No custom Prototype extensions
15 15  * A set of widgets in the Prototype + Scriptaculous family.
16 16  
17 17  ==== Unobtrusive Javascript in ERPrototaculous ====
... ... @@ -62,10 +62,10 @@
62 62  1. Form submits can be the form of a:
63 63  
64 64  *
65 -** Static ##<button>##.
66 -** WOSubmitButton (if the result is to update whole page/app).
63 +** Static ##<button>##
64 +** WOSubmitButton (if the result is to update whole page/app.
67 67  ** AjaxUpdaterButton (to update a **container**). Or
68 -** AjaxRequestButton (for a **background** ajax request).
66 +** AjaxRequestButton (for a background ajax request)
69 69  
70 70  == Ajax Page Caching in ERPrototaculous ==
71 71  
... ... @@ -72,7 +72,7 @@
72 72  One notable difference in the ERPrototaculous and Ajax.framework is in the ajax responses.
73 73  ERPrototaculous updates and actions break with "The WebObjects Way" by being pseudo-stateless.
74 74  
75 -Instead of returning a fresh response, an ajax update or action is in fact the same instance.
73 +Instead of returning a new context, an ajax update or action is in fact the same instance.
76 76  
77 -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.
78 -Here the current state 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.
76 +Here the current state (or context) of the update or action is all that is necessary.