Skip to Content

Changes for page ERPrototaculous

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

Summary

Details

Page properties
Content
... ... @@ -74,7 +74,7 @@
74 74  1. All form controls must be named. This includes text fields, selects and buttons.
75 75  (WebObjects dynamically assigned names are not compatible with ERPrototaculous).
76 76  1. All ajax forms in an ERPrototaculous app need to be instances of ##AjaxUpdaterForm##.
77 -1. Form submit buttons can be a:
77 +1. Form submit buttons can be the form of a:
78 78  
79 79  *
80 80  ** Static ##<button>##.
... ... @@ -89,7 +89,7 @@
89 89  
90 90  == Ajax Page Caching in ERPrototaculous ==
91 91  
92 -One notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
92 +One notable difference in the ERPrototaculous and Ajax.framework is in the ajax responses.
93 93  In ERPrototaculous, updates and actions break with "The WebObjects Way" by being pseudo-stateless.
94 94  
95 95  WebObjects typically vends a fresh response for each and every action. With ajax, this is not necessary.
... ... @@ -96,7 +96,7 @@
96 96  
97 97  In a typical WebObjects application, when a user clicks on the back button and clicks on a link in on that page in the browser history, WebObjects needs to remember how to handle that action and to return the correct page. This is no longer true for ajax.
98 98  The reason is a user never travels backwards or forwards through the ajax application history.
99 -(i.e there is no forward/back buttons in a 100% ajax app - as there aren't in desktop apps).
99 +(i.e there is no forward/back buttons in a 100% ajax app - as there isn't in desktop app).
100 100  
101 101  So for ajax, the current state of the page fragment component is all that is necessary.
102 102