Re: RFC: Ajax Roadmap

2005-12-15 Thread Jeremy Quinn
On 14 Dec 2005, at 18:22, Sylvain Wallez wrote: Jeremy Quinn wrote: I am stuck, not able to commit at the moment, as the code in Dojo for loading javascripts in the fly, currently has fatal problems on Safari. Jerm, I'm catching up on this, and will have time to dedicate to it starting

Re: RFC: Ajax Roadmap

2005-12-14 Thread Sylvain Wallez
Antonio Gallardo wrote: Carsten Ziegeler wrote: I think this global switch is a misconception. Can we change the meaning to: "use ajax if it's enabled in the form *and* if the current browser supports it?" Currently I only have the choice for switching ajax on for *all* users. Now if they happe

Re: RFC: Ajax Roadmap

2005-12-14 Thread Sylvain Wallez
Jeremy Quinn wrote: I am stuck, not able to commit at the moment, as the code in Dojo for loading javascripts in the fly, currently has fatal problems on Safari. Jerm, I'm catching up on this, and will have time to dedicate to it starting next week. So I'd be happy to take the ball! Sylvain

Re: RFC: Ajax Roadmap

2005-12-14 Thread Jeremy Quinn
On 13 Dec 2005, at 00:54, Carsten Ziegeler wrote: Ralph Goers wrote: Jeremy Quinn wrote: Hi Ralph On 9 Dec 2005, at 15:06, Ralph Goers wrote: Jeremy Quinn wrote: The first thing I have done is to use the dojo.require mechanism to dynamically load all JS in the browser, so for instan

Re: RFC: Ajax Roadmap

2005-12-14 Thread Jeremy Quinn
On 14 Dec 2005, at 11:17, Jean-Baptiste Quenot wrote: Hello Jeremy, Thank you for taking care of integrating Dojo in Cocoon. We are very interested in that, and especially to have the suggestion list working with Dojo and CForms. Do you plan to commit your changes soon? We would be gl

Re: RFC: Ajax Roadmap

2005-12-14 Thread Jean-Baptiste Quenot
Hello Jeremy, Thank you for taking care of integrating Dojo in Cocoon. We are very interested in that, and especially to have the suggestion list working with Dojo and CForms. Do you plan to commit your changes soon? We would be glad to help if we can manage to get into it. Thanks in adv

Re: RFC: Ajax Roadmap

2005-12-12 Thread Antonio Gallardo
Carsten Ziegeler wrote: I think this global switch is a misconception. Can we change the meaning to: "use ajax if it's enabled in the form *and* if the current browser supports it?" Currently I only have the choice for switching ajax on for *all* users. Now if they happen to have turned off java

Re: RFC: Ajax Roadmap

2005-12-12 Thread Carsten Ziegeler
Carsten Ziegeler wrote: > The ajax support in the portal is currently just for the portal itself > (reloading of coplets etc.), but not for the portlets itself. (Yes, Ralf > I'm mixing coplet and portlet again - like I did in the presentation :( ) > Sorry, I misspelled your name, it should read Ra

Re: RFC: Ajax Roadmap

2005-12-12 Thread Carsten Ziegeler
Ralph Goers wrote: > Jeremy Quinn wrote: > > >>Hi Ralph >> >>On 9 Dec 2005, at 15:06, Ralph Goers wrote: >> >> >>>Jeremy Quinn wrote: >>> >>> The first thing I have done is to use the dojo.require mechanism to dynamically load all JS in the browser, so for instance, if your form

Re: RFC: Ajax Roadmap

2005-12-12 Thread Carsten Ziegeler
Jeremy Quinn wrote: > > Refactor Cocoon JS > -- > > forms-lib.js and cforms.js get merged into a new file that will > contain all (non-ajax) CForms-specific code in the following > namespace: cocoon.forms.cforms. > > Any ajax-specific code from the files above and from cocoon

Re: RFC: Ajax Roadmap

2005-12-09 Thread Ralph Goers
Jeremy Quinn wrote: Hi Ralph On 9 Dec 2005, at 15:06, Ralph Goers wrote: Jeremy Quinn wrote: The first thing I have done is to use the dojo.require mechanism to dynamically load all JS in the browser, so for instance, if your form does not use htmlarea, the javascripts are not loaded :

Re: RFC: Ajax Roadmap

2005-12-09 Thread Jeremy Quinn
Hi Antonio, On 9 Dec 2005, at 17:17, Antonio Gallardo wrote: Jeremy Quinn wrote: Hi All I am working on refactoring our CForms Ajax code to use the Dojo Ajax Library. [1] The aim of this is to reduce the amount of cocoon-specific ajax code that needs maintaining by us, to a minimum,

Re: RFC: Ajax Roadmap

2005-12-09 Thread Jeremy Quinn
Hi Ralph On 9 Dec 2005, at 15:06, Ralph Goers wrote: Jeremy Quinn wrote: The first thing I have done is to use the dojo.require mechanism to dynamically load all JS in the browser, so for instance, if your form does not use htmlarea, the javascripts are not loaded :) If there are multi

Re: RFC: Ajax Roadmap

2005-12-09 Thread Antonio Gallardo
Jeremy Quinn wrote: Hi All I am working on refactoring our CForms Ajax code to use the Dojo Ajax Library. [1] The aim of this is to reduce the amount of cocoon-specific ajax code that needs maintaining by us, to a minimum, while simultaneously adding useful new functionality. The fir

Re: RFC: Ajax Roadmap

2005-12-09 Thread Ralph Goers
Jeremy Quinn wrote: The first thing I have done is to use the dojo.require mechanism to dynamically load all JS in the browser, so for instance, if your form does not use htmlarea, the javascripts are not loaded :) If there are multiple forms on a page (i.e. in the portal) will multiple c

Re: RFC: Ajax Roadmap

2005-12-09 Thread Jeremy Quinn
On 9 Dec 2005, at 12:46, hepabolu wrote: Jeremy Quinn wrote: I am working on refactoring our CForms Ajax code to use the Dojo Ajax Library. [1] GREAT! :) The aim of this is to reduce the amount of cocoon-specific ajax code that needs maintaining by us, to a minimum, while simult

Re: RFC: Ajax Roadmap

2005-12-09 Thread hepabolu
Jeremy Quinn wrote: I am working on refactoring our CForms Ajax code to use the Dojo Ajax Library. [1] GREAT! The aim of this is to reduce the amount of cocoon-specific ajax code that needs maintaining by us, to a minimum, while simultaneously adding useful new functionality. +1, will

RFC: Ajax Roadmap

2005-12-09 Thread Jeremy Quinn
Hi All I am working on refactoring our CForms Ajax code to use the Dojo Ajax Library. [1] The aim of this is to reduce the amount of cocoon-specific ajax code that needs maintaining by us, to a minimum, while simultaneously adding useful new functionality. The first thing I have done i