You're right Charlie, at the very least folks should be doing their color declarations in a file that looks something like: style.css!
I'd be curious to know if your second observation is true, does anyone have any feedback on that? I know that in most of the work I'm doing currently my .cfm files tend to be fairly small in the first place... - Calvin -----Original Message----- From: Charlie Griefer [mailto:[EMAIL PROTECTED] Sent: Thursday, February 10, 2005 12:44 PM To: CF-Talk Subject: Re: Few cfoutput Vs Many cfoutput well, for one...you now have to worry about doubling up on # signs everywhere (yes, yes, i know..i'm referring to # in hex color declarations but the presentation layer should be seperate anyway :P)... i would also think (assume?) that the larger the block of text between <cfoutput> tags, the more the cf engine has to parse...the less efficient the page execution overall. On Thu, 10 Feb 2005 12:27:25 -0500, Calvin Ward <[EMAIL PROTECTED]> wrote: > Why do you consider top and bottom cfoutputs a 'silly' thing? > > - Calvin > > -----Original Message----- > From: Adam Haskell [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 10, 2005 11:59 AM > To: CF-Talk > Subject: Re: Few cfoutput Vs Many cfoutput > > I agree top and bottum cf outputs could be as equally as silly. My > point was more to the fact I would rather that to cfoutputs littered > everywhere. I also don;t see how that could compile any > faster...noticable or not. > > Adam H > > On Thu, 10 Feb 2005 10:26:18 -0500, Charlie Griefer > <[EMAIL PROTECTED]> wrote: > > i see <cfoutput> as being similar to starting a car, and </cfoutput> > > as similar to shutting it off. > > > > I wouldn't stop/start the car at every corner (or every > > streetlight/stopsign) that I came to. > > > > Altho...I also wouldn't leave it running overnight just so I wouldn't > > have to start it in the morning (trying to keep running with the same > > analogy as it relates to a lone <cfoutput> at the top of the page and > > a lone </cfoutput> at the bottom). > > > > for your specific example, i would certainly suggest a single set of > > <cfoutput></cfoutput> surrounding the entire <select></select>. > > > > > > On Thu, 10 Feb 2005 10:17:39 -0500, Adam Haskell <[EMAIL PROTECTED]> > wrote: > > > I am sifting through some inherited code and it is littered with > > > CFoutputs everywhere... > > > For example: > > > > > > <select name="<cfoutput> #sel_name#</cfotuput> > > > <option value="<cfoutput>#sel_value#</cfoutput>"> > > > <cfoutput>#sel_text#</cfoutput> > > > </option> > > > </select> > > > > > > I figured it was done b/c somone jsut didn't know any better, but I am > > > seeing it where I would think the individual writting it wouldn't do > > > it that way. Why would anyone code like this as opposed to just > > > throwing a cfoutput at the beginig of a page and the end, assuming > > > they are ussing something other than <cfsetting> to control white > > > space. > > > > > > One co-worked claimed he did it for performance he thought it would > > > parse quiker, in CF5...I disagree. > > > > > > Adam H > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:194097 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
