frame work matrix .include-once.org

more detailed PHP library/framework feature comparisons

a look beyond the dirty dozen

Framework list

Agavi
Agile Toolkit
Akelos
Adventure PHP Framework
Banshee
Breeze
Caffeine
CakePHP
CodeIgniter
DynaPort Lite X
DynaPort X
EasyPhpApp
Elefant
Emergence
eZ Components
Fat-Free Framework (F3)
FlexiReed
Flourish
TYPO3 Flow
flufPHP
Frostbite Framework
FuelPHP
Fusebox
Hoa
Horde
Ivy Connect
Joomla Platform
Kata
KissMVC
Kohana
Laravel
lexa-tools
Limonade
Lion
Lithium
mocovi / dresscode
Nette
PhalconPHP
Nibble PHP Framework
Openbiz Cubi
Opendelight (Ash.MVC)
Packfire Framework
PHPCodebooster
PHPDevShell
PHPixie
phpMF
PHP Work (QPHP)
phpwt
phraw
phunction
PRADO
PSX Framework
QCubed
Recess
Scorpio Framework for PHP
Seagull
SilverStripe
Sloths
Solar PHP
Spawn Framework
Sukoshi
Swiftlet
Symfony
Symfony2
Tekuna
Thin PHP Framework
Tiny MVC
tinyPHP
Turbo PHP
WACT
YeePHP Framework
Yii
Zend Framework
Zend Framework 2

Filter
MVC  minimal  library  routing  toolkit  ajax  shortlist  all

Submit
Add a new framework

fusebox

Info fusebox
titleFusebox
descriptionColdFusion origin
urlhttp://www.fusebox.org/
licenseApache2
version5.0.1 PHP version stalled, version 5.5.1 for ColdFusion
release1998 2003 for PHP
size676
languagePHP + ColdFusion
documentation
maturitylonglived
developmentclosed
team discontinued
typetoolkit
Coding style fusebox
coding.paradigm XML callbacks
coding.names
coding.autoloader
coding.debugE_DEPRECATED
abstraction.level
coding.unit_tests
Shiny tickoff boxes 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
Compatibility fusebox
compatible.phpphp4
standard.htmlhtml4
compatible.app
compatible.forksFusebox CFMX
compatible.sql
compatible.css
compatible.plugin
Security fusebox
security.db-
security.inputsanitization-
security.outputescaping
security.auth
security.admin
MVC fusebox
mvc.type Honestly, no idea how to categorize it.
Routing fusebox
routing.typefront controller
routing.rewriterules
routing.dispatch
routing.responder
Model fusebox
model.type
model.db
model.backend
View fusebox
view.type
view.backend
view.collect
view.output
Controller fusebox
controller.type
controller.helper
Configuration fusebox
configuration.type framework-only configuration xml structure
configuration.storefiles
configuration.formatXML
AJAX fusebox
ajax.type-
ajax.library-
Helper fusebox
util.upload
util.session
util.cookie
util.pagination
util.http
util.url
util.mime
util.permission
util.debug
util.localization-
util.formtemplate
Utility 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
Services 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
Fun Facts fusebox
forum_from_framework
popular_apps
big_websites

Comments

Add a Comment


What is 14 * 7 =  

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