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 155.1
edited by Ravi Mendis
on 2009/07/20 08:26
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
... ... @@ -87,6 +87,12 @@
87 87  In ERPrototaculous you may still have typical WebObjects forms (i.e WOForm) as well as use ajax forms (i.e **AjaxUpdaterForm**).
88 88  They behave differently in that an AjaxUpdaterForm will update the contents of a container as opposed to the entire page.
89 89  
90 +{{warning title="Warning"}}
91 +
92 +You must *name your form controls*, otherwise under certain circumstances Prototype (ajax) form submission will break.
93 +
94 +{{/warning}}
95 +
90 90  == Ajax Response Handling in ERPrototaculous ==
91 91  
92 92  One notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
... ... @@ -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  
109 +{{info title="No More"}}
110 +
111 +A 100% ajax WO-app (like an [ERDivaLook|ERDivaLook] app) will no longer be plagued by the well known _limitation_ of WebObjects - the browser *backtrack problem*.
112 +
113 +{{/info}}
114 +
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.
... ... @@ -108,7 +108,7 @@
108 108  So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
109 109  This breaks with WO-tradition, so this is where you need to be careful.
110 110  
111 -{{note title="Actions"}}
123 +{{note title="Note"}}
112 112  
113 113  ERPrototaculous actions *differ* from Ajax.framework actions - _They must return only the page fragment_.
114 114