<IMHO>
Philosophically:
I think that each programmer in the team should be able
to decide what is output and what is not. It seems like
this approach would cause the developer to have to work
around the architecture instead of the architecture
supporting the developer.
example 1:
-PART 2: Working with Query Recordsets
-Tell yourself and anybody concerned that they are to use
-<CFLOOP QUERY=..>
-instead of <CFOUTPUT QUERY=..>
This does not take into consideration
<CFOUTPUT QUERY="queryName" GROUP="columName">
Technically:
wrapping potentially huge sections of code in cfoutput
has the possibility of creating not only slow performance
on the server, but also a tremendous amount of whitespace
beign pushed through the pipe to the client.
example 2:
see example 1
</IMHO>
<snip>
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...
</snip>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
