Personally, I think Fusebox is actually working against it's stated purpose.
Which is to make it easier for a coder to read your code later down the
line. The vast majority of CF developers are not Fusebox literate. So what
happens when one of them comes across some Fusebox code??
They have to learn Fusebox to do anything with the code. Which means it will
take LONGER to complete a project.
I think the basic structure of Fusebox, modularizing the code is good and
have been doing this long before I had heard of Fusebox, but the evangelists
need to get off their soapbox. As I think they are only worsening the
problem they are trying to combat.
Bottom Line:
I am not learning Fusbox and my code will always be readable to ANY CF coder
who needs to work on it, and modularized Sensibly, not overdoing it just to
stick to a standard.
jon
----- Original Message -----
From: "Phil Helms" <[EMAIL PROTECTED]>
To: "CF-Server" <[EMAIL PROTECTED]>
Sent: Wednesday, October 11, 2000 8:41 PM
Subject: Re: Best Practices
> Let me try to answer this, although I'm not a programmer.
>
> Fusebox is a set of standards for developing (at this time only) CF-based
> applications. The main purpose of it is to standardize coding practices
so
> that other programmers can support or extend an application. Or work
> together on a single project. That's an important consideration for us,
as
> we're based in the Philippines and work with developers in the US and
> Australia. Fusebox is also a much better environment for bug fixing.
> Overall it probably doesn't save time in the initial coding, but it will
> over time, for the following reason.
>
> The other appeal of Fusebox is that it's hoped that it can lead to the
Holy
> Grail, i.e., reuse of code. But in our experience the basic snippets of
> code - the Fuse - are too small and specific to warrant the time needed to
> catalog and then retrieve, but the larger process-oriented blocks of
code -
> Circuits - are highly reusable. Long term we think that's a major payoff
of
> using this methodology.
>
> There's really very little written on this, although there are
> specifications on the fusebox.org site. The people that I know of who've
> adopted it have learned about it from friends and tried it out. There are
> rumors of a couple of books in the works, but it seems like a very small
> potential market for a publisher.
>
> We use Fusebox exclusively and are completely committed to it - even to
the
> extent of now trying to implement it on a new C++-based Palm venture.
>
> Hope that helps.
>
> Phil Helms
>
> J. Philip Helms
> President/CEO
> Pacific Internet Development Group
>
> ----- Original Message -----
> From: "Eben Hewitt" <[EMAIL PROTECTED]>
> To: "CF-Server" <[EMAIL PROTECTED]>
> Sent: Wednesday, October 11, 2000 10:28 PM
> Subject: RE: Best Practices
>
>
> > www.fusebox.org
> >
> > -----Original Message-----
> > From: David Mineer Jr [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, October 11, 2000 8:22 AM
> > To: CF-Server
> > Subject: RE: Best Practices
> >
> >
> > What is the address of this fusebox. I hear a lot about it but have
been
> > unable to pin point a good tutorial or other information.
www.fusebox.com
> > doesn't seem to have anything, or at least I don't know where to look,
> >
> > TIA,
> >
> > -------------------------------
> > Construction Monitor Tel: 435-586-1205
> > David Mineer Jr Fax:435-586-7414
> > Systems Administrator
> > [EMAIL PROTECTED]
> >
> >
> > -----Original Message-----
> > From: Reynolds, Adam [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, October 10, 2000 9:34 AM
> > To: CF-Server
> > Subject: RE: Best Practices
> >
> >
> > Use of the Fusebox methodology (where appropriate).
> >
> > > ----------
> > > From: Eben Hewitt[SMTP:[EMAIL PROTECTED]]
> > > Sent: 10 October 2000 15:57
> > > To: CF-Server
> > > Subject: Best Practices
> > >
> > > I am working on drumming up a list of best practices for CF coding. I
> > > would
> > > welcome all of your personal Best Practices, and will publish it (and
> give
> > > contributors appropriate credit!) in the avenues I am able to (web, a
> > > journal, a txt file taped to my shaving mirror).
> > >
> > > I know that Ben Forta has a 10 Commandments, but I am thinking of more
> > > specific guidelines, such as 'Validate at the TOP of your form so you
> can
> > > immediately tell which fields contain a validation rule', and like
that.
> > >
> > > I have searched the forums already for such a thing, and do not see it
> > > (myopia?). What are the little things you always make sure to do when
> > > coding?
> > >
> > > Thanks!
> > > Eben
> > >
> > >
> >
>
> --------------------------------------------------------------------------
> > > ----
> > > To unsubscribe, send a message to [EMAIL PROTECTED]
> with
> > > 'unsubscribe' in the body or visit the list page at
> www.houseoffusion.com
> > >
> > **********************************************************************
> > This email and any attachments are confidential and solely
> > for the use of the intended recipient. They may contain
> > material protected by legal professional or other privilege.
> > If you are not the intended recipient or the person responsible
> > for delivering to the intended recipient, you are not authorised
> > to and must not disclose, copy, distribute or retain this email
> > or its attachments. Although this email and its attachments
> > are believed to be free of any virus or other defect, it is the
> > responsibility of the recipient to ensure that they are virus free
> > and no responsibility is accepted by the company for any
> > loss or damage arising from receipt or use thereof.
> >
> > **********************************************************************
>
> --------------------------------------------------------------------------
> --
> > --
> > To unsubscribe, send a message to [EMAIL PROTECTED]
with
> > 'unsubscribe' in the body or visit the list page at
www.houseoffusion.com
>
> --------------------------------------------------------------------------
> --
> > --
> > To unsubscribe, send a message to [EMAIL PROTECTED]
with
> > 'unsubscribe' in the body or visit the list page at
www.houseoffusion.com
> >
> >
>
> --------------------------------------------------------------------------
> ----
> > To unsubscribe, send a message to [EMAIL PROTECTED]
with
> 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
>
> --------------------------------------------------------------------------
----
> To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
