I'm not using a circuits.cfm
The code isn't that bad at all. The nesting is done logicly, for example:
Home
|
fuse1-fuse2-fuse3-fuse4-fuse5
|
Admin
|
fuse6-fuse7-fuse8-Search------------------Contact_Management
|
|
fuse9-fuse10-Sub_Search fuse11-fuse12-fuse13
|
fuse14-fuse15
It's actually not comeplex at all and the code is very easy to follow.
That's why I still don't see the need for anything more complex. i don't
know .. I guess I'm just missing something.
Todd Ashworth --
| i think it's important to also keep in mind that even when things are
nested
| several fuses deep, that that is by the architect's choice....you can as
| easily make everything be nested one deep simply by expanding the
| top-level's Circuits.cfm file.
|
| it took a few days for that to sink in with me, so that is why I'm
offering
| the thought up.
|
| Also, I'd dare to say that if one's app is multiply-multiply nested then
| perhaps there's a chance that it is too complexly nested? (not that it is,
| but you should at least consider the possibility). Sometimes being too
| general, although it looks good in theory, results in a nightmare,
| particularly if you get hit by a bus and some other schmuck has to take
over
| your code. That's one of the reasons Hal did NOT make the Circuits.cfm
| inherit all the sub-fuseboxes beneath it automatically.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
