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]
