I do something like this, but its within the same fusebox application, I do
it mainly for organization of my fuseactions, if I have a bunch of
fuseactions that add records to the datasource I don't want a lot of single
fuseactions scattered all over the place within the index.cfm where I have
to scan through 50 of them to find the one I want. so I have it like so.
<cfswitch expresion="#listfirst(attributes.fuseaction,'.')#">
<cfcase value="add">
<cfswitch expression="#listlast(attributes.fuseaction,'.')#">
<cfcase value="user">
..... code here (includes, modules, whatever)
</cfcase>
....... Blah Blah Blah
</cfswitch>
</cfcase>
....... Blah Blah Blah
</cfswitch>
It works well for me, its more for organizational purposes than anything
else, but there's been times when I wanted to add code to all related fuses
at the same time (i.e. a tag we wrote to log what was done in by the user.)
that all I needed to do was add it after the nested switch statement, and
not to each fuseaction singlely.
Fred
----- Original Message -----
From: "Patrick McElhaney" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 8:42 AM
Subject: A Kinder, Gentler Nesting Suggestion
> Has anyone ever considered making the name of a circuit
> dynamic, and letting the home app call it by whatever
> name it wants to?
>
> <cfset myName = listFirst(request.rawfuseaction, ".")>
>
> ....
>
> <cfset xfa.somethingOrOther = "#myName#.doSomething>
>
> Patrick
>
>
> ----------------------------------
> Patrick McElhaney
> Application Developer
> American City Business Journals
> 704-973-1019 704-236-8351 (cell)
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
