I think that's what CFObjects does. Doing so would basically
turn fusebox into an OO implemenation of CF (esp. if combined
with the StatefulCustomTag[1] theory). I'm not a proponent
of creating classes in CFML (that's why we have CFObject,
CFServlet, etc.) but anyway here's 90% of the solution:
<cfdefaultcase>
<cfinclude template="../index.cfm">
</cfdefaultcase>
Patrick
[1] http://www.meta-magic.com/cgi-bin/fusewiki?StatefulCustomTag
> -----Original Message-----
> From: Ken Beard [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 23, 2001 1:20 PM
> To: Fusebox
> Subject: inheritance of fuseactions
>
>
> cfset in the app_locals/app_globals (myGlobals, whatever) provides for
> inheritance and overriding properties... but what about inheritance and
> overriding of methods (fuseactions)? any good ideas on how?
>
> -----------------------------------------------------
> Ken Beard
> Manager, Application Development
> Stone Ground Solutions
> 5100 West Kennedy Blvd, Suite 430
> Tampa FL 33602
> 813.387.1235 voice
> 866.767.4051 toll free
> 813.387.1237 fax
> www.stoneground.com
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
