> XSLT is not a "config file" though. It's a Turing-complete programming > language that will let you transform one XML language to another, or to > HTML. CF will also let you do that sort of thing, and it'll generally be a > lot easier.
Indeed. On the web XSLT is great if you want to pass the XML file/data directly to the browser and have the browser render it in a certain way (using XSLT to convert the XML to HTML output). If you're running it through ColdFusion anyway, it's easier to write CF than deal with XSLT. > I wouldn't get too hung up on the idea of representing your forms as XML, > either. You can represent reusable form elements just as easily with a > relational database. I'll second that also. One project I worked on we just defined the form fields in a pipe-delimited text file that would get read and parsed into a ColdFusion application variable. Then we had a custom tag that we could call and it would generate all of the HTML for each form field in whatever "form" definition we needed. -Justin Scott ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:310311 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
