since he was using frames in his demo he obviously does not need to use
bodycontent in the same way a non-framed app would...but yes, this is
exactly how I do mine for what it is worth...though I need to go get your
tags so I can see how you have adpated xfb with your cf_xfb tag and the
myaction value (sorry Lee, just have not had the time to look at it yet...I
flog myself repeatedly).
Mike Craig
-----Original Message-----
From: lee borkman [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 07, 2001 7:00 PM
To: Fusebox
Subject: XFB and CF_BodyContent
Hi all,
On the topic of the standard FuseBox tags, I wonder are any of you XFB
junkies out there using CF_BodyContent, or do you have some other incredibly
clever way to do all of those cool things?
My XFB fusebox look like this:
<CFINCLUDE template="myGlobals.cfm">
<CF_XFB LOCATION="#getcurrenttemplatepath()#">
<cfif NOT XFB.myaction>
<cfinclude template="#XFB.nextcircuit#">
<cfelse>
<CF_BODYCONTENT>
<cfswitch expression = "#attributes.fuseaction#">
<cfcase value=...>
...
</cfcase>
<cfdefaultcase>
<CF_UnknownFuseAction>
</cfdefaultcase>
</cfswitch>
</CF_BODYCONTENT>
</cfif>
Is there some better way to do this? Frankly, I'm surprised that Hal's
demos don't use CF_BodyContent, which I consider to be the most amazingly
useful of all FuseBox tags. What does he know that I don't? ;-)
Thanks heaps,
Lee Bjork Borkman
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
