Jeremy Quinn wrote:
On 19 Aug 2005, at 13:25, Sylvain Wallez wrote:
<snip/>
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.
Yes, yes, please do :-)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
