Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 196.1
edited by Ravi Mendis
on 2009/07/17 06:29
Change comment: Change heading name
To version 197.1
edited by Ravi Mendis
on 2009/07/17 06:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -67,14 +67,14 @@
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  
70 -== Forms in ERPrototaculous ==
70 +== Ajax Forms in ERPrototaculous ==
71 71  
72 72  Differences from using forms in WebObjects. i.e ##WOForm##:
73 73  
74 -1. All form controls must be named. This includes text fields, selects and buttons.
74 +1. All ajax 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. Ajax form submit buttons can be a:
78 78  
79 79  *
80 80  ** Static ##<button>##.
... ... @@ -100,7 +100,7 @@
100 100  
101 101  So for ajax, the current state of the page fragment component is all that is necessary.
102 102  
103 -== Actions in ERPrototaculous ==
103 +== Ajax Actions in ERPrototaculous ==
104 104  
105 105  Typically, in a WebObjects application, an action would return the contents of the entire page.
106 106