Sylvain Wallez wrote:
I personally don't use v2 nor v3. People using it are invited to speak up!
You answered the question in your summary of the last year GT Hackathon
discussion about cforms
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=109774752401800w=2) yourself:
[...]
- don't use
Hi, i've just finished quite a large cocoon site using 2.1.7 with
Forms V3. We choose this version for two reasons:
1. At the time i couldnt find much info on the different versions or
why they were there so assumed V3 meant it was more mature and the
latest.
2. showForm() in V3 offers the
Paul Crabtree wrote:
Hi, i've just finished quite a large cocoon site using 2.1.7 with
Forms V3. We choose this version for two reasons:
1. At the time i couldnt find much info on the different versions or
why they were there so assumed V3 meant it was more mature and the
latest.
Well,
Reinhard Poetz wrote:
Sylvain Wallez wrote:
I personally don't use v2 nor v3. People using it are invited to
speak up!
You answered the question in your summary of the last year GT
Hackathon discussion about cforms
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=109774752401800w=2)
Sylvain Wallez wrote:
Paul Crabtree wrote:
Hi, i've just finished quite a large cocoon site using 2.1.7 with
Forms V3. We choose this version for two reasons:
1. At the time i couldnt find much info on the different versions or
why they were there so assumed V3 meant it was more mature and
Sylvain Wallez wrote:
Ralph Goers wrote:
snip/
The bottom line is you cannot have code sitting around forever telling
people its great but you have to use it at your own risk cause we
might change it anytime we feel like it. This has just been going on
for far too long. The code is never
-Oorspronkelijk bericht-
Van: Leszek Gawron [mailto:[EMAIL PROTECTED]
5 - flatten the configuration to allow for easier extension with the
xconf include mechanism in 2.2
I could give it a shot but I have no deeper knowledge of cocoon.xconf
syntax in this case. Do we have to
Leszek Gawron wrote:
Sylvain Wallez wrote:
The main points to achieve stable state are:
1 - remove v2 and v3 apis
I assume there are some features that we would like to port back to
v1. Could we identify them?
I personally don't use v2 nor v3. People using it are invited to speak up!
Sylvain Wallez wrote:
I could give it a shot but I have no deeper knowledge of cocoon.xconf
syntax in this case. Do we have to make every widget a component? That
doesn't feel right.
Nono, what I'm talking about is the various subcontainers that exist in
CForms, such as forms-datatypes
On Jun 9, 2005, at 1:48 AM, Sylvain Wallez wrote:
I personally don't use v2 nor v3. People using it are invited to speak
up!
I have a few Cocoon projects, and I use v2 in all but one of them (the
oldest one)!
cheers, :-)
ml
Mark Lundquist wrote:
On Jun 9, 2005, at 1:48 AM, Sylvain Wallez wrote:
I personally don't use v2 nor v3. People using it are invited to speak
up!
I have a few Cocoon projects, and I use v2 in all but one of them (the
oldest one)!
Can you give a short explanation on the reasons for
11 matches
Mail list logo
