My person feeling is there's a lot lacking from CFFORM's js. Although you can customize the code, it's still fairly inflexible. Check out qForms:
http://www.pengoworks.com/qforms/ I started writing the API a few years ago to overcome some of the issues I had w/CFFORM's JS implementation. It's a lot more expandable and has built in methods for doing just about everything you'll need to do. (And if there's something missing it's *very* easy to add the functionality.) To my knowledge there's not another JavaScript-based form API that's even half as complete or flexible. -Dan > -----Original Message----- > From: G L [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, August 13, 2002 11:53 AM > To: CF-Talk > Subject: CFFORM/CFINPUT > > Can someone explain to me why alot of advanced CF'ers don't like to use > CFFORM and CFINPUTs in their code? I've even heard them refer to it as > "novice cf-coding". I've always had good luck using them. Are there > drawbacks to letting CF generate the js to validate your input fields? > There > must be a good reason. > > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
