Hey Shane,
yeah that's how FB was calling the fuses when it first came out. "Standard"
fusebox does this by CFINCLUDE now, since generally speaking there is little
need to use a separate memory space as a call to cfmodule (ie custom tag)
would do. There are times when you want to call a fuseaction with a custom
tag (example sometimes you are in the middle of doing something inside one
fuseaction and then want to call some fucntionality handled by another
fuseaction without cflocation-ing) . But that is on a case-by-case basis.
There is really nothing wrong with your buddy's approach. But it does
require a whole bunch more typing probably, and it has a major or minor
additional resources cost depending on what he is doing.
----- Original Message -----
From: "Shane Johnson" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Thursday, March 29, 2001 5:22 PM
Subject: Tell me what I should tell him....
> Hey all,
> I was going over a fusebox site in development with a friend and noticed
> he was doing something that I don't see done anywhere else. Rather than
> using <cfinclude> in his index.cfm he is calling his includes as custom
> tags. so <cfinclude template = "dspDoggie.cm"> becomes
<cf_dspDoggie.cfm>.
> Now this works as CF will look in the immediate directory for a tag before
> going to the custom tag directory but it just seems very wrong.
> Unfortunatley I was unable to articlate why it is wrong to do it this way.
> Can I get some logical arguments to this effect so I can get back to him
> with a logical explanation?
>
>
>
> Shane Johnson
> Coldfusion Developer
> Fusebox [XFB]
> www.strangetactics.com
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
