While I don't feel comfortable commenting on those other projects since I haven't used them, I do want to chime in with my views that trying to standardize on a single framework would be very helpful. I'm pretty new to Cocoon, and I spent so much time trying to digest what were the differences between xml-form, woody, and jxforms etc., and which one was really the most promising. It was VERY confusing, and almost, at times, led me back to Struts.
The Cocoon project will be best advanced with a well-defined set of components or best-practice solutions, instead of a multitude of sometimes poorly documented and fragmented choices. However, I appreciate the need to always encourage innovation, so it's a difficult tradeoff. Thanks, jeff -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Torsten Curdt Sent: Thursday, March 11, 2004 6:26 AM To: [EMAIL PROTECTED] Subject: [POLL] form frameworks Over on cocoon-dev we are in the middle of cleaning up the form framework situtation. With the upcoming 2.1.5 release "Woody" is being renamed into "CForms", "precept" is being removed and we currently considering removing "xml-form" and "jxforms" as well. So in the end we finally have a single framework :) ...but since some of you folks might be still using the deprecated packages here comes a poll: xml-form [ ] keep it as deprecated in the 2.1 branch [ ] remove it with the next 2.1.5 release [ ] remove it with the 2.1.6 release [ ] remove it only in the 2.2 branch jxforms [ ] keep it as deprecated in the 2.1 branch [ ] remove it with the next 2.1.5 release [ ] remove it with the 2.1.6 release [ ] remove it only in the 2.2 branch Thanks for your feedback -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
