Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 277.1
edited by Ravi Mendis
on 2009/07/17 01:35
Change comment: Add note on actions
To version 273.1
edited by Ravi Mendis
on 2009/07/17 01:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,7 @@
7 7  Features include:
8 8  
9 9  * 'Organic' support for Prototype and Scriptaculous in WebObjects.
10 -** Light-weight dynamic elements to support Prototype
10 +** Light-weight dynamic WebObjects elements to support Prototype
11 11  ** No custom patches to Prototype
12 12  ** Sans the need to extend Prototype
13 13  * Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
... ... @@ -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.