> Yes, Issac, we're working on that. For the record, it's
> not just Fusebox; it's any code that uses <cfsavecontent>.
> But we've got some ideas brewing...
Hey Hal, Yea, I know it's not _just_ fusebox... Sorry about that, I really
didn't mean it to sound antagonistic... I was just really frustrated earlier
today. :)
My first thinking on the subject was something like this:
<cfinclude template="#layoutdir#/#layoutfile#">
<cfinclude template="#circuits[fusebox.thiscircuit]#/fbx_switch.cfm">
<cfinclude template="#layoutdir#/#layoutfile#">
.. admittedly, you still have to check for the length of the layoutfile
variable and of course, redo the loops to account for nested layouts,
however, the advantage is that this would keep the layouts in a single file
( one of the big advantages to the current method over the more common
_header.cfm and _footer.cfm files I see in non-cf apps ) and all the people
who are using fb layout files currently can convert to this with a
_BARE_MINIMUM_ of effort. :)
A layout file like this:
<table ...>
<tr><td>
#fusebox.layout#
</td></tr>
</table>
Would simply become
<cfif fusebox.layoutmode is "start">
<table ...>
<tr><td>
<cfelse>
</td></tr>
</table>
</cfif>
As a matter of fact, some developers who are particularly good with regular
expressions may be able to convert layouts for an entire app with a single
multi-file REReplace in CF Studio! :)
I started looking at converting on of my own apps to use this structure, but
just didn't have the time to really disect the existing core files...
Isaac
www.turnkey.to
954-776-0046
______________________________________________________________________
Signup for the Fusion Authority news alert and keep up with the latest news in
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
