Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 115.1
edited by Ravi Mendis
on 2010/02/18 23:28
Change comment: There is no comment for this version
To version 113.1
edited by Ravi Mendis
on 2010/05/02 22:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,10 +6,10 @@
6 6  
7 7  Features include:
8 8  
9 -* 'Organic' support for Prototype and Scriptaculous in WebObjects.
9 +* 'Organic' support for [[Prototype>>http://www.prototypejs.org/]] and [[Scriptaculous>>http://script.aculo.us/]] in WebObjects.
10 10  ** Light-weight dynamic elements to support Prototype
11 -** No custom patches to Prototype
12 -** Sans extensions to Prototype
11 +** Transparent API that doesn't hide or abstract Prototype and Scriptaculous
12 +** Sans patches or extensions to Prototype
13 13  * Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]].
14 14  * Pseudo-stateless ajax responses
15 15  * A set of widgets in the Prototype + Scriptaculous family.
... ... @@ -63,7 +63,7 @@
63 63  * LightWindow
64 64  * ModalBox
65 65  * CalendarDateSelect
66 -* FileUpload
66 +* [[FileUpload>>http://valums.com/ajax-upload/]]
67 67  
68 68  Support for these widgets have been similarly implemented as **button** and **link** variants, depending whether it is used inside a form or not.
69 69  
... ... @@ -91,11 +91,17 @@
91 91  
92 92  {{/warning}}
93 93  
94 -== Ajax Response Handling in ERPrototaculous ==
94 += Embrace Statelessness! =
95 95  
96 -One notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
96 +{{include value="WO:Embrace Statelessness"}}{{/include}}
97 +
98 +ERPrototaculous embraces the stateless model Ajax offers in exchange for simplifying the work WebObjects has to do.
99 +
100 +so you may observe one notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
97 97  In ERPrototaculous, updates and actions break with //The WebObjects Way// by being pseudo-stateless.
98 98  
103 +=== Ajax Response Handling in ERPrototaculous ===
104 +
99 99  In a typical WebObjects application, when a user navigates to the previous page using the browser back button and subsequently clicks on a link in on that page, WebObjects needs to remember how to handle that action and to return the correct page. This is no longer necessary for ajax.
100 100  
101 101  A user never travels backwards or forwards through the ajax application history.
... ... @@ -115,7 +115,7 @@
115 115  
116 116  Ajax responses are mostly page fragments or just part of a page.
117 117  So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
118 -This breaks with WO-tradition (again), so this is where you need to be careful.
124 +This is different to how WebObjects normally works, so this is where you need to be careful.
119 119  
120 120  {{note title="Note"}}
121 121