Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 174.1
edited by Ravi Mendis
on 2009/07/17 03:41
Change comment: There is no comment for this version
To version 178.1
edited by Ravi Mendis
on 2009/07/17 04:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -73,7 +73,7 @@
73 73  
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 -1. All forms in an ERPrototaculous app are instances of ##AjaxUpdaterForm##.
76 +1. All ajax forms in an ERPrototaculous app need to be instances of ##AjaxUpdaterForm##.
77 77  1. Form submit buttons can be the form of a:
78 78  
79 79  *
... ... @@ -85,7 +85,7 @@
85 85  So forms are different in Ajax.framework and ERPrototaculous.
86 86  
87 87  In ERPrototaculous you may still have typical WebObjects forms (i.e WOForm) as well as use ajax forms (i.e **AjaxUpdaterForm**).
88 -They behave differently in that n AjaxUpdaterForm will update the contents of a container as opposed to the entire page.
88 +They behave differently in that an AjaxUpdaterForm will update the contents of a container as opposed to the entire page.
89 89  
90 90  == Ajax Page Caching in ERPrototaculous ==
91 91  
... ... @@ -120,4 +120,4 @@
120 120  
121 121  Perhaps the only real similarity to Ajax.framework is the ajax update container.
122 122  **WXGenericContainer** is the ERPrototaculous update container.
123 -It will behave like an AjaxUpdateContainer when it has the binding ##ajax = true;##, otherwise it acts like **WOGenericContainer**.
123 +It is similar to an AjaxUpdateContainer when it has the binding ##ajax = true;##, otherwise it's pretty much like **WOGenericContainer**.