I always include the base fuse as well. Instead of calling another circuit,
I will usually call the "exposed" method directly.
<cfcase value="show_developer">
<cfinclude template="dsp_show_developer.cfm">
</cfcase>
<cfcase value="get_coffee">
<cfmodule template="../coffeepot/qry_remove_coffee.cfm" ounces="8">
<cfmodule template="../coffeefund/qry_add_funds.cfm" cents="10">
<cfinclude template="dsp_show_developer.cfm">
</cfcase>
You can use an approot type request var to keep up where your other circuits
are if the application is not linear.
It complicates fuses a little but it works for me.
In terms of duplicating templates and functionality, I think alot of that
goes into the modeling. I tend to reduce my circuits to the base case as to
limit my decision on where to put similar templates. I believe if you ever
have to question yourself on where to place a template then that puts up a
red flag; well, for me anyways.
<cf_remove_coffee ounces="2">
'Tis late.
Scott
----- Original Message -----
From: Kinley Pon <[EMAIL PROTECTED]>
To: Fusebox <[EMAIL PROTECTED]>
Sent: Thursday, December 07, 2000 7:11 PM
Subject: calling between circuit applications
> I am implementing a very similar fusebox structure as fusebox.org. That
is,
> EVERY fusebox, whether it is the root or circuit application, contains the
> following code:
>
> <cfinclude template="app_globals.cfm">
> <cfinclude template="app_locals.cfm">
>
> <cf_bodycontent>
> <cfparam name="attributes.fuseaction" default="">
> <cfswitch expression="#attributes.fuseaction#">
> <cfcase value="help">
> <cfinclude template="dsp_help.cfm">
> </cfcase>
> <cfdefaultcase>
> <cfinclude template="dsp_homepage.cfm">
> </cfdefaultcase>
> </cfswitch>
> </cf_bodycontent>
>
> <cfinclude template="app_layout.cfm">
>
> I came across a situation where within one circuit application directory,
I
> needed to have a fuse that actually call another fusebox of another
circuit
> application directory. For instance, I have a USER fusebox and PROJECT
> fusebox. From the PROJECT fusebox I needed a dsp_userForm.cfm which is in
> the USER fusebox. If I were to call this from within the PROJECT fusebox,
I
> would either end up struggling with the variables and/or have a
> <cf_bodycontent> nested in another <cf_bodycontent>.
>
> How can I avoid replicating the templates into another fusebox (circuit
> application)?
>
> I hope I make sense�
>
> Kinley
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
