We use something like this internally. Ours is called CF_MODULE. Besides
doing everything that normally happens in a Fusebox application, it also
handles all the work of nesting modules (Fuses) using a dotted syntax Method
(FuseAction) variable.
In any case, I highly recommend it. :)
Benjamin S. Rogers
Web Developer, c4.net
voice: (508) 240-0051
fax: (508) 240-0057
-----Original Message-----
From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 4:25 PM
To: Fusebox
Subject: CF_Fusebox
Hi Everyone
I just finished reading the Fusebox book.
I use Fusebox in all of my applications, but only
use the basic concepts along with a couple of my
own simple tecniques. I've always found that a lot
of the code is unnecissarily complicated.
One thing I've never understood is why there are
a handful of custom tags that should be used in
every fusebox app, but the still exist as seperate
entities.
I'm considering adopting a new tag to encapsulate
all the code that goes into EVERY fusebox app.
<cf_fusebox defaultFuseaction="list" header="dsp_header.cfm"
footer="dsp_footer.cfm">
<cfcase value="list">
<cfinclude template="qry_getList">
<cfinclude template="dsp_viewList">
</cfcase>
<cfcase value="view">
<cfinclude template="qry_getItem">
<cfinclude template="dsp_viewItem">
</cfcase>
</cf_fusebox>
The cf_fusebox tag would include references to
the app_ files, the formURL2Attributes code,
the <cf_bodycontent> code, and the <cfswitch>
tags (including <cfdefaultcase>), and
whatever else normally goes into a fusebox
file.
Suggestions? Comments?
Patrick
----------------------------------
Patrick McElhaney
Application Developer
American City Business Journals
704-973-1019 704-236-8351 (cell)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
