.include-once.org
Framework list
Filter
MVC
minimal
library
routing
toolkit
ajax
shortlist
all
Submit
Add a new framework
fusebox
| fusebox | |
title | Fusebox |
| description | ColdFusion origin |
| url | http://www.fusebox.org/ |
| license | Apache2 |
| version | 5.0.1 |
| release | 1998 |
| size | 676 |
| language | PHP |
| documentation | |
| maturity | longlived |
| development | closed |
| team | |
| type | toolkit |
| fusebox | |
| coding.paradigm | |
| coding.names | |
| coding.autoloader |  |
| coding.debug | E_DEPRECATED |
| abstraction.level | |
| coding.unit_tests | |
| fusebox | |
| modules.mvc |  |
| modules.db |  |
| modules.orm | |
| modules.crud | |
| modules.multidb | |
| modules.filedb | |
| modules.auth | |
| modules.cache | |
| modules.validate | |
| modules.filter | |
| modules.i18n | |
| modules.session | |
| modules.log |  |
| modules.sandbox | |
| modules.benchmark | |
| modules.form | |
| modules.ajax | |
| modules.edp | |
| modules.plugins | |
| modules.dist | |
| modules.cli | |
| modules.scaffolding | |
| modules.rest | |
| fusebox | |
| compatible.php | php4 |
| standard.html | html4 |
| compatible.app | |
| compatible.forks | Fusebox CFMX |
| compatible.sql | |
| compatible.css | |
| compatible.plugin | |
| fusebox | |
| security.db | - |
| security.inputsanitization | - |
| security.outputescaping | |
| security.auth | |
| security.admin | |
| fusebox | |
| mvc.type | |
| fusebox | |
| routing.type | front controller |
| routing.rewriterules | |
| routing.dispatch | |
| routing.responder | |
| fusebox | |
| model.type | |
| model.db | |
| model.backend | |
| fusebox | |
| view.type | |
| view.backend | |
| view.collect | |
| view.output | |
| fusebox | |
| controller.type | |
| controller.helper | |
| fusebox | |
| configuration.type | |
| configuration.store | files |
| configuration.format | XML |
| fusebox | |
| ajax.type | - |
| ajax.library | - |
| fusebox | |
| util.upload | |
| util.session | |
| util.cookie | |
| util.pagination | |
| util.http | |
| util.url | |
| util.mime | |
| util.permission | |
| util.debug | |
| util.localization | - |
| util.form | template |
| fusebox | |
| http.negotiation | |
| http.conditional | |
| util.xml | |
| util.rss | |
| util.zip | |
| util.mail | |
| util.gzip | |
| util.captcha | |
| util.dom | |
| util.markup | |
| util.pdf | |
| util.images | |
| util.wysiwyg | |
| util.webdav | |
| fusebox | |
| util.sitemap | |
| util.pingback | |
| util.rpc | |
| service.twitter | |
| service.google | |
| service.facebook | |
| service.openid | |
| service.cardspace | |
| service.oauth | |
| service.opensearch | |
| service.geo | |
| service.paypal | |
| fusebox | |
| forum_from_framework | |
| popular_apps | |
| big_websites | |
Edit
You can also update this entry, if you have more information.
Updated versions
Comments
fusebox
It is important to note that Fusebox deals primarily with the effort of wiring together view states (pages) with controller actions (form submits, etc.) and the front-end of the business-logic tier. The framework does not address creating and maintaining business logic such as database interaction or service layers.
== Concepts ==
Fusebox, Circuits and Fuseactions
The original concepts behind Fusebox were based on the household idiom of an electrical fusebox that controls a number of circuits, each one with its own fuse. In a Fusebox web application, all requests are routed through a single point (usually index.cfm for ColdFusion) and processed by the Fusebox core files. The application is divided into a number of circuits (usually in sub-directories) which are intended to contain related functionality. Each circuit in the application is further divided into small files called fuses that should perform simple tasks. As such, Fusebox is considered an implementation of the front controller, a common design pattern.
URLs within a Fusebox web application are usually of the form index.cfm?fuseaction=cname.fname where "cname" is the name of a circuit and "fname" is an XML-defined "method" within that circuit known as a fuseaction. The query-string variable name "fuseaction" can vary depending on configuration parameters, so not all applications using Fusebox need to use the action variable "fuseaction".
Naming Conventions
Fusebox encourages, but does not enforce, separation of presentation logic from business logic. It uses a number of file naming conventions to encourage this separation: presentation files begin with dsp (display) or lay (layout), database access files begin with qry (query) and general business files begin with act (action). Typical file names are in the format [prefix]_[filename] like dsp_loginform.cfm. Additional naming conventions are used by some Fusebox developers but these are the most common ones.
Exit Fuseactions
Another concept that Fusebox encourages is to parameterize any exit points in a web page, coding them as variables that are set in the circuit control file. These exit points are known as XFAs - eXit FuseActions. The idea is that by parameterizing the exit points in a web page, the flow of control can be updated more easily, allowing more reuse of web pages or fragments thereof.
FuseDocs
Associated with the framework, but not strictly part of it, is the concept of FuseDocs which is a semi-formalized form of documentation written in XML that specifies the inputs and outputs of each fuse file. There are third-party tools available which can use FuseDocs to do things like generate test harness code.
== Project Status ==
discontinued
Add a Comment