Changes for page ERPrototaculous
Last modified by Ravi Mendis on 2010/11/18 05:07
From version 249.1
edited by Ravi Mendis
on 2009/07/16 09:03
on 2009/07/16 09:03
Change comment:
There is no comment for this version
To version 247.1
edited by Ravi Mendis
on 2009/07/16 09:47
on 2009/07/16 09:47
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -10,7 +10,7 @@ 10 10 * No custom Prototype extensions 11 11 * A set of widgets in the Prototype + Scriptaculous family. 12 12 * Use of [[Unobtrusive Javascript>>http://en.wikipedia.org/wiki/Unobtrusive_JavaScript]]. 13 -* Virtuallystateless ajax responses13 +* Pseudo-stateless ajax responses 14 14 15 15 ==== Unobtrusive Javascript in ERPrototaculous ==== 16 16 ... ... @@ -19,6 +19,29 @@ 19 19 20 20 The result is **faster** and more **reliable** ajax in WebObjects applications. 21 21 22 +==== Prototype WebObjects Elements ==== 23 + 24 +##Ajax.Updater## and ##Ajax.Request## have been implemented as WebObjects dynamic elements. 25 + 26 +===== Ajax.Updater ===== 27 + 28 +Support for Prototype's [[Ajax.Updater>>http://www.prototypejs.org/api/ajax/updater]] is in the form of three components: 29 + 30 +* AjaxUpdaterLink 31 +* AjaxUpdaterButton 32 +* AjaxUpdaterForm (with ##onsubmit## for ajax form submission) 33 + 34 +These components will update a **container** on the page. 35 + 36 +===== Ajax.Request ===== 37 + 38 +Prototype's [[Ajax.Request>>http://www.prototypejs.org/api/ajax/request]] is in the form of: 39 + 40 +* AjaxRequestLink 41 +* AjaxRequestButton 42 + 43 +These are used for strictly **background** ajax communication. 44 + 22 22 ==== Prototype + Scriptaculous Widgets ==== 23 23 24 24 * Accordion ... ... @@ -31,11 +31,23 @@ 31 31 32 32 Differences from using forms in WebObjects. i.e ##WOForm##: 33 33 34 - *All form controls must be named. This includes text fields, selects and buttons.57 +1. All form controls must be named. This includes text fields, selects and buttons. 35 35 (WebObjects dynamically assigned names are not compatible with ERPrototaculous). 36 -* All forms in an ERPrototaculous app are instances of ##AjaxUpdaterForm##. 37 -* Form submits can be the form of a: 59 +1. All forms in an ERPrototaculous app are instances of ##AjaxUpdaterForm##. 60 +1. Form submits can be the form of a: 61 + 62 +* 38 38 ** Static ##<button>## 39 39 ** WOSubmitButton (if the result is to update whole page/app. 40 40 ** AjaxUpdaterButton (to update a **container**). Or 41 41 ** AjaxRequestButton (for a background ajax request) 67 + 68 +== Page Caching Ajax in ERPrototaculous == 69 + 70 +One notable difference in the ERPrototaculous and Ajax.framework is in the ajax responses. 71 +ERPrototaculous updates and actions break with "The WebObjects Way" by being pseudo-stateless. 72 + 73 +Instead of returning a new context, an ajax update or action is in fact the same. 74 + 75 +The reason returning a new context is not necessary is because a client never travels back or forwards through an ajax application unlike in a typical WebObjects app. 76 +Here the current state (or context) of the update or action is all that is necessary.