On 19 Aug 2005, at 13:25, Sylvain Wallez wrote:
Ugo Cei wrote:Il giorno 19/ago/05, alle 11:34, Sylvain Wallez ha scritto:http://www.orbeon.com/blog/2005/08/16/ops-stack-traces/Yeah, but their new "ajaxified" XForms engine looks cool.What do you find particularily cool? Except the eye-candy when focus enters a list, I wasn't impressed. I was also surprised to see that almost every user action triggers a roundtrip to the server (the "Loading" spinning wheel), which puts a useless load on the server, especially on large forms where the user may tab quickly to navigate inputs.At least, the demos do. I'm wondering whether we could reuse something for CForms.The icons and the CSS?I also started looking at integrating Scriptaculous [1] and Rico's LiveGrid [2] in Cocoon, but as always it requires to dedicate time, i.e. finding a project that needs it.Scriptaculous is RoR's Ajax library and it uses a very similar approach to CForms, by sending HTML snippets for partial page updates rather than requiring large amounts of client-side application-specific logic.Actually, Ajax in Cocoon should be separated from CForms, and this is why the BrowserUpdateTransformer is in core and not in CForms. Now if we're to add more Ajax-related stuff in Cocoon, I'm not sure putting it in the core is a good thing, and a separate Ajax block may be better.
I already have a desire to separate the BrowserUpdate and DOMUtils JavaScript Objects out of cforms.js, as I am using them outside the context of CForms.
I can add (either to the wiki, or as a sample in a new AJAX Block) a JX Macro and JS file (TimedBrowserUpdate) that allow you to have regions of your page update in the background using BrowserUpdate on a periodic basis, if there are changes in the underlying data. We are using it to update the user on the status of asynchronous processes.
regards Jeremy
smime.p7s
Description: S/MIME cryptographic signature
