I'll just thought I'd add a few things :)

I've used Fusebox extensively for several years. My user group (Devon CFUG)
consists of all Fusebox XML users (and one spaghetti coder whom we are
trying to educate!)

I tried out the No XML version when it was launched and haven't really
looked back. I don't mind the XML syntax but prefer having circuit as CFC
(although the named circuit.xml.cfm that Adam proposes will be great!). You
can also mix XML and circuit as CFC if you wish. The lack of plugins hasn't
really stopped me doing anything and the speed of development is much faster
as I don't need to keep parsing the XML.

The designers I work with like Fusebox as they can understand to a point
what is happening, which isn't as easy to follow in some other frameworks.
Admittedly this may just be because I've shown them what is happening so
that may be a moot point.

Also because it supports procedural and OOP styles I can show them
procedural code so that they get up to speed with Fusebox and then introduce
them to OOP with Fusebox.

The fastest framework I've used for getting a site up quickly is actually
ColdFusion on Wheels, however I'd be reticent to use it for a highly bespoke
project. Fusebox is great for building simple websites as I can use
procedural if all it's got is a contact form on it! ColdBox has some cool
built-in but I've barely touched the features so do I want them? It's like
the AJAX tags in CF8, great for quick stuff, but I'd rather do it with
jQuery.

So I really do think it depends on a number of factors as to which is the
best framework for a specific project. Just don't dismiss Fusebox/Other
until you know it's pros and cons.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to