Sounds like you're using tables, so try this:
Header opens table fills first row (top frame) and a new row with the first
column holding the left menu,
Then the body is displayed in the middle column.
The footer adds a right nav menu in the third column.
And another row (bottom frame)

TTTTTTTTTTTT
L MMMMMMMR
L MMMMMMMR
L MMMMMMMR
L MMMMMMMR
BBBBBBBBBBB

And so in the fuses you set attributes variables to modify the way the
header and footer display their menus later.
 
HTH,
Noam

        ----------
        From:  Peter Terhorst [SMTP:[EMAIL PROTECTED]]
        Sent:  Friday, 22 September 2000 4:47
        To:  Fusebox
        Subject:  RE: Explain CF_BodyContent

        I got that much of it... and what's more, it appears that whatever
code is
        invoked within the <cf_bodycontent> tags can modify the variables
that hold
        the header and footer, thus being able to drive their content on a
        page-by-page basis.... cool enough.

        But here's a reach I was wondering if this tag was good for >>  I
have a
        frame-like page that has varying "main" content that needs to drive
the
        content of the surrounding navigational structure.  I have left side
navs
        and top navs that need to get created, based upon what the main part
of the
        page does...its not framed, the page is just built in a frame-like
style.
        The <cf_bodycontent> tag seems to do this type of thing for us, but
only for
        the header and footer of a page...

        can the so-called "header" be more than just a header for the page?
Can it
        be a definition for what all of the page, except the main body part
looks
        like?  I want to invoke that content in just the same way.

        pts

        ~~ -----Original Message-----
        ~~ From: BORKMAN Lee [mailto:[EMAIL PROTECTED]]
        ~~ Sent: Thursday, September 21, 2000 2:25 PM
        ~~ To: Fusebox
        ~~ Subject: RE: Explain CF_BodyContent
        ~~
        ~~
        ~~ Hi all,
        ~~
        ~~ I'm just new to CF_BodyContent, but it's working beautifully.
        ~~
        ~~ Fist of all, grab the source for the entire fusebox.org site from
        ~~ fusebox.org.  It is a perfect example/skeleton to start with.
        ~~
        ~~ Basically, there are two important files working together,
CF_BodyContent
        ~~ and app_layout.cfm (both supplied with CF_BodyContent). They get
        ~~ called like
        ~~ this in your FuseBox (index.cfm):
        ~~
        ~~
        ~~ <cf_bodycontent>
        ~~      <cfparam name="attributes.fuseaction" default="menu">
        ~~
        ~~      <!--- Handle FuseActions --->
        ~~      <cfswitch expression="#attributes.fuseaction#">
        ~~
        ~~              <CFCASE VALUE="menu">
        ~~                      <CFSET request.title="Menu Page">
        ~~                      blah
        ~~                      blah
        ~~                      blah
        ~~              </CFCASE>
        ~~
        ~~      </cfswitch>
        ~~ </cf_bodycontent>
        ~~
        ~~ <!--- Display the page --->
        ~~ <cfinclude template="app_layout.cfm">
        ~~
        ~~
        ~~ The CF_BodyContent builds a variable called BodyContent, BUT
        ~~ DOESN'T DISPLAY
        ~~ ANYTHING.  app_layout THEN displays Header, BodyContent, and
Footer.  The
        ~~ cool thing is that the logic in your body has ALREADY been
        ~~ executed, BEFORE
        ~~ you display your Header.  That allows the logic in your body (in
your
        ~~ FuseAction, for example) to affect the display of the Header.
        ~~ In this case,
        ~~ my Menu FuseAction sets a variable (request.title). If my Header
file
        ~~ references that variable (it does!), then the Title displayed in
        ~~ my Header
        ~~ can be set by my Body logic.
        ~~
        ~~ Does that make sense?
        ~~
        ~~ Let me know if I have it all wrong ;-)
        ~~
        ~~ Lee (Bjork) Borkman
        ~~ http://bjork.net ColdFusion Tags by Bjork
        ~~
        ~~
        ~~
        ~~ -----Original Message-----
        ~~ From: Chris Lott [mailto:[EMAIL PROTECTED]]
        ~~ Sent: Friday, September 22, 2000 2:44 AM
        ~~ To: Fusebox
        ~~ Subject: Re: Explain CF_BodyContent
        ~~
        ~~
        ~~ -----BEGIN PGP SIGNED MESSAGE-----
        ~~ Hash: SHA1
        ~~
        ~~ Please explain on the list! Among other things, this is a tag I
am
        ~~ not yet using because I STILL don't get it!
        ~~
        ~~ c
        ~~ - --
        ~~ Chris Lott
        ~~
        ~~ -----BEGIN PGP SIGNATURE-----
        ~~ Version: PGP 6.5.8 for message encryption and authentication: USE
PGP!
        ~~ Comment: PGP KeyID: 0x51046CFD
        ~~
        ~~ iQA/AwUBOcos1daLYehRBGz9EQIWIQCg6zabtBhIU6NPqPTSz/HbYBFM5gEAoOXG
        ~~ O6l6K2EDTiwGq3zF4tB3gCUV
        ~~ =P3Ks
        ~~ -----END PGP SIGNATURE-----
        ~~
        ~~
        ~~ -----------------------------------------------------------------
        ~~ -----------
        ~~ --
        ~~ To Unsubscribe visit
        ~~ http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/f
        usebox or
        send a message to [EMAIL PROTECTED] with
'unsubscribe' in
        the body.
        
----------------------------------------------------------------------------
        --
        To Unsubscribe visit
        
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
        send a message to [EMAIL PROTECTED] with
'unsubscribe' in
        the body.

        
----------------------------------------------------------------------------
--
        To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to