Changes for page ERPrototaculous

Summary

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

Details

Page properties

Content

...	...	@@ -96,7 +96,7 @@
96	96
97	97	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.
98	98	The reason is a user never travels backwards or forwards through the ajax application history.
99		-(i.e there is no forward/back buttons in a 100% ajax app - as there isn't in desktop app).
	99	+(i.e there is no forward/back buttons in a 100% ajax app - as there aren't in desktop apps).
100	100
101	101	So for ajax, the current state of the page fragment component is all that is necessary.
102	102
...	...	@@ -104,7 +104,7 @@
104	104
105	105	Typically, in a WebObjects application, an action would return the contents of the entire page.
106	106
107		-Ajax responses are typically page fragments or part of a page.
	107	+Ajax responses are mostly page fragments or just part of a page.
108	108	So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
109	109	This breaks with WO-tradition, so this is where you need to be careful.
110	110
...	...	@@ -121,3 +121,5 @@
121	121	Perhaps the only real similarity to Ajax.framework is the ajax update container.
122	122	**WXGenericContainer** is the ERPrototaculous update container.
123	123	It is similar to an AjaxUpdateContainer when it has the binding ##ajax = true##, otherwise it's pretty much like **WOGenericContainer**.
	124	+
	125	+It has been implemented as a utility or //convenience// for Prototype's ##Ajax.Updater##.