> But the
> structure standards *are* necessary for the development of various tools
> that are starting to emerge...
John,
IMO, it's unnecessary for people to bother creating Fusebox-related tools
that can't adapt (or be adapted) to individual patterns of usage. Either
keep the function flexible or the source open... that's about as close to a
"standard" as anyone needs in this context.
> ...but "heavy" enough to gently
> ease folks away from the Clint Eastwood "Do it any way you want without
> ramifications" problem.
Y'know, I can honestly say that I didn't start using Fusebox so I could
experience a random group of people on a mailing list gently easing me away
from any practice I find useful. Call me crazy. [g]
--
Roger
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
