or the same thing with cfinclude ?

This is how we did it in the good ol' days when you had to roll your own document output formats and use CFcontent/CFheader.

 <cfif isDefined('test')>
         <cfdocument format="flashPaper" fontembed="true">
           <cfinclude template="content.cfm" >
         </cfdocument>
 <cfelse>
         <cfinclude template="content.cfm" >
 </cfif>

Ricardo Russon wrote:
How about using cfsvecontent ?

<cfif isDefined('test')>
        <cfdocument format="flashPaper" fontembed="true">
          #content#
        </cfdocument>
<cfelse>
   #content#
</cfif>

On 6/7/05, Gareth Edwards <[EMAIL PROTECTED]> wrote:

Just a quick question.

Is it possible to put conditions around start and end tags? I've tried it and 
it doesnt seem like you can. Code example below of what I would like to be able 
to do.

<cfif isDefined('test')>
       <cfdocument format="flashPaper" fontembed="true">
</cfif>

<html>
       <head></head>
       <body>
               test
       </body>
</html>

<cfif isDefined('test')>
       </cfdocument>
</cfif>

What I need to do is allow the user to display a report/document in either 
plain html or pdf/flash paper, while still allowing (in the pdf/flash paper) 
pager headers, footers, pagebreaks, etc.

Wrapping it all up in a custom tag kind of works where generatedContent is used 
in the end tag, but stops/limits my use of headers, footers, etc.

All I can think of at the moment is have two files? but I rather not have to 
maintain two files for every document that needs to be created.

So, suggestions are welcome.

TIA
Gareth.



---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/





---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to