Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 204.1
edited by Ravi Mendis
on 2009/07/22 05:29
Change comment: There is no comment for this version
To version 206.1
edited by Ravi Mendis
on 2009/07/21 03:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,7 +38,7 @@
38 38  
39 39  {{code value="javascript"}}
40 40  
41 -new Ajax.Updater('container', url, {options});
41 + new Ajax.Updater('container', url, {options});
42 42  
43 43  {{/code}}
44 44  
... ... @@ -53,7 +53,7 @@
53 53  
54 54  {{code value="javascript"}}
55 55  
56 -new Ajax.Request(url, {options});
56 + new Ajax.Request(url, {options});
57 57  
58 58  {{/code}}
59 59  
... ... @@ -75,11 +75,13 @@
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 77  1. Ajax form submit buttons can be a:
78 -1*. Static ##<button>##.
79 -1*. WOSubmitButton (if the result is to update whole page/app).
80 -1*. AjaxUpdaterButton (to update a **container**). Or
81 -1*. AjaxRequestButton (for a **background** ajax request).
82 82  
79 +*
80 +** Static ##<button>##.
81 +** WOSubmitButton (if the result is to update whole page/app).
82 +** AjaxUpdaterButton (to update a **container**). Or
83 +** AjaxRequestButton (for a **background** ajax request).
84 +
83 83  So forms are different in Ajax.framework and ERPrototaculous.
84 84  
85 85  In ERPrototaculous you may still have typical WebObjects forms (i.e WOForm) as well as use ajax forms (i.e **AjaxUpdaterForm**).
... ... @@ -106,7 +106,7 @@
106 106  
107 107  {{info title="No More"}}
108 108  
109 -A 100% ajax WO-app (like an [ERDivaLook|ERDivaLook] app) is no longer be plagued by the well known _limitation_ of WebObjects - the browser *backtrack problem*.
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*.
110 110  
111 111  {{/info}}
112 112  
... ... @@ -115,7 +115,7 @@
115 115  Typically, in a WebObjects application, an action would return the contents of the entire page.
116 116  
117 117  Ajax responses are mostly page fragments or just part of a page.
118 -So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
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.
119 119  This breaks with WO-tradition, so this is where you need to be careful.
120 120  
121 121  {{note title="Note"}}