I like it. -----Original Message----- From: John Farrar [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 2:57 PM To: [EMAIL PROTECTED] Subject: Re: [CFCDev] Display CFC (aka CFC for display purposes)
Here goes a bomb... you could create the logic and create a cfc that does the display and "inherits" the logic. That would allow flash to access the logic pure, and if you want to mix them and keep the seperate at the same time... that is one way to do it. (Likely someone will have a problem with it though.) DisplayMamal is a LogicMammal approach. John Farrar ----- Original Message ----- From: "Brad Howerter" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 08, 2003 4:29 PM Subject: RE: [CFCDev] Display CFC (aka CFC for display purposes) > Yep, the whole shebang, all within the same CFC. Maybe your query output > method could be called 'outputTable'. But the idea of separating the CFCs > sounds good (and then recombining them into one somehow), I just don't > understand how to do that. > > -----Original Message----- > From: Scott Keene [mailto:[EMAIL PROTECTED] > Sent: Friday, August 08, 2003 2:22 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] Display CFC (aka CFC for display purposes) > > > Before I get myself all juiced up for the soapbox - are you talking about > outputting simple string values as your example shows, or can I stretch the > theory to include complex display logic and function calls, etc? > > For example: one function does a database query, another function calls that > function and then outputs and displays the query info (including HTML, etc) > - all within the same CFC. > > Is this what you are implying? > > Scott > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Brad Howerter > Sent: Friday, August 08, 2003 12:36 PM > To: '[EMAIL PROTECTED]' > Subject: RE: [CFCDev] Display CFC (aka CFC for display purposes) > > > Your CFC will be easier to use if you have a method that does the cfoutput, > too. You can still have a method that returns a string, but go ahead and > create another method to do the cfoutput, too. Like in my example. > > <cfcomponent> > <cffunction name="OutputHelloWorld"> > <cfoutput>#helloWorld()#</cfoutput> > </cffunction> > > <cffunction name="HelloWorld"> <!--- keeping the data separate from the > display ---> > <cfreturn "Hello, World"> > </cffunction> > </cfcomponent> > ---------------------------------------------------------- > 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). > > ---------------------------------------------------------- > 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). > > ---------------------------------------------------------- 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). ---------------------------------------------------------- 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).
