I agree about not having conditional logic in the fusebox (index.cfm). I put
this in the qry file. I didn't follow what you meant about having to rewrite
it, though.
Hal Helms
== See ColdFusionTraining.com for info on "Best Practices with ColdFusion &
Fusebox" training ==
-----Original Message-----
From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 1:01 AM
To: Fusebox
Subject: Re: FuseBox 3.0 dot notation concepts and frames.
>. In fact, Steve has recently convinced me that it makes more sense
> to do as you suggest and just include them in the index.cfm file. I
> initially didn't like the idea, as it meant that two files were linked
> without making this dependency explicit. I've since seen that this can be
> handled by an entry in the Fusedoc.
this is interesting since the more I've been working with your technique,
Hal, the more convinced I am that it is a safer way to leave room for
expansion in the future. The problem with CFINCLUDEing the QRY files in the
index.cfm is that if you have any amount of conditional logic either now or
the future, the index.cfm gets quickly complex. And the index.cfm is the
last place you want to be adding in fusedocs explaining that complexity.
Further, if the QRY file itself starts to have conditional logic (perhaps
you are creating a Fusebox that works on both SQL server and Oracle, and you
want to only ever have to modify the QRY files) then you're gonna end up
wanting to split it up, which means re-writing in two places, rather than
one.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
