Changes for page ERPrototaculous

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -78,7 +78,7 @@
78	78	1*. Static ##<button>##.
79	79	1*. WOSubmitButton (if the result is to update whole page/app).
80	80	1*. AjaxUpdaterButton (to update a **container**). Or
81		-1*. AjaxRequestButton (for a **background** ajax submit).
	81	+1*. AjaxRequestButton (for a **background** ajax request).
82	82
83	83	So forms are different in Ajax.framework and ERPrototaculous.
84	84
...	...	@@ -96,10 +96,11 @@
96	96	One notable difference between the ERPrototaculous and Ajax frameworks is in the way they handle ajax responses.
97	97	In ERPrototaculous, updates and actions break with //The WebObjects Way// by being pseudo-stateless.
98	98
99		-In a typical WebObjects application, when a user navigates to the previous page using the browser back button and subsequently clicks on a link in on that page, WebObjects needs to remember how to handle that action and to return the correct page. This is no longer necessary for ajax.
	99	+WebObjects typically vends a fresh response for each and every action. With ajax, this is not necessary.
100	100
101		-A user never travels backwards or forwards through the ajax application history.
102		-(i.e there is no forward/back buttons for ajax requests - just as there aren't forward/back buttons on desktop apps).
	101	+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.
	102	+The reason is a user never travels backwards or forwards through the ajax application history.
	103	+(i.e there is no forward/back buttons in a 100% ajax app - as there aren't in desktop apps).
103	103
104	104	So for ajax, the current state of the page fragment component is all that is necessary.
105	105
...	...	@@ -115,7 +115,7 @@
115	115
116	116	Ajax responses are mostly page fragments or just part of a page.
117	117	So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
118		-This breaks with WO-tradition (again), so this is where you need to be careful.
	119	+This breaks with WO-tradition, so this is where you need to be careful.
119	119
120	120	{{note title="Note"}}
121	121