On 4/29/05, Dave Merrill <[EMAIL PROTECTED]> wrote: > If you want components in various physical locations to inherit from some > app-specific classes, where would you put those ancestor classes physically?
Wherever you what. You can use mappings or custom tag paths to make the ancestors accessible: child extends="path.to.ancestor" So either /path maps to a directory that contains to/ancestor.cfc or you have a custom tag path that for the directory that contains path/to/ancestor.cfc. -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
