Barney and Michael both make excellent points regarding the layouts and
use of CCV's.

I also migrated from fb3, and although most of the time I do things much
the way barney illustrated, its important to note the flexibility that
they built into fb4.

For instance a well know fact of fb3 was taht you could not use nested
layouts and still have use of cfflush for incremental page output.  With
fb4 you can still utilize nested layouts and take advantage of cfflush.  
This is possible by the use of the prefuseaction and postfusaction at
the circuit level.  Breaking your display into before and after
(header/footer) fragments you can have the layout build top down, then
build your incremental output then add the footer.

It was challenging to switch up to fb4 because the methodology allows
for alot of customization.  Which without proper planning can be more of
a pain than a blessing.

I am sure that I missed something here, but I just wanted to round out
the other side of the feature set, and make sure you understand why they
changed that feature set.

simeon

Barney Boisvert wrote:

> If you're using an MVC setup, then it's fairly trivial to set up.  In your
> 'controller' fuseactions, whenever you call a 'view' fuseaction, use a
> contentVariable to capture the content.  Then, use a layout file to render
> that contentVariable into your generic layout code.
>
> <circuit access="public">
>   <fuseaction name="home">
>     <do action="" />
>     <do action="" />
>     <do action="" contentVariable="layout" />
>   </fuseaction>
>
>   <postfuseaction>
>     <do action="" />
>   </postfuseaction>
> </circuit>
>
> That will give you per-circuit layouts.  Note, however, that circuits
> don't
> cascade in FB4 the same way they do in FB3, so if you want nested layouts,
> you'll need to take care of that.
>
> I prefer layout fuseaction called from the global postfuseaction
> section of
> fusebox.xml which lays out my page.  In other words, I don't use any
> nesting, nor circuit-specific layouts.  If I need a couple different
> layouts
> (with/without navigation, for example), then I set a request-scope
> variable
> in the given fuseaction that is checked in the layout fuseaction, which
> controls which specific layout is used.
>
> Cheers,
> barneyb
>
> > -----Original Message-----
> > From: Phill B [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 12, 2004 10:36 AM
> > To: CF-Talk
> > Subject: FB4 and layouts
> >
> > I use FB3 and trying to learn FB4. I like the way I could use layout
> > files in FB3 but I'm not sure of the best way to do it in FB4.
> >
> > Any suggestions?
> >
> > --
> > Phillip B.
> >
> >
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to