The issue with CFImport is something that could be solved in <CFApplication> or something like that. There is a group of people working on a solution for this issue. It's something that doesn't look apparent on the deck of the ship... but if you go below level to the Java you could understand it. (Or so I am told.)
Suggestion... create a standard library of CF files off the site root and call it something like "shared". Then put your custom tags in that directory. If that doesn't fix your issue you could use CFModule... but that should work on any sites. I create a set of tags for my apps in /share/sos and then map them with CFImport from all my apps to "sos" and call the apps like this... <sos:skin ...> </sos:skin> Or public tags in /share/public <public:myTag> And that should solve your issues. It's not exactly "how you want to do it"... but it sure works. John Farrar -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scratch Sent: Monday, December 19, 2005 6:41 AM To: [email protected] Subject: [CFCDev] CFIMPORT - Oh the pain I know this has been brought up before, but what's the deal with CFIMPORT! I just can't believe you need to specify a hard path. My apps have become fully portable, encapsulated, separated and even, some might say, beautiful - except when it comes to my CFIMPORTS! They destroy everything - but I can't go back to CFMODULE - I won't do it. Even worse than not being able use a variable for the path, is having to declare the imports on every page. So if I'm 5 includes deep and call a tag that it itself calls other tags, I have to CFIMPORT the same generic UI in each include, each TAG and each sub-tag. On some page requests my UI library is called over 10 times! Seems very inefficient to me. What are people doing? Should I just make display CFCs? Cheers, Baz ---------------------------------------------------------- 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] ---------------------------------------------------------- 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]
