Hi Eric,
In standard FuseBox, you don't actually have FuseAction files.
You have a FuseBox file (index.cfm)
You have Fuses (anything else .cfm)
Inside the FuseBox, you have a CFSWITCH statement that assembles the fuses
together to implement your fuseactions.
So a FuseAction to display a form might look like this:
<CFSWITCH EXPRESSION="fuseaction">
...
<CFCASE VALUE=showform>
<CFINCLUDE TEMPLATE="qry_getdropdowndata.cfm">
<CFINCLUDE TEMPLATE="dsp_form.cfm">
</CFCASE>
...
</CFSWITCH>
Your single FuseBox index.cfm can define man FuseActions, all built out of a
set of re-usable Fuses.
Does that make any sense?
Lee (Bjork) Borkman
http://bjork.net ColdFusion Tags by Bjork
-----Original Message-----
From: Eric Gravel [mailto:[EMAIL PROTECTED]]
I'm currently reading the Fusebox book by Steve and I'm finding examples
that call the fuse files with cfmodule and others like on page 39 with
cfinclude. I'd like know how to determine when to the various cases.
IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used by
the named addressee. It is confidential and may contain legally privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. If you receive this e-mail in error, please
immediately delete it from your system and notify the sender. You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient. The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
