Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 278.1
edited by Ravi Mendis
on 2009/07/17 01:35
Change comment: Add note on actions
To version 279.1
edited by Ravi Mendis
on 2009/07/16 10:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,20 +7,17 @@
7 7  Features include:
8 8  
9 9  * 'Organic' support for Prototype and Scriptaculous in WebObjects.
10 -** Light-weight dynamic elements to support Prototype
11 -** No custom patches to Prototype
12 -** Sans the need to extend Prototype
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 ====
18 18  
19 19  Unobtrusive javascript is used in contrast to on-demand style of ajax programming.
20 -By including Javascript as well as CSS globally in the page wrapper, CSS and Javascript don't have to load inside each and every ajax requests.
21 -This keeps the ajax responses compact and granular.
18 +By including Javascript as well as CSS globally in the page wrapper, CSS and/or Javascript doesn't have to load inside ajax requests.
22 22  
23 -The result is **faster** and more **reliable** ajax in WebObjects.
20 +The result is **faster** and more **reliable** ajax in WebObjects applications.
24 24  
25 25  ==== Prototype WebObjects Elements ====
26 26  
... ... @@ -63,10 +63,10 @@
63 63  1. Form submits can be the form of a:
64 64  
65 65  *
66 -** Static ##<button>##.
67 -** WOSubmitButton (if the result is to update whole page/app).
63 +** Static ##<button>##
64 +** WOSubmitButton (if the result is to update whole page/app.
68 68  ** AjaxUpdaterButton (to update a **container**). Or
69 -** AjaxRequestButton (for a **background** ajax request).
66 +** AjaxRequestButton (for a background ajax request)
70 70  
71 71  == Ajax Page Caching in ERPrototaculous ==
72 72  
... ... @@ -77,10 +77,3 @@
77 77  
78 78  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.
79 79  Here the current state of the update or action is all that is necessary.
80 -
81 -== Actions in ERPrototaculous ==
82 -
83 -Typically, in a WebObjects application, an action would return the contents of the entire page.
84 -
85 -Ajax responses are typically page fragments or part of a page.
86 -So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page. This breaks with WO-tradition, so this is where you need to turn your attention to.