> Lots of people. But they're missing the point of Fusebox, IMO... index.cfm
> is an application's (or circuit's) roadmap. Without those clearly defined
> CFCASE signposts pointing the way, there's no real reason to route
> everything through index.cfm in the first place.
I don't think it's missing the point. Maybe capitalizing on the best
points at the expense of the weaker points. I love my signposts too,
but I think putting all of the signposts in a database would make it
even easier to find what I'm looking for. Imagine a plug-in for
Studio that would allow me to browse my Fusebox app, rather than
browsing the directory structure, etc.
> And of course, on a pragmatic level, a given CFCASE may contain more than
> includes. Mine often contain CFPARAMs, CFMODULE calls, and so on.
I can see the CFParams being part of the database as well. Maybe
CFModule, but see my other post. And of course CFLocation. In a
more generic way we can say that each fuseaction would have some
initialization code and pointers to various subroutines. Personally,
I *never* let any business logic creep into my index.cfm.
> > Why write the same code over and
> > over?
>
> For my part, I *don't* write the same code over and over.
Surely there are patterns that you use over and over? Otherwise,
what's the point? (Oh, and if you mean you use templates,
snippets, etc., that's just as bad in my book. ;-))
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
