> > 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.
>
> It's the perceived problem with browsing the directory structure that I
> don't get. Putting a database layer between me and something as
> fundamental
> as the components of a fuseaction will only slow things down.
The problem (and it's not really a problem so much as an
opportunity for innovation) is that I have to keep referring back to
my index.cfm for reference. To find the file I need, I first have
to look up the fuseaction in the index.cfm and then go to the file.
That involves wading through a bunch of (neatly organized) junk,
then 2-3 screens worth of cfcase tags. I ended up sorting my
fuseactions alphabetically to make things easier.
So what I'm talking about is something like that site browser
Studio already provides. It would give me an instant picture of
the relationships between fuses, fuseactions, and circuits.
> If I've got a fusebox/directory that is too cluttered, that's a
> sign that I
> need to break things up into circuit applications and use the existing
> database (the filesystem itself) more efficiently.
So the file system imposes a constraint on how large a circuit
can be. Yes, I realize that encourages modularization, but I don't
need the encouragement.
The problem with Fusebox today is that it tackles two apparently
conflicting ideas: MODULARITY and a SINGLE ENTRY POINT. I've
decided to focus on the single entry point, and throw in some
middleware to break up the app into digestable pieces.
> > Surely there are patterns that you use over and over?
>
> I don't personally consider the task of typing <CFSWITCH
> expression="#attributes.fuseaction#">once in each index.cfm all that
> onerous. [g]
I wouldn't go to this much trouble to save typing. :) It's
just the fact that all that stuff distracts me from the task
at hand. And ways of doing things are bound to change gradually
over time, and from programmer to programmer. I dunno, maybe
I'm a madman with an OO-hammer. ;-)
Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
