Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 156.1
edited by Ravi Mendis
on 2009/07/20 08:26
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
... ... @@ -87,12 +87,6 @@
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 -
96 96  == Ajax Response Handling in ERPrototaculous ==
97 97  
98 98  One notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
... ... @@ -108,7 +108,7 @@
108 108  
109 109  {{info title="No More"}}
110 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*.
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*.
112 112  
113 113  {{/info}}
114 114  
... ... @@ -120,7 +120,7 @@
120 120  So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
121 121  This breaks with WO-tradition, so this is where you need to be careful.
122 122  
123 -{{note title="Note"}}
117 +{{note title="Actions"}}
124 124  
125 125  ERPrototaculous actions *differ* from Ajax.framework actions - _They must return only the page fragment_.
126 126