Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 157.1
edited by Ravi Mendis
on 2009/07/17 06:40
Change comment: There is no comment for this version
To version 163.1
edited by Ravi Mendis
on 2009/07/20 02:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,11 +24,11 @@
24 24  
25 25  ==== Prototype WebObjects Elements ====
26 26  
27 -##Ajax.Updater## and ##Ajax.Request## have been implemented as WebObjects dynamic elements.
27 +##Ajax.Updater## and ##Ajax.Request## have been implemented as WebObjects elements.
28 28  
29 29  ===== Ajax.Updater =====
30 30  
31 -Support for Prototype's [[Ajax.Updater>>http://www.prototypejs.org/api/ajax/updater]] is in the form of three components:
31 +Support for Prototype's [[Ajax.Updater>>http://www.prototypejs.org/api/ajax/updater]] is in the form of three elements:
32 32  
33 33  * AjaxUpdaterLink
34 34  * AjaxUpdaterButton
... ... @@ -100,6 +100,12 @@
100 100  
101 101  So for ajax, the current state of the page fragment component is all that is necessary.
102 102  
103 +{{info title="No More"}}
104 +
105 +A 100% ajax WO-app (like an ERDivaLook D2W app) will no longer be plagued by the well known _limitation_ of WebObjects - the browser *backtrack problem*.
106 +
107 +{{/info}}
108 +
103 103  == Ajax Actions in ERPrototaculous ==
104 104  
105 105  Typically, in a WebObjects application, an action would return the contents of the entire page.