Fork me on GitHub



Fusebox was first conceived by Steve Nelson and Gabe Roffman in late 1997. Fusebox 1.0 was mainly just a methodology; a way to structure the files and directories in an application. Initially, Fusebox was specific to ColdFusion (Allaire Cold Fusion back in those days).

In 1998 and 1999, Fusebox evolved from just a methodology to include some initial code. These came in the form of several ColdFusion custom tags such as cf_bodycontent and cf_formurl2attributes. In 2000, Steve Nelson and Craig Girard published the first Fusebox book, "Fusebox: Methodology and Techniques".

After the book was published, Hal Helms began pushing for a new direction. Under the label "Extended Fusebox", Hal introduced the idea of circuits and exit fuseactions. It took some time for the power of these ideas to sink in with the rest of the community, but they eventually found their way into the next version of Fusebox. Hal also pioneered two other ideas that have been strongly associated with Fusebox ever since: Fusedocs and FLiP (the Fusebox Lifecycle Process).

2001 saw the release of Fusebox 3 by a larger group of developers such as Steve Nelson, Nat Papovich, Hal Helms, and John Quarto-vonTivadar. This was when Fusebox truly moved from a methodology to a framework. Fusebox 3 had a set of core files which handled all the work of processing a request in a Fusebox application. Several books were released to promote Fusebox 3, including "Discovering Fusebox 3" and "Fusebox: Developing ColdFusion Applications".

At this point, the Fusebox community was expanding extremely rapidly and experienced some growing pains. Unsure of the best way to manage and control ongoing development of the framework, some failed attempts at community governance were pursued. A group of key, active members of the community were elected into a Fusebox Council which would vote on and manage key issues. This proved to be too much bureaucracy and eventually was abandoned. It was, however, a useful learning experience in what not to do!

After the release of Fusebox 3, several offshoot frameworks were released by various community members such as FuseQ and Fusebox 3 Lite. None gained very widespread acceptance, but they provided some interesting ideas.

Fusebox 3 also saw the framework expand beyond ColdFusion. David Huyck ported the framework to PHP. Other ports included ASP and JSP.

In 2003, Fusebox 4 was released by John Quarto-vonTivadar. It was loosely based on FuseQ, but had one major new element: XML configuration files. Defining the configuration of a Fusebox application and its circuits in XML brought some compelling advantages. Most enticing was the ability to write application server-neutral code which could then be used to generate either PHP or ColdFusion applications (or any other server which could process the Fusebox XML). "Discovering Fusebox 4" and "Fusebox 4 and FLiP" were published along with this release.

Fusebox 4.1 was released in 2004, which added some new features like the ability to work with CFCs. "Discovering Fusebox 4, Second Edition" and "What's New in Fusebox 4" were published.

In 2006 the development torch was passed to Sean Corfield, and Fusebox 5 was released. This version was backward-compatible with Fusebox 4.1, but rewrote the core files to use CFCs, as well as allowing multiple Fusebox applications share a common application scope. It also took the experimental Lexicons present in 4.1 and made them an official part of the framework. It was now possible to extend the framework without modifying the core files. "Fusebox 5 and FLiP" was published.

Sean released Fusebox 5.1 in early 2007. New features include the ability to have globally shared files, and better support for generating search engine safe URLs.

In August of 2008 Adam Haskel took the riegns of development lead for the Fusebox Framework and released Fusebox 5.5. He worked on the framework until August of 2009.

After a long hiatus the Fusebox Framework, website, and copyright was transfered from TeraTech to John Blayter. The overall goals of this transfer was to place the future of the framework in the community. In January 2012 the transfer was completed and the copyright was removed from the source code.