Thank you for putting my application to the human resources of your company.
I now its true that i am a great programer with the kinds of skillz that
internet people like. I do not understand what you guys are talking about
with all thse emials. I do not think that you are my type of programmer.
Geo Cities is good, but not always good. I also like Excite. I think i might
start a programmer channel on IRC, but my friend says that i will just give
away me secrets programing. Also MR. Hopkinsp----I did get your email and I
usally dont have people pay by the hour. I do it by the websites. My charges
are really depending on how much tables and coloring.
>From: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>To: Fusebox <[EMAIL PROTECTED]>
>Subject: RE: <cfoutput>#request.variable#<cfoutput>
>Date: Thu, 30 Nov 2000 07:14:06 -0900
>
>I'm curious about this one... I mean, I'm thinking, this is an issue that I
>do think could be considered as part of the Fusebox methodology.
>
>I see four possibilities here:
>1: Apply CFOUTPUTs tersly, only around specific portions of code that need
>it
>2: Apply CFOUTPUTs around large blocks of code, which may or may not need
>it
>everywhere
>3: Apply CFOUTPUTs around the entire template, with only CFMAILs and other
>anti-CFOUTPUT functions being left out.
>4: Apply CFOUTPUTs at the index.cfm level, and explicitly escape out
>anti-CFOUTPUT tags by starting with </CFOUTPUT> and ending with <CFOUTPUT>
>to restart the CFOUTPUT string
>
>Now, lets think of it like this.... here is an idea, so I'm lookin' for
>input, advice, what-have-you...
>
>A Proposal For Structuring a Fusebox App So That Everything Is Implicitly
>CFOUTPUTted
>
>PART 1: The Index.cfm file
>You take your index.cfm, and make it look like this...
>
><CFOUTPUT>
><CFSWITCH ....>
>{all the CFCASE statements for fuseactions}
></CFSWITCH>
></CFOUTPUT>
>
>PART 2: Working with Query Recordsets
>Tell yourself and anybody concerned that they are to use <CFLOOP QUERY=..>
>instead of <CFOUTPUT QUERY=..>
>
>PART 3: Dealing with anti-CFOUTPUT code, such as CFMAIL
>Encapsulate all code by STARTING with a </CFOUTPUT> and ENDING with a
><CFOUTPUT> to restore the CFOUTPUT nest.
>
>The End...
>
>
>Alan McCollough
>Web Programmer
>Allaire Certified ColdFusion Developer
>Alaska Native Medical Center
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, November 29, 2000 5:46 PM
> > To: Fusebox
> > Subject: RE: <cfoutput>#request.variable#<cfoutput>
> >
> > ... Also, just be aware that there is a performance
> > penalty with wrapping the whole page in cfoutputs.
> > {redacted}
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
