Just to add my own 2 cents to the ever-growing list of opinions. In general, I almost never display directly from the CFC - it just hasn't felt right, however I'm working on an application now where I want it to be quick to use if you don't care too much about look and feel. The CFC has a 'render' method that allows you to use the entire functionality of it w/o wring a line of CFML. Basically I like the fact that the CFC can be used a few seconds after being installed on the system. While I wouldn't use the 'default' render for a client, for my own personal use and for quick and dirty implementations, it's perfect.
-rc > As for display methods; this was hashed out a lot way back > when CFC first appeared, I'm glad to see it hasn't become the > religious war that THIS scope has/did. But my 2 cents. I like > using CFCs for display, basically I like the idea that the > cfc knows everything about itself, have to > create,edit,delete, and display itself. Now if I need > multiple display formats (html, flash, etc) then I will put > all the display methods for one format in one cfc and extend > the base cfc with the data methods (but that's not a usual need). > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
