You should replace my SiteComposer.Globals.cfComponents.content.content package with the appropriate package name.  Here's an example:

 

File path:

D:\inetpub\wwwroot\codebase\sitecomposer\globals\cfcomponents\content\content.cfc

 

SiteComposer is a ColdFusion mapping to D:\inetpub\wwwroot\codebase\sitecomposer folder.  Replace the '\' with '.' for each folder name and include the cfc file name minus the .cfc extension:

 

SiteComposer.Globals.cfComPonents.content.content

 

 

<cfdump

var="#oCFC.getCFCInHTML('SiteComposer.Globals.cfComPonents.content.content')

#">

 

Hope that helps.

 

Tom Schreck  - They removed the 'c's from my last name when they made the movie so I can not claim royalties :(

 

 

 

-----Original Message-----
From: Barnaby Relph [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 12:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [CFCDev] Printing ComponentDocs

 

I don't know if you saw Tom Shrek's post earlier today, so I've copied it in

here. You should be able to spider and save all the HTML easily enough. If

there's loads of CFC's you can get IE to print them all by creating a page

that links to all of them and then choose the 'print all linked pages'

option when printing. It's a bit basic, but it'll only take an hour to whip

up the scripts and might get rid of the PHB :)

 

 

 

Barny

 

 

 

Brian- try this:

 

 

 

<cfscript>

 

oCFC = createObject('component','CFIDE.componentutils.cfcexplorer');

 

</cfscript>

 

 

 

<cfdump

var="#oCFC.getCFCInHTML('SiteComposer.Globals.cfComPonents.content.content')

#">

 

 

 

This produces a HTML file.  You could augment this by using <CFDIRECTORY> to

get a recordset of CFC files then loop over the above code and for each file

capture the produced HTML using <CFSAVECONTENT> then save the HTML using

<CFFILE>.

 

 

 

Hope this helps.

 

 

 

Thanks -

 

 

 

Tom Schreck

 

 

 

----- Original Message -----

From: "John Temm" <[EMAIL PROTECTED]>

To: <[EMAIL PROTECTED]>

Sent: Thursday, March 25, 2004 5:52 PM

Subject: [CFCDev] Printing ComponentDocs

 

 

Hi

My PHB wants me to print out my documentation he can 'read' it. I think he

is more interested in _weighing_ it... but whatever.  Anyway, I am now

presented with the challenge of how to either combine all of the

componentdoc output into a nice paginated book and then print it or batch a

job to spider through each component and print it separately.

 

Anyone done this? Any PHB assassins for hire out there?

Chip Temm

Dir Knowledge Architecture

Conservation International

Washington, DC, USA

+1 202 912 1402

----------------------------------------------------------

You are subscribed to cfcdev. To unsubscribe, send an email

to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'

in the message of the email.

 

CFCDev is run by CFCZone (www.cfczone.org) and supported

by Mindtool, Corporation (www.mindtool.com).

 

An archive of the CFCDev list is available at

www.mail-archive.com/[EMAIL PROTECTED]

 

----------------------------------------------------------

You are subscribed to cfcdev. To unsubscribe, send an email

to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev'

in the message of the email.

 

CFCDev is run by CFCZone (www.cfczone.org) and supported

by Mindtool, Corporation (www.mindtool.com).

 

An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]

Reply via email to