Actually, I'm not becoming bigotted. As a matter of fact, I never once
mentioned fusebox in my email. I've never even used fusebox. I've read the
docs but havent had time to get away from my workload to learn it or try to
put it to use so I don't know if I'll like it or hate it yet. All I was
saying is that the point of coming up with a standard methodology is for the
reuse and sharing of code and what not. Sort of like browser standards that
are ignored by IE and Netscape to the point that we have lovely browser
incompatibilities. Not that the way you code CF will ever come to that level
of incompatibility (at least I hope not). Maybe soem osrt of broad, general
methodology that everyone used and built upon would be nice. Anyway, for the
most part I'm only theorizing. I've never worked anywhere that had any
coding standards. I'm the only web developer, designer, programmer at my
company and I'm the one who convinced "the boss" to buy CF and put it on our
servers. (Now if I can only convince him to pay for my training). So I guess
if anything, my method is our company methodology... now I just need to come
up with my own personal standard :)
-Will
----- Original Message -----
From: "Pecora, James" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 13, 2000 2:08 PM
Subject: RE: Fusebox or not Fusebox that is the question...
> Only if you want to dictate how the world codes...
> A methodology should fit the design standards and goals of a team/company
> only.
>
> As discussed in numerous threads onthis list - not every methodology fits
> every need. And indeed, specificially FUSEBOX doesn't NOT fit everyones
> needs - so for you to assume that a standard methology should be
implemented
> throughout the CF community is quite presumptious.
>
> Each firm that I have worked for implements their own coding standards -
and
> Yes I need to learn a new standard each time I change jobs, but each job
has
> different goals...it can be no other way.
>
> I know there are a lot of FUSEBOX proponents out there - but let's not
cross
> teh line and become bigots..
>
>
>
> -----Original Message-----
> From: William James [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 13, 2000 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Fusebox or not Fusebox that is the question...
>
>
> But the point of a standard methodology is that its consistent throughout
> the team AND outside of it. If you or one of your team left and went to
> another company you might have to learn a whole new methodology and throw
> out a lot of what you'd been using for years. With a standard, you would
be
> using the same methodology from one place to another and the same for
> sharing fuses, etc. If it uses a different scheme than someone else, it
> kills the reusability and shareability across companies/teams/etc. But I
> guess a mini-methodology is better than none ;)
>
> ----- Original Message -----
> From: "Pecora, James" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 13, 2000 9:19 AM
> Subject: RE: Fusebox or not Fusebox that is the question...
>
>
> > Bill - you are correct - FUSEBOX is just a methodology, any standarized
> > methodology throughout a team environment will do the same thing. As for
> > compartmentalizing the code for ease of debugging in the team..that can
be
> > part of your standard and not necessarily fe fusebox.
> >
> > Personally I use a method that is similar to fusebox in some way and
> > diferent in other ways..
> > I suppose it's the consistancy throughout the team that makes a standard
> > usefull..
> >
> >
> >
> > -----Original Message-----
> > From: Bill Killillay [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, April 13, 2000 10:20 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Fusebox or not Fusebox that is the question...
> >
> >
> > Can't all of that be done by establishing standards for a project or all
> > projects. Why does it have to be Fusebox? I have been looking at
Fusebox
> > and I guess that I am a bit confused as to what it is and why I should
use
> > it over some other set of standards?
> >
> > FWIW
> > Bill Killillay
> > ICQ @ 8425781
> >
> > Emily B. Kim Wrote:
> > > when you're working in a team environment, isolating pages makes them
> > > easier to debug and also easier to reuse. for instance, we were
working
> on
> > > an app and people were doing different parts of the app. the client
made
> a
> > > change to the db and threw off one part of the app....a part i didn't
> work
> > > on. but i was able to fix it in 5 minutes 'cause i knew what the
> > > fuseaction
> > > was and that it was a query error so i just opened the query
associated
> > > with that fuseaction, and BINGO! it was fixed. i didn't even have to
> look
> > > at the rest of the code for that piece of the app.
> > >
> > > also, if you have a query that can be re-used - for instance to
populate
> a
> > > table in one page and then a select drop down box in another page - it
> is
> > > easier to just write it once. you could even make it more flexible by
> > > adding options for conditional processing. -emily
> >
> >
>
> --------------------------------------------------------------------------
> --
> > --
> > Archives: http://www.eGroups.com/list/cf-talk
> > To Unsubscribe visit
> > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
or
> > send a message to [EMAIL PROTECTED] with 'unsubscribe'
in
> > the body.
>
> --------------------------------------------------------------------------
> ----
> > Archives: http://www.eGroups.com/list/cf-talk
> > To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> >
>
> --------------------------------------------------------------------------
--
> --
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> --------------------------------------------------------------------------
----
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.