I have been working with XFB technique for a little while now and I have not
come to any conclusions yet. The techniques are not dissimilar to what I
have been doing and I have a series of "nested" circuts that go up to 8, yes
8 levels deep...and I got this working just fat, dumb and happy without XFB.
In any event, I do not subscribe to these answers John but not because they
are invalid. In point of fact both of your examples have happened to me in
one form or another. But the logic is invalid because the same could be
said about MyGlobals.cfm or app_locals.cfm...there are some crazy managers
out there who know just enough to be dangerous, mandating things like this
all willy nilly without respect for our years of expertise and common sense.
When does it stop? Where do the variables end and the code begin? Enough
is enough I say...we are #requesting# ourselves to death! Ok, ok...taking a
valium.
But seriously, as Hal will point out, Fusebox is designed with flexibility
in mind so it does not matter if you use #self# or not. The one advantage
he points out as well as does John here is that if you assign #self# then
you don't need to remember where you came from and if you are in a situation
where #self# might actually be a fully qualified path of some sort, you
shorted the amount of typing more than if you just replaced "index.cfm".
My 2.5 cents (inflation...oh wait interest rates are down...guess that's
more like 1.95 cents).
Mike
-----Original Message-----
From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 14, 2001 2:13 AM
To: Fusebox
Subject: Re: Question: Why the change from RFA to XFA method?
> > hey, remember when Hal converted everyone to use "#self#" or
> > "#request.self#" in CFLOCATIONs and FORM ACTIONs ? It is the same
> > idea. You
> > give up very little but gain quite a lot.
>
> Umm, no I don't remember that.
>
> Why use #self# instead of index.cfm? Sure, it's less characters, but I'd
> have to edit my ctrl-1 snippet to change it. Please convince me to use
> #self# instead of index.cfm.
>
> NAT
ok, you have a client who you've already finished the job for, who has a new
boss that decrees that all the web server default documents will be called
"default.*" rather than "index.*". With Hal's way, one change is made in
one place (MyGlobals.cfm). Your way, you have to reach into every template
of the entire app
ok here is an even better idea. In a fit of madness, you want to have have
two fuseboxes in the same directory. Both are already written, you jsut want
them to exist in the same spot. Hal's way, his madness is easily patronized.
One switch to one variable in one file, plus renaming one of his index.cfm
to default.cfm, or somesuch. Your way you descend further into the depths of
insanity.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
