Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 321.1
edited by Ravi Mendis
on 2023/11/13 11:57
Change comment: Renamed back-links.
To version 319.1
edited by Ravi Mendis
on 2010/11/18 05:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -Frameworks
Tags
... ... @@ -1,1 +1,0 @@
1 -webobjects|wonder|scriptaculous|ajax|prototype
Content
... ... @@ -16,10 +16,8 @@
16 16  
17 17  ==== Unobtrusive Javascript in ERPrototaculous ====
18 18  
19 -[[doc:WO.Using Unobtrusive JavaScript]]
19 +{{include 0="WO:Using Unobtrusive JavaScript"/}}
20 20  
21 -{{include/}}
22 -
23 23  {{code}}
24 24  
25 25  er.prototaculous.useUnobtrusively = true
... ... @@ -96,10 +96,8 @@
96 96  
97 97  = Embrace Statelessness! =
98 98  
99 -[[doc:WO.Embrace Statelessness]]
97 +{{include 0="WO:Embrace Statelessness"/}}
100 100  
101 -{{include/}}
102 -
103 103  ERPrototaculous embraces the stateless model Ajax offers in exchange for simplifying the work WebObjects has to do - it's a win-win!
104 104  
105 105  So you may observe one notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
... ... @@ -115,7 +115,7 @@
115 115  So for ajax, the current state of the page fragment component is all that is necessary.
116 116  
117 117  {{info title="No More ~"You backtracked too far~""}}
118 -A 100% ajax WO-app (like an [[ERDivaLook>>doc:documentation.Home.Frameworks.ERDivaLook.WebHome]] app) is no longer plagued by the well known //limitation// of WebObjects - the browser **backtrack problem**.
114 +A 100% ajax WO-app (like an [[ERDivaLook>>doc:ERDivaLook]] app) is no longer plagued by the well known //limitation// of WebObjects - the browser **backtrack problem**.
119 119  {{/info}}
120 120  
121 121  == Ajax Actions in ERPrototaculous ==