On Mon, 2005-10-17 at 14:01 +0200, Sylvain Wallez wrote:
Carsten Ziegeler wrote:
I briefly looked at the Ajax and the cforms block and I think there are
two problems here:
a) cforms depends on ajax block (which is ok), so why is there a
CForms: new Object(), in the cocoon-ajax.js?
Bruno Dumon wrote:
On Mon, 2005-10-17 at 14:01 +0200, Sylvain Wallez wrote:
Carsten Ziegeler wrote:
I briefly looked at the Ajax and the cforms block and I think there are
two problems here:
a) cforms depends on ajax block (which is ok), so why is there a
CForms: new Object(), in the
On 10/18/05, Sylvain Wallez [EMAIL PROTECTED] wrote:
snip/
Yes! Basically, this is a retro-factoring of the JS library to the
pre-Scriptaculous version.
I've been following your activities WRT to AJAX with some interest.
We've got our own forms and screen management system that we are also
I briefly looked at the Ajax and the cforms block and I think there are
two problems here:
a) cforms depends on ajax block (which is ok), so why is there a
CForms: new Object(), in the cocoon-ajax.js? Shouldn't the ajax block
be independent of the cforms block?
b) If you're not using ajax (for
Carsten Ziegeler wrote:
I briefly looked at the Ajax and the cforms block and I think there are
two problems here:
a) cforms depends on ajax block (which is ok), so why is there a
CForms: new Object(), in the cocoon-ajax.js? Shouldn't the ajax block
be independent of the cforms block?
b) If
Sylvain Wallez wrote:
Carsten Ziegeler wrote:
I briefly looked at the Ajax and the cforms block and I think there are
two problems here:
a) cforms depends on ajax block (which is ok), so why is there a
CForms: new Object(), in the cocoon-ajax.js? Shouldn't the ajax block
be independent of the
