Changes for page ERPrototaculous
Last modified by Ravi Mendis on 2010/11/18 05:07
From version 248.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
To 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
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 -* Pseudo-stateless ajax responses13 +* Virtually stateless ajax responses 14 14 15 15 ==== Unobtrusive Javascript in ERPrototaculous ==== 16 16 ... ... @@ -19,29 +19,6 @@ 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 - 45 45 ==== Prototype + Scriptaculous Widgets ==== 46 46 47 47 * Accordion ... ... @@ -54,23 +54,11 @@ 54 54 55 55 Differences from using forms in WebObjects. i.e ##WOForm##: 56 56 57 - 1.All form controls must be named. This includes text fields, selects and buttons.34 +* All form controls must be named. This includes text fields, selects and buttons. 58 58 (WebObjects dynamically assigned names are not compatible with ERPrototaculous). 59 -1. All forms in an ERPrototaculous app are instances of ##AjaxUpdaterForm##. 60 -1. Form submits can be the form of a: 61 - 62 -* 36 +* All forms in an ERPrototaculous app are instances of ##AjaxUpdaterForm##. 37 +* Form submits can be the form of a: 63 63 ** Static ##<button>## 64 64 ** WOSubmitButton (if the result is to update whole page/app. 65 65 ** AjaxUpdaterButton (to update a **container**). Or 66 66 ** 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.