I agree with Jeff, completely. Putting the XFAs into a myGlobals.cfm or
equivalent adds....what? yet one more file that has to be opened up, and the
whole concept of "global XFAs" leaves me asking "how often do I 'reuse' a
XFA definition, and even when i do, do I care for any scope other than that
fuse's scope (which is local)?" I also like being able to change the value
in the fuse on-the-fly without having to even remotely wonder or fear that
I'm goofing up something in some other fuse. If my fuse breaks due to a XFA
mistake then I've got one and only one place to look over where the mistake
is and to know the little "roadmap" just for that fuse. And, in some fuses
I do like to be able to have XFA.onSubmit mean something different than
XFA.onSubmit in another.
And lest the objections start to flow vehemently, yes all the problems above
can be gotten round with this global XFA file...but everytime you touch the
file (or in this case the variable) you're potentially setting up every fuse
that depends on it to break--when the XFAs are all local you can't step on
more than your own feet.
> Nope. Assigning XFAs in the fusebox enhances the roadmap nature of that
> pivotal file. Besides, if you assign them in myGlobals, you wind up
reserving
> a bunch of variables that never get used, and you do it for every page
request
> (unless you use a persistent scope and set a conditional block). Keeping
the
> definitions within the Fusebox's CFCASE blocks is much more efficient and
> readable. To me.
>
> - Jeff
>
> On 7 May 2001, at 10:40, Erik Voldengen wrote:
>
> > Does anyone put commonly used XFA definitions in MyGlobals.cfm?
> > Seems like it's a good idea. If it's not, please clue me in.
> >
> > -Erik
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
