Preach it, brother! Amen!
Hal Helms
Team Allaire
[ See www.halhelms.com <http://www.halhelms.com> for info on training
classes ]
-----Original Message-----
From: Fred T. Sanders [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 9:34 AM
To: Fusebox
Subject: Re: Surveying the community
Simple. What makes us fuseboxers is the feeling we have in the pit of our
gut that there is a better way to do it, and the likelihood that we will not
only go out and look for that better way, but will share its wisdom and
ideas with as many people as possible in the hopes that it will a spark an
idea within them that will also be shared with us.
What makes a user a fusebox user isn't the fact that we run all actions
through a single file, it isn't the fact that we have fuseaction=blah in our
urls and forms. Its not our nifty naming conventions we use on files. It
isn't even the over abundance of cfinclude statements in our code that we
use to make everything as reusable as possibly as well as our code cleaner.
At one time the fusebox in an index.cfm was actually a great big
if/elseif/else statement. I cringe when I see some older fusebox apps that
are like that. (yes there are plenty and they're still making their
customers proud. Now its a switch/case statement. Why? Well because a
fuseboxer found out it that CF had finally added switch/case logic to
ColdFusion, and apon further research they noticed it was much much faster
(exponentially so, as the application grew bigger) than the if/elseif/else
way of doing things, and they shared their findings.
Fusebox is about finding the best way to get the job done. Any job, period.
Whether its adding 3 extra weeks of specifications, so that you can cut the
time you'll spend writing code into a matter of 2-3 days, or developing an
application frame work that allows you to take almost any application and
integrate it into another application your working on, and have it work.
It doesn't matter if your personal preference is A or B. Depending on the
complexity of the application, my cflocation might be directly in the fuse
or in a url_ file.
Sure just because I don't need conditional logic for that one cflocation
doesn't mean I should still put it in a URL_ file, just for the sake of
"standardization", when it doesn't add readability, or make it more
efficient.
Sometimes, it makes more sense to include a file directly in the fuse
calling it, sometimes it doesn't. because I'm including a query at the fuse
level instead of in the fuseaction, doesn't mean I'm not living up to my
"Fusebox" potential. Its because I am smart enough to know when its best to
include it directly in the template, or when to include it in the fuse
definition.
This, "that's not the fusebox way man!" crap has really got to stop, this
isn't a religion, its a way of thinking, that hopefully promotes THINKING
FOR YOURSELF.
So to summarize Lee, no your not loosing your way. Everyone will always
have different ways, and its the situation and needs of the application that
dictate. the
best way to go about it.
Cheers! :)
Fred S.
----- Original Message -----
From: "BORKMAN Lee" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Tuesday, April 10, 2001 1:59 AM
Subject: RE: Surveying the community
> To me, this is not a matter of Style A vs Style B - it's a matter of
FuseBox
> vs non-FuseBox. Take out this rule, and it's no longer what I would call
> FuseBox. I'm sure that either way is fine, but now I'm losing my way,
> wondering what common idea makes us all FuseBox users.
>
> So there ;-)
>
>
> IMPORTANT NOTICE:
> This e-mail and any attachment to it is intended only to be read or used
by
> the named addressee. It is confidential and may contain legally
privileged
> information. No confidentiality or privilege is waived or lost by any
> mistaken transmission to you. If you receive this e-mail in error, please
> immediately delete it from your system and notify the sender. You must
not
> disclose, copy or use any part of this e-mail if you are not the intended
> recipient. The RTA is not responsible for any unauthorised alterations to
> this e-mail or attachment to it.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
