On 19 Aug 2005, at 23:09, Sylvain Wallez wrote:
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 :-)
Which do you think is more appropriate? Add this this to the Wiki, or starting an AJAX block in Cocoon ?I like the idea of a Block, as someone may be more likely to improve what I have done ;)
How likely is it that others may contribute AJAX stuff ? Thanks regards Jeremy
smime.p7s
Description: S/MIME cryptographic signature
