I am almost done coding a site (more or less) using Fusebox. My $.02:
The Good:
- The naming conventions are good to use; it is good to have each app in its own
folder.
- You should always focus on code reuse, and FB helps.
The Bad:
- For small teams (I work alone), strictly following the fusedocs and some of the more
specific rules is sort of silly. You always should keep in mind that some other poor
shmuck might inherit your code, so it should be well documented none the less.
The Bottom Line:
- The rules are meant to be broken or bent to fit your situation anyway, so it is a
good enough system. The most important thing is to have a methodology in the first
place.
---------------------------------------
Ben Morris
Web Site Developer
American Federation of Government Employees, AFL-CIO
(202) 639-6448
http://www.afge.org
>>> Gonzo Rock <[EMAIL PROTECTED]> 08/08/01 05:31PM >>>
I want to solicit opinions on FuseBox...
I'm brand new to CF and am wondering if I should really go down that road now or
later... I have a huge app to build... actually already started.
I am soliciting the downside positions... I can already predict the fanatical support
from the upside contributors :-)
And with that let the opinions begin
Thankx,
Oh... PS... I did a search of the cf-talk archives for FuseBox... But those whacky
signatures;(see below) Show up as the majority of the messages for FuseBox... not to
useful no?
Txixtxax Cxaxnxex
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
