That was my thought too but I figured there must be something snazzy about
how the new file worked if they were being combined in some way.
Ken
> Why would you want to have app_layout included in CF_BodyContent?
> CF_BodyContent should be the same fort everyone; but app_layout is where
YOU
> get to layout YOUR site. Where do you want to put your:
> header
> footer
> body
> main nav
> secondary nav
> logo
>
> ??
>
> Now possibly a default layout that can be overridden might be okay, but
that
> just makes life that little bit harder.
>
> Or, once again, am I missing the point completely?
>
> LBB.
>
>
> -----Original Message-----
> From: Ken Wilson [mailto:[EMAIL PROTECTED]]
>
>
> I finally got around to reading some most of the FuseBox book this week
and
> noticed that it mentions a new version CF_BodyContent that has the
> app_layout.cfm code included in it...no need to cfinclude it seperately.
The
> tag on the FuseBox site is apparently the old version. Anyone know where
to
> get the new one mentioned in the book?
>
>
>
> IMPORTANT NOTICE:
> This e-mail and any attachment to it is intended only to be read or used
by
> the named addressee. It is confidential and may contain legally
privileged
> information. No confidentiality or privilege is waived or lost by any
> mistaken transmission to you. If you receive this e-mail in error, please
> immediately delete it from your system and notify the sender. You must
not
> disclose, copy or use any part of this e-mail if you are not the intended
> recipient. The RTA is not responsible for any unauthorised alterations to
> this e-mail or attachment to it.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
