Personally, I don't think the "best practice" is necessarily "don't use HTML in a CFC" as much as "don't mix HTML presentation with business logic in a single CFC" -- it makes sense in my mind (and keep in mind I'm no OO guru by any stretch) that you would have a "layer" of CFCs that render things on the page -- these would take as arguments data structures produced by your business logic CFCs and/or instances of the "objects" you want to render.
At Nat pointed out, the original prototype for Modus had "fat" content object, that knew how to do everything, but it was decided that was not the optimal way to proceed -- instead, it was decided to break it up into "services" that handle the various aspects and make "thin" content objects that are really just the necessary data. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Scott Barnes > Sent: Wednesday, March 19, 2003 2:35 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] Is anyone out there using cfc for GUI elements? > > > I was thinking on this last night, and although I too have lived > by the "Keeping of CFC's purity" rule, i personally don't see the > drawbacks in using it on the presentation layer side of things? [snip] ---------------------------------------------------------- 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).
