> > 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/
Thanks for jumping in Sean, appreciate it. Both path maps and custom tag paths need to be set up in cf admin. Not that doing that is an insurmountable task of course, but is there any way to handle this that's completely self-contained in the app only? No external setup? Dave Merrill ---------------------------------------------------------- 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]
