If running CFMX, you could always do this as well (with CFMODULE or
CFINCLUDE):
<cfscript>
variables.iString = "#application.mapping#/testfiles/includeme.cfm";
inc_obj = CreateObject('component','include');
inc_obj.INCLUDE( iString: variables.iString);
</cfscript>
INCLUDE CFC contents:
<cfcomponent hint="I am an include" extends="<your_construct_here>">
<cffunction name="INCLUDE" returntype="any" access="public">
<cfargument name="iString" type="string" required="yes" />
<cfinclude template="#arguments.iString#">
</cffunction>
</cfcomponent>
Regards,
Phillip B. Holmes
-----Original Message-----
From: Jerry Johnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 01, 2004 10:56 AM
To: CF-Talk
Subject: Re: CFMODULE vs. CFINCLUDE
I am going to regret this, but...
We use a similar approach, and for the same reasons.
But instead of the <cf_footer> tag, we use </cf_header>. (No parameters are
passed to the close tags.)
<cf_channelHeader title="Blah">
<cf_channelContent title="" subtitle="" subscriberOnly="">
Blah
</cf_channelContent>
</cf_channelHeader>
Jerry
Jerry Johnson
Web Developer
Dolan Media Company
>>> [EMAIL PROTECTED] 12/01/04 11:49AM >>>
Our framework here uses the custom tag approach, not to imply it is the best
way to go, just what has been in use here for years. So a typical page
could be something like:
<cf_headertag title="Blah" check="Yes" userlevel="GenUp">
<cf_tableheader title="Something">
<tr><td>Blah</td></tr>
<cf_tablefooter>
<cf_button label="Back;Menu">
<cf_footer links="Yes">
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Special thanks to the CF Community Suite Silver Sponsor - RUWebby
http://www.ruwebby.com
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:185825
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
