This relates to the recent poll on Woody/CForms versions:
We are working on a Cocoon application that currently runs
under Cocoon 2.1.2.
Upgrading Cocoon is somewhat effort-expensive/risky for us,
because several other parties are using the same Cocoon test
server as we are. (Although we could separate them...)

Anyway, we're about to begin adding some forms to our application,
probably using Woody/CForms. I've learned that "Woody" has changed
to "CForms", but I'm told that this occurred after 2.1.4, the latest
stable release.

So... the question is, should we start implementing our forms
in Woody, possibly working with misfeatures that haven't yet
had the kinks shaken out, and knowing that we'll have to migrate
to CForms later?
Or should we start using the not-yet-stable Cocoon 2.1.5,
develop in not-yet-stable CForms, knowing we'll need to upgrade
Cocoon again when 2.1.5 stable release comes out?

I'm thinking that the former is better, since we won't have
as much of the headache of working with an unstable framework.
But I'd welcome your thoughts.

Lars



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to