I dont' follow fusebox to the letter. I adapted the methodology to what
works best for me.
Since each of the programs off my main nav are true programs in their own
right, I didn't see what the point was of going through a top level
index.cfm. If you want to though, go ahead. YMMV. This is a methodology,
not a strait jacket.
Also I veer away from the methodology in a very important point, but to me
it makes my work even more modular and easier to read.
In every form submittal I have my fuseaction set to <input type="Hidden"
name="fuseaction" value="#Attributes.FuseAction#">
I also have a <input type="Hidden" name="ProcessForm" value="true"> in every
form.
When a fuseaction is called, index.cfm checks to see if there is a variable
called ProcessForm. If there isn't it executes the display.
If the variable exists, it executes an action file instead tied to the
fuseaction. This could be update, add, delete, whatever. I then do
a cflocate back to the fuseaction in effect calling itself and going back to
the display.
This works very well for me, For every fuseaction, all functionality is
contained in one area. Much easier for me to figure where I am going then
to call different fuseactions for every type of process I want to perform.
It also promotes form reuse in that I can just plug in my display file for
either an add or an update and it knows what to call each and every time.
Then again I also use a lot of composite forms which aren't defined in the
fusebox methodology either, but work great for me in terms of re-use.
Bottom line, don't follow blindly. Take what is good about fusebox, use it
and don't be afraid to not use what doesn't make sense for you.
-----Original Message-----
From: Jerry L. Tarter [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 09, 2000 11:17 AM
To: Fusebox
Subject: Re: Root Index.cfm
This is a multi-part message in MIME format.
------=_NextPart_000_00B9_01C04A57.A7FC3DB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
So, if I understand you correctly, your nav buttons make the call =
directly and don't go through root index.cfm.
This is the exact scenario that I don't understand -- I would think you =
would want to set your root index.cfm as the parent and treat all of the =
circuit apps as children. . Maybe I should ask the question: Is there =
suppose to be a relationship between the root (Index.cfm) and circuit =
apps?
I'm trying to implement the FuseBox methodology but would like to adopt =
a more standard way of handling the root index.cfm logic.=20
Is there one standard that is more accepted than the other?
Later--Jerry
----- Original Message -----=20
From: "Sandra Clark" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Thursday, November 09, 2000 11:42 AM
Subject: RE: Root Index.cfm
> Not necessarily. I have my navigational buttons making calls to the
> different fuseapps that make up my application. My index page only =
really
> controls the home page and login functionality.
>=20
> -----Original Message-----
> From: Jerry L. Tarter [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 09, 2000 7:55 AM
> To: Fusebox
> Subject: Root Index.cfm
>=20
>=20
> This is a multi-part message in MIME format.
>=20
> ------=3D_NextPart_000_006D_01C04A3B.8DF54040
> Content-Type: text/plain;
> charset=3D"iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>=20
> I'm having difficulties in grasping the intent of the index.cfm file =
on =3D
> the root directory and it's relationship to the circuit application's =
=3D
> index.cfm files.=3D20
>=20
> Is the root index.cfm file suppose to control the flow to all of the =
=3D
> circuit applications fuseboxes (index.cfm)? In other words, is the =3D
> initial call to a circuit application's index.cfm suppose to come only =
=3D
> through the root index.cfm?
>=20
> Any help in this area would be appreciated.=3D20
>=20
> Later--Jerry
>=20
>=20
>=20
>=20
> ------=3D_NextPart_000_006D_01C04A3B.8DF54040
> Content-Type: text/html;
> charset=3D"iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>=20
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META content=3D3D"text/html; charset=3D3Diso-8859-1" =3D
> http-equiv=3D3DContent-Type>
> <META content=3D3D"MSHTML 5.00.2919.6307" name=3D3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D3D#ffffff>
> <DIV><FONT face=3D3DArial size=3D3D2>
> <P>I'm having difficulties in grasping the intent of the index.cfm =
file =3D
> on the=3D20
> root directory and it's relationship to the circuit application's =3D
> index.cfm=3D20
> files.=3D20
> <P>Is the root index.cfm file suppose to control the flow to all of =
the =3D
> circuit=3D20
> applications fuseboxes (index.cfm)? In other words, is the initial =
call =3D
> to a=3D20
> circuit application's index.cfm suppose to come only through the root =
=3D
> index.cfm?
> <P>Any help in this area would be appreciated. </P>
> <P>Later--Jerry</P>
> <P> </P></FONT></DIV></BODY></HTML>
>=20
> ------=3D_NextPart_000_006D_01C04A3B.8DF54040--
>=20
> =
-------------------------------------------------------------------------=
---
> --
> To Unsubscribe visit
> =
http://www.houseoffusion.com/index.cfm?sidebar=3Dlists&body=3Dlists/fuseb=
ox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' =
in
> the body.
>=20
>=20
> =
-------------------------------------------------------------------------=
-----
> To Unsubscribe visit =
http://www.houseoffusion.com/index.cfm?sidebar=3Dlists&body=3Dlists/fuseb=
ox or send a message to [EMAIL PROTECTED] with =
'unsubscribe' in the body.
------=_NextPart_000_00B9_01C04A57.A7FC3DB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>So, if I understand you correctly, your =
nav buttons=20
make the call directly and don't go through root index.cfm.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>This is the exact scenario that I don't =
understand -- I would think you would want to set your root =
index.cfm as=20
the parent and treat all of the circuit apps as children. . Maybe I =
should ask=20
the question: <FONT color=3D#0000ff>Is there suppose to be a =
relationship between=20
the root (Index.cfm) and circuit apps?</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>I'm trying to implement the FuseBox =
methodology but=20
would like to adopt a more standard way of handling the root index.cfm =
logic.=20
</FONT></DIV>
<DIV> </DIV>
<DIV></FONT><FONT face=3DArial size=3D2>Is there one standard that is =
more accepted=20
than the other?</FONT></DIV></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Later--Jerry</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>----- Original Message ----- </FONT>
<DIV><FONT face=3DArial size=3D2>From: "Sandra Clark" <</FONT><A=20
href=3D"mailto:[EMAIL PROTECTED]"><FONT face=3DArial=20
size=3D2>[EMAIL PROTECTED]</FONT></A><FONT face=3DArial =
size=3D2>></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>To: "Fusebox" <</FONT><A=20
href=3D"mailto:[EMAIL PROTECTED]"><FONT face=3DArial=20
size=3D2>[EMAIL PROTECTED]</FONT></A><FONT face=3DArial=20
size=3D2>></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sent: Thursday, November 09, 2000 11:42 =
AM</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Subject: RE: Root =
Index.cfm</FONT></DIV></DIV>
<DIV><BR></DIV><FONT face=3DArial size=3D2>> Not necessarily. I =
have my=20
navigational buttons making calls to the<BR>> different fuseapps that =
make up=20
my application. My index page only really<BR>> controls the =
home page=20
and login functionality.<BR>> <BR>> -----Original =
Message-----<BR>>=20
From: Jerry L. Tarter [</FONT><A =
href=3D"mailto:[EMAIL PROTECTED]"><FONT=20
face=3DArial size=3D2>mailto:[EMAIL PROTECTED]</FONT></A><FONT =
face=3DArial=20
size=3D2>]<BR>> Sent: Thursday, November 09, 2000 7:55 AM<BR>> To: =
Fusebox<BR>> Subject: Root Index.cfm<BR>> <BR>> <BR>> This =
is a=20
multi-part message in MIME format.<BR>> <BR>>=20
------=3D_NextPart_000_006D_01C04A3B.8DF54040<BR>> Content-Type:=20
text/plain;<BR>> charset=3D"iso-8859-1"<BR>> =
Content-Transfer-Encoding:=20
quoted-printable<BR>> <BR>> I'm having difficulties in grasping =
the intent=20
of the index.cfm file on =3D<BR>> the root directory and it's =
relationship to=20
the circuit application's =3D<BR>> index.cfm files.=3D20<BR>> =
<BR>> Is the=20
root index.cfm file suppose to control the flow to all of the =
=3D<BR>> circuit=20
applications fuseboxes (index.cfm)? In other words, is the =3D<BR>> =
initial=20
call to a circuit application's index.cfm suppose to come only =
=3D<BR>> through=20
the root index.cfm?<BR>> <BR>> Any help in this area would be=20
appreciated.=3D20<BR>> <BR>> Later--Jerry<BR>> <BR>> =
<BR>> <BR>>=20
<BR>> ------=3D_NextPart_000_006D_01C04A3B.8DF54040<BR>> =
Content-Type:=20
text/html;<BR>> charset=3D"iso-8859-1"<BR>> =
Content-Transfer-Encoding:=20
quoted-printable<BR>> <BR>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD =
HTML 4.0=20
Transitional//EN"><BR>> <HTML><HEAD><BR>> <META=20
content=3D3D"text/html; charset=3D3Diso-8859-1" =3D<BR>>=20
http-equiv=3D3DContent-Type><BR>> <META content=3D3D"MSHTML =
5.00.2919.6307"=20
name=3D3DGENERATOR><BR>> <STYLE></STYLE><BR>>=20
</HEAD><BR>> <BODY bgColor=3D3D#ffffff><BR>> =
<DIV><FONT=20
face=3D3DArial size=3D3D2><BR>> <P>I'm having difficulties =
in grasping=20
the intent of the index.cfm file =3D<BR>> on the=3D20<BR>> root =
directory and=20
it's relationship to the circuit application's =3D<BR>> =
index.cfm=3D20<BR>>=20
files.=3D20<BR>> <P>Is the root index.cfm file suppose to =
control the=20
flow to all of the =3D<BR>> circuit=3D20<BR>> applications =
fuseboxes=20
(index.cfm)? In other words, is the initial call =3D<BR>> to =
a=3D20<BR>>=20
circuit application's index.cfm suppose to come only through the root =
=3D<BR>>=20
index.cfm?<BR>> <P>Any help in this area would be appreciated.=20
</P><BR>> <P>Later--Jerry</P><BR>>=20
<P>&nbsp;</P></FONT></DIV></BODY></H=
TML><BR>>=20
<BR>> ------=3D_NextPart_000_006D_01C04A3B.8DF54040--<BR>> =
<BR>>=20
-------------------------------------------------------------------------=
---<BR>>=20
--<BR>> To Unsubscribe visit<BR>> </FONT><A=20
href=3D"http://www.houseoffusion.com/index.cfm?sidebar=3Dlists&body=3D=
lists/fusebox"><FONT=20
face=3DArial=20
size=3D2>http://www.houseoffusion.com/index.cfm?sidebar=3Dlists&body=3D=
lists/fusebox</FONT></A><FONT=20
face=3DArial size=3D2> or<BR>> send a message to </FONT><A=20
href=3D"mailto:[EMAIL PROTECTED]"><FONT face=3DArial=20
size=3D2>[EMAIL PROTECTED]</FONT></A><FONT face=3DArial =
size=3D2> with=20
'unsubscribe' in<BR>> the body.<BR>> <BR>> <BR>>=20
-------------------------------------------------------------------------=
-----<BR>>=20
To Unsubscribe visit </FONT><A=20
href=3D"http://www.houseoffusion.com/index.cfm?sidebar=3Dlists&body=3D=
lists/fusebox"><FONT=20
face=3DArial=20
size=3D2>http://www.houseoffusion.com/index.cfm?sidebar=3Dlists&body=3D=
lists/fusebox</FONT></A><FONT=20
face=3DArial size=3D2> or send a message to </FONT><A=20
href=3D"mailto:[EMAIL PROTECTED]"><FONT face=3DArial=20
size=3D2>[EMAIL PROTECTED]</FONT></A><FONT face=3DArial =
size=3D2> with=20
'unsubscribe' in the body.</FONT></BODY></HTML>
------=_NextPart_000_00B9_01C04A57.A7FC3DB0--
----------------------------------------------------------------------------
--
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.
