I suppose this depends on your enviroment. On a hosted site, they are
seldom going to let you put custom tags in the C:\CFusion\CustomTags
directory. If you have control of the enviroment, then I would say yes put
your custom tags in that directory.
If it is your development server, just make sure you set up your advanced
security appropriately so that not everyone RDS'ing in has access to your
custom tags. Also, I would make a backup folder of custom tags on some
media device like a CD or jaz drive so some discrunted employee doesn't wipe
out your custom tags.
I seldom CFMODULE any more most often I use the shorthand version <CF_
What I meant by it depends on how you call your custom tags is this. Every
application I build has a custom tag called act_html_tags.cfm. This tag
simply puts in all the html tags I hate to write over and over. Every web
app I build might have different stylesheets, so for this specific tag I do
not put it in the C:\CFusion\CustomTags directory, but rather in the web's
root directory. And if a web app itself has different stylesheets for child
apps, I make a switch in act_html_tags.cfm based on the fusaction and I
would use CFASSOCIATE in the parent switch's "end" case to add any links
that would go in the footer of the app.
CF looks first to the template's local directory, then the web root
directory then the C:\CFusion\CustomTags directory. Someone correct me if I
am wrong, but I think that is the order
I call act_html_tags.cfm like this...
<cf_act_htmltags>
<cfinclude template="dsp_admin_cat_select_cat.cfm">
</cf_act_htmltags>
----act_html_tags----
<cfparam name="caller.title" default="My Website">
<cfswitch expression="#thistag.executionmode#">
<cfcase value="start">
<html>
<head>
<title><cfoutput>#caller.title#</cfoutput></title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">
body { font-family: arial, verdana, helvetica; color: #434343;
text-decoration: none; font=11;}
td { font-family: arial, verdana, helvetica; color: #434343;
text-decoration: none; font=11;}
td.msg { font-family: verdana, arial, helvetica; color: #327e98;
text-decoration: none; font=14;}
th { font-family: verdana, arial, helvetica; color: #737373;
text-decoration: bold; font=11;}
a { font-family: verdana, arial, helvetica; color: #330099;
text-decoration: underline; cursor: hand; font=11;}
a:hover { font-family: verdana, arial, helvetica; color: #DE8C12;
text-decoration: underline; cursor: hand; font=11;}
p { font-family: arial, verdana, helvetica; color: #434343;
text-decoration: none; font=11;}
</style>
</head>
<body bgcolor="#ffffff">
</cfcase>
<cfcase value="end">
</body>
</html>
</cfcase>
</cfswitch>
----- Original Message -----
From: "Daye, Marianne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 21, 2000 4:38 AM
Subject: RE: FuseBox Confusion
> Sean,
>
> Thanks for your thorough response. I was starting to give up hope!
>
> On the second question regarding the location of the tag, could I ask you
to
> elaborate just a little. I'm assuming you would always call a custom tag
> with CFMODULE. Having common modules located within various applications
> instead of one central location just seems slightly unsystematic to me.
For
> instance, let's say I have two applications that both call on the same
> module (circuit app/fusebox), and the module is equally important to both
> applications. If I move the application with the common module to a
> different server, I'll have to update the other site. If the module was
in
> a central location, it wouldn't be going anywhere, and nothing needs to be
> updated. Am I missing something?
>
> Thanks!
>
> Marianne
>
> -----Original Message-----
> From: Sean Renet [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 20, 2000 7:24 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: FuseBox Confusion
>
>
> > 1. If you choose to call a circuit application as a tag, is it only the
> > index.cfm file that has to be called using CFMODULE?
>
> yes just make sure to include your attributes. for the circut app
>
> > 2. If a circuit application is called as a custom tag by multiple
> > applications, shouldn't it be located in the C:\CFusion\CustomTags
> directory
> > on the server?
>
> This depends on how you are calling the circuit app.
>
> > 3. I understand that you can pass a fuesaction value of 'blank',
'form',
> or
> > 'query' to use the same form three different times. If you use this
> > technique with a circuit application that has more than one form, how
does
> > the index file know which form to include?
>
> well if the forms are completely different, like one form is shipping
> choices and the other is recipient info, I would have a different case in
my
> switch for both. However, if the forms are similar but one fuseaction
> doesn't use elements that the other does, I would build if statements into
> the form based on the fuseaction. For instance, I have a search engine
that
> includes radio buttons for types of search. This file is included with
> every child app in my parent administration app. However, lets say you
> can't search employees by topic(which is search used for research
articles),
> I have an if statement around that that radio button so that it is only
> included if it is necessary. Hal as come up with a technique called pfa's
or
> something, I simply call them subfuses
>
> > 4. According to advanced technique # 5, when the child application
> > (dual-page tag object) sends the information for the first page to the
> > second page, it will call the parent application, which will call the
> child
> > application (second page, I presume). How is this done? Does anyone
have
> > an example.
> This is a current conversation on this board. I like my way, Hal, et al,
> are figuring out a less readable way that I am not so fond of. The
readable
> way is...
>
> <cfswitch expression="#attributes.fuseaction#">
> ---child app ----
> <cfcase value="orm,ormlogin,ormfulfill,ormcomplete,ormrefuse"
> delimiters=",">
> <cf_act_htmltags>
> <cfinclude template="orm/index.cfm">
> </cf_act_htmltags>
> </cfcase>
>
> ....a bunch of other cases.....
>
> ---case for left nav in frames---
> <CFCASE VALUE="navside">
> <cf_act_htmltags>
> <cfinclude template="dsp_nav_side.cfm">
> </cf_act_htmltags>
> </CFCASE>
> ---case for splash page in frames---
> <CFCASE VALUE="slashlogin">
> <cf_act_htmltags>
> <cfinclude template="dsp_admin_login.cfm">
> </cf_act_htmltags>
> </CFCASE>
> ---home---
> <CFDEFAULTCASE>
> <cf_act_htmltags_frames>
> <frameset rows="137,*" border="0" frameborder="no" framespacing="0">
> <frame name="header" src="index.cfm?fuseaction=navglobal"
> marginwidth="0" marginheight="0" scrolling="no" frameborder="0" noresize>
> <frameset cols="150,*">
> <frame name="nav" src="index.cfm?fuseaction=navside"
> marginwidth="0" marginheight="0" scrolling="no" frameborder="0" noresize>
> <frame name="main" src="index.cfm?fuseaction=slashlogin"
> marginwidth="2" marginheight="2" scrolling="auto" frameborder="0"
noresize>
> </frameset>
> </frameset>
> </cf_act_htmltags_frames>
> </CFDEFAULTCASE>
>
> In this manner, your child app hits the parent index page sees this case
and
> knows that any of those fuseactions go to your child app's index.cfm file,
> which then finds the information for that fuseaction.
>
> ----- Original Message -----
> From: "Daye, Marianne" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, July 17, 2000 11:25 AM
> Subject: FuseBox Confusion
>
>
> > I've read the FuseBox Model by Steve Nelson, and used it to some extent
> (not
> > as a tag) for over five months, but there are a few things I don't quite
> > understand:
> >
> > 1. If you choose to call a circuit application as a tag, is it only the
> > index.cfm file that has to be called using CFMODULE?
> yes just make sure to include your attributes. for the circut app
> > 2. If a circuit application is called as a custom tag by multiple
> > applications, shouldn't it be located in the C:\CFusion\CustomTags
> directory
> > on the server?
> yes
> > 3. I understand that you can pass a fuesaction value of 'blank',
'form',
> or
> > 'query' to use the same form three different times. If you use this
> > technique with a circuit application that has more than one form, how
does
> > the index file know which form to include?
>
> > 4. According to advanced technique # 5, when the child application
> > (dual-page tag object) sends the information for the first page to the
> > second page, it will call the parent application, which will call the
> child
> > application (second page, I presume). How is this done? Does anyone
have
> > an example.
> >
> > Thanks in advance!
> >
> > Marianne Daye
> > Programmer/Analyst
> > Information Delivery Systems
> > http://ids.rti.org
> >
>
> --------------------------------------------------------------------------
> ----
> > To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> >
>
> --------------------------------------------------------------------------
--
> --
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> --------------------------------------------------------------------------
----
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
