Fusebox really just offers a standard way of developing n-tier applications, and an easy way for new modules/applications to be plugged into the developed system. Although it was developed with CF in mind it has been used with other development languages.
The basics are along these lines. All of the code is seperated into their own seperate files. so for a page that has a query, some processing and then some output, all of these functions would be in different files and then included into the system using cfinclude's
so where a page might have looked like this:
Code:
<cfquery ...>
select a
from b
</cfquery>
<cfif query.a eq 10>
<cfset something = query.a>
<cfelse>
<cfset something = 1>
</cfif>
<table border....>
<tr>
<td><cfoutput>#something#</cfoutput></td>
</tr>
</table>
the page would look like this:
Code:
<cfinclude template="qrySomething.cfm">
<cfinclude template="actProcessing.cfm">
<cfinclude template="dspResults.cfm">
with all of the info from the 1st code block in the various files.
this could for example allow several people to be working on things at the same time. a db person could work on queries, a designer on the output and you could work on processing, and not trip over each other.
A query filename is proceded by qry, an action file by act and an output file by dsp. Some people use frm for a form as well but i just think that is taking things one step too far. to be honest I don't use the full fusebox specification when developing applicaton, we tend to use the bits that suit us and adapt things to out needs.
Hope this helps!
Tony