The Fusebox methodology is created/modified/evolved by hundreds of people in
the FB community. Throw your hat into the ring if you like!

Greg

-----Original Message-----
From: Adrocknaphobia Jones [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003 4:17 PM
To: CF-Talk
Subject: RE: Fusebox was RE: Design Pattern Question


" Fusebox is the most widely distributed Framework/Methodology for
developing ColdFusion Applications"

What other Framework/Methodologies exist for Cold Fusion?

Is the fuseBox framework/methodology decided by a consortium? Or by a
few elite people?

Adam Wayne Lehman
Web Systems Developer
Johns Hopkins Bloomberg School of Public Health
Distance Education Division


-----Original Message-----
From: Mike Brunt [mailto:[EMAIL PROTECTED]] 
Sent: Monday, January 13, 2003 3:09 PM
To: CF-Talk
Subject: Fusebox was RE: Design Pattern Question

As far as I understand it Hal Helms is no longer on the Fusebox
committee,
he was a founding member.  I can tell you that he is still very much
involved with Fusebox and at the forefront of the Fusebox iteration for
ColdFusion MX just repeating here, you can see some of his work in that
regard here
http://www.halhelms.com/webresources/fuseboxmxpreso/page1.htm.

Fusebox is the most widely distributed Framework/Methodology for
developing
ColdFusion Applications and as stated here is also being looked at for
ASP,
JSP and PHP development.  There are rumblings that CFC's obviate the
need
for Fusebox, my feelings are that CFC's as of themselves do not answer
all
the application needs that Fusebox including Fusedocs (a documentation
capability) and FLiP (an application lifecycle methodology) answered.

Many people are waiting to see what Fusebox for ColdFusion MX looks like
and
I also know that there is a lot of interest among Flash developers about
Fusebox as a methodology/framework for Flash Application development.

Kind Regards - Mike Brunt, CTO
Webapper
Blog http://www.webapper.net
Web site http://www.webapper.com
Downey CA Office
562.243.6255
AIM - webappermb

Web Application Specialists


-----Original Message-----
From: charlie griefer [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003 11:48 AM
To: CF-Talk
Subject: Re: Design Pattern Question


Scott Wilhelm writes:

> This might be a stupid question, but what's Fusebox? (Sorry, I'm a
> newbie in the CF world)

http://www.fusebox.org.

it's a fairly popular design methodology (started with CF, and i believe
has
been ported to PHP).

Altho I understand that CFC's, now available in CFMX, kind of render
fusebox
moot (disclaimer: i do not know fusebox...i do not know for certain that
fusebox is no longer 'worthwhile'...this is only something that i have
heard
in certain circles) :)

charlie





>
> SW
>
>       -----Original Message-----
>       From: Adrocknaphobia Jones
>       Sent: Mon 01/13/2003 02:22 PM
>       To: CF-Talk
>       Cc:
>       Subject: RE: Design Pattern Question
>
>
>
>       Not one to start gossip, but I was under the influence that Hal
> Helms
>       left the fusebox group. Is this true? If so why did he leave, if
> not,
>       why is this rumor floating around?
>
>       Adam Wayne Lehman
>       Web Systems Developer
>       Johns Hopkins Bloomberg School of Public Health
>       Distance Education Division
>
>
>       -----Original Message-----
>       From: Mike Brunt [mailto:[EMAIL PROTECTED]]
>       Sent: Sunday, January 12, 2003 12:13 PM
>       To: CF-Talk
>       Subject: RE: Design Pattern Question
>
>       Yes this is a good methodology to consider as we all move out of
>       procedural
>       methodologies to more 'OO' based concepts.  Yet in my opinion
> there is a
>       further dimension that Fusebox achieves, or has done for us,
> that I have
>       not
>       yet seen expounded in CFMX tutorials etc.
>
>       Using Fusebox in conjunction with FLIP we have a complete
> application
>       design
>       and development environment from concept-discussion through
>       coding-ongoing
>       maintenance.  In addition by using Fusebox we have found it easy
> to
>       bring in
>       developers who had never coded on CF before but who had a good
> grasp of
>       HTML, JavaScript and/or ASP-JSP.  Further by abstracting the
> actual
>       Fuseaction values till run-time Fusebox truly affords the
> capability at
>       another layer of separation, that of separating design from
> development;
>       when combined with the very descriptive capabilities afforded by
> the use
>       of
>       Fusedocs.  Finally, the logicality of using Circuits as a
>       mapping/pathing
>       mechanism addresses to physical layout questions of developing a
> web
>       application.
>
>       There is one last very important point here, there have been
> many
>       previous
>       methodologies/frameworks applied to ColdFusion development.
> What is
>       different in Fusebox is it has become the most widely used of
> all of
>       them
>       and that is a very considerable factor for those of us using
> teams of
>       developers that can change, grow, shrink etc.
>
>       I recommend you take a look at Hal Helms work
>       http://www.halhelms.com/webresources/fuseboxmxpreso/page1.htm as
> CFMX
>       and
>       Fusebox are melded to form the next iteration of Fusebox.
>
>       Kind Regards - Mike Brunt
>       Webapper Services LLC
>       Web Site http://www.webapper.com
>       Blog http://www.webapper.net
>
>       Webapper <Web Application Specialists>
>
>       -----Original Message-----
>       From: Peter Bagnato [mailto:[EMAIL PROTECTED]]
>       Sent: Saturday, January 11, 2003 6:38 PM
>       To: CF-Talk
>       Subject: RE: Design Pattern Question
>
>       I think that this is a very healthy design methodology for CF.
>
>       Ben Forta has been harping for ages about the importance of
> separating
>       the
>       display, application, and data layers from the CF applications.
>
>       The methodology outlined in that page presents this to the CF
>       environment.
>
>       It actually follows many of the well known and widely used J2EE
>       methodologies out there. That was something that always bugged
> me about
>       FuseBox and other methodologies presented for CF.
>
>       Those are just my thoughts:
>       Peter Bagnato
>
>
>       -----Original Message-----
>       From: Cutter (CF_Talk) [mailto:[EMAIL PROTECTED]]
>       Sent: Saturday, January 11, 2003 11:59 PM
>       To: CF-Talk
>       Subject: Design Pattern Question
>
>       Has anyone here taken a detailed look at the CFMX (semi) OOP
> design
>       pattern put forth at http://www.benorama.com? Is anyone here
> using it?
>       Formed some opinions? Have anything to add (or subtract)? Know
> who put
>       this together in the first place?
>
>       As one of my former commanders used to ask "Questions? Comments?
> War
>       Stories?"
>
>       Cutter
>
>
>
>
>
>
>



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to