I try not to go to bed before it's dark. My children find such behaviour
disturbing.
I must admit that I get depressed by the do-what-works-for-you mantra. Of
course, that is what we will all do. But to use that as a reply to any
criticism smacks of a cop-out. Is "best-practice" just a pipe-dream? I
want the rest of the CF community to take up FuseBox, BUT I DO NOT want to
expand the definition of FuseBox so that it simply encompasses all CF coding
styles.
I accept that there are plenty of ways to get things done. I have
maintained since the dawn of time that FuseBox was probably not the best
possible architecture - it just happens to be a popular, well-documented,
useful architecture, so I choose to go along.
But insisting that calls to fuses are all made from the fusebox is the whole
FuseBox concept to me, or I am just a poor deluded Southerner. Everything
else is frills. If you have a better way, then let's just say you have
something better than FuseBox.
Allowing fuses to call each other may create a better architecture. But if
you call it FuseBox, then I'll just get confused. My mind is just so
fragile, as you know.
Lee.
-----Original Message-----
From: Erik Voldengen [mailto:[EMAIL PROTECTED]]
....
Dude go to bed! There are countless versions of Fusebox that
have been adopted by the community, and there always will be.
The idea that I believe makes most of us users of the Fuse is
that it helps us code web applications modularly, which in turn
gives us code that is easier reuse, maintain, and develop within
a team environment. Fusebox two years ago did this, and XFB
does this, too. Doesn't matter to me (or my clients) as long as
it gets done and it works. 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
