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.
