Since I do all the owrk on my sites, and I am heavily into graphics. I see
Fusebox as a great way to seperate te code from the graphics, and if I need
to handle any javaScript for any graphic function, pure clientside coding,
the Fusebox DSP_xxx.cfm is perfect, I don't have to worry about getting lost
in server side code, and I only have to worry about the one page or sections
of pages I am working on. So I don't see why this is a concern, all you do
is just give your graphic designers the template files with the fusedoc info
in them,and go over with them the layout of the site and they do the rest
with the dsp tags, and if any server side codeing needs to be done, just
have the cf developer do the adding of the serverside when teh graphic
designers are done.
----- Original Message -----
From: "Shawn Regan" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Friday, December 08, 2000 11:02 AM
Subject: RE: Decision
> I not sure why a graphic designer would take a bit to "get" fusebox. Can
you
> explain more on that point? My view is that graphic designers don't even
> need to know the code at all.
>
>
> Shawn Regan
> [EMAIL PROTECTED]
> Cold Fusion Developer
> Pacific Technology Solutions
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 07, 2000 3:03 PM
> To: Fusebox
> Subject: Re: Decision
>
>
>
> Chris,
>
> I would wholeheartedly recommend that your group adopt Fusebox for your
> Intranet. I have a few concerns about FuseBox on public sites (although I
> haven't come up with a better idea ... so I use FuseBox) but I think that
> FuseBox is ideal for internal stuff.
>
> The downsides to Fusebox that I see are: added complexity to visual
design
> and search engine friendliness of URLs. It does take a while for some
> graphic designers to "get" FuseBox. Most Intranets have less visual
design
> than public marketing sites anyway and there are certainly other folks on
> this list who have created visually appealing FuseBox sites. An Intranet
> probably won't need any sort of search engine coverage so that shouldn't
be
> an important factor.
>
> The benefits of code reuse, greater organization and 'transparency' of
code
> and improved team development make Fusebox a terrific methodology to use.
> Its not the only way to go, but if you don't have a significantly better
> solution, Fusebox is definitely the best way.
>
> regards,
> Kevin
>
> --------------------------
> Kevin Marshall
> Certified ColdFusion Developer
> eCalton.com, Inc.
> Vero Beach, FL
> www.ecalton.com
> [EMAIL PROTECTED]
> 561.569.4500
>
>
>
>
> CAlvarado@tma
>
> nage.com To: Fusebox
> <[EMAIL PROTECTED]>
> cc:
>
> 12/07/00 Subject: Decision
>
> 11:52 AM
>
> Please
>
> respond to
>
> fusebox
>
>
>
>
>
>
>
>
> Hello All,
>
> I am pretty new to the Fusebox list but have been working with Cold Fusion
> since version 1.5 (ahh the good ole buggy CGI days)
>
> The company I just went to work for has a pretty nice CF setup. CF Server
> on
> Sparc Solaris, and an Oracle backend. I am effectively the lead developer
> and we are completely retooling the Intranet. The question has risen
> whether
> we should instantiate some sort of standardized methodology such as
> Fusebox.
> After the research I have done I am pretty much convinced that we would
> benefit from this methodology. My question is (and this comes from my
> supervisors as well), is what are the downsides (if any) to Fusebox? I
have
> already given them my thoughts on the upsides based on my reading / common
> sense. Does the fact that the Fusebox methodology seems to inherently
> generate the use of more .cfm files than 'normal' on the server create any
> kind of performance issues?
>
> Thanks for any and all help.
>
> chris.alvarado
> cold.fusion - developer
> [phone] 512.794.6563
> [email] [EMAIL PROTECTED]
> [web] http://www.tmanage.com
>
>
> Privileged/Confidential Information may be contained in this message. It
is
> not for use or disclosure outside TManage without a written proprietary
> agreement. If you are not the addressee indicated in this message, or
> agent
> responsible for delivery, you may not copy or deliver this message to
> anyone. Please notify the sender as soon as possible and immediately
> destroy this message and its attachments entirely.
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
