AW: RFC: CForms + Dojo: the way forward

2006-10-09 Thread [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Gesendet: Freitag, 6. Oktober 2006 20:01 An: dev@cocoon.apache.org Betreff: Re: RFC: CForms + Dojo: the way forward Hi Jeremy, I see the following ways to solve this: - create a DojoReader that will dynamically compress and aggregate Javascript on the fly. - create a Maven

Re: AW: RFC: CForms + Dojo: the way forward

2006-10-09 Thread Jeremy Quinn
-Ursprüngliche Nachricht- Von: Lars Trieloff [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 6. Oktober 2006 20:01 An: dev@cocoon.apache.org Betreff: Re: RFC: CForms + Dojo: the way forward Hi Jeremy, I see the following ways to solve this: - create a DojoReader that will dynamically compress

Re: AW: RFC: CForms + Dojo: the way forward

2006-10-09 Thread Lars Trieloff
:[EMAIL PROTECTED] Gesendet: Freitag, 6. Oktober 2006 20:01 An: dev@cocoon.apache.org Betreff: Re: RFC: CForms + Dojo: the way forward Hi Jeremy, I see the following ways to solve this: - create a DojoReader that will dynamically compress and aggregate Javascript on the fly. - create a Maven Mojo

Re: RFC: CForms + Dojo: the way forward

2006-10-09 Thread hepabolu
Jeremy Quinn said the following on 6/10/06 20:47: On 6 Oct 2006, at 18:46, hepabolu wrote: Jeremy Quinn said the following on 6/10/06 16:42: Hi All We had an informal group discussion on Tuesday at the Hackathon about CForms. The purpose of the discussion was to find a consensus on the

Re: AW: RFC: CForms + Dojo: the way forward

2006-10-09 Thread Sylvain Wallez
Lars Trieloff wrote: Hi Christopher, as the individual JS files are rather small, the most costly part is requesting them from the web server, not downloading them. With an aggregated file, there is only one single request. I agree that it does not make sense to create a JS file per form

Re: RFC: CForms + Dojo: the way forward

2006-10-07 Thread Jeremy Quinn
On 6 Oct 2006, at 21:45, Jean-Baptiste Quenot wrote: Hello Jeremy, Ah, Monsieur Querty ;) This is a nice CForms roadmap indeed. See my comment below: Thanks to all those who took part . * Jeremy Quinn: 3. We have two templating systems, there are incompatibilities between them

RFC: CForms + Dojo: the way forward

2006-10-06 Thread Jeremy Quinn
Hi All We had an informal group discussion on Tuesday at the Hackathon about CForms. The purpose of the discussion was to find a consensus on the direction to take CForms, so that everybody who would like to work on it is hopefully going to take it in the same general direction. These

Re: RFC: CForms + Dojo: the way forward

2006-10-06 Thread hepabolu
Jeremy Quinn said the following on 6/10/06 16:42: Hi All We had an informal group discussion on Tuesday at the Hackathon about CForms. The purpose of the discussion was to find a consensus on the direction to take CForms, so that everybody who would like to work on it is hopefully going to

Re: RFC: CForms + Dojo: the way forward

2006-10-06 Thread Lars Trieloff
Hi Jeremy, I see the following ways to solve this: - create a DojoReader that will dynamically compress and aggregate Javascript on the fly. - create a Maven Mojo that does the same job as Dojo's ant task, but this needs to be configured at build time. The first option needs no build time

Re: RFC: CForms + Dojo: the way forward

2006-10-06 Thread Jeremy Quinn
Hi Lars On 6 Oct 2006, at 18:49, Lars Trieloff wrote: Hi Jeremy, I see the following ways to solve this: - create a DojoReader that will dynamically compress and aggregate Javascript on the fly. Amazing idea !! :) - create a Maven Mojo that does the same job as Dojo's ant task, but

Re: RFC: CForms + Dojo: the way forward

2006-10-06 Thread Jean-Baptiste Quenot
Hello Jeremy, This is a nice CForms roadmap indeed. See my comment below: * Jeremy Quinn: 3. We have two templating systems, there are incompatibilities between them and different capabilities, can we deprecate one? Conclusion: the JXMacro generation technique seems to be more