On directory choice, we're using the same paths for CFIMPORT as we're using for components e.g.
<cfimport taglib="/com/ourcompany/ourapplication/somemodule" prefix="somemodule" /> You need to get that kind of directory structure finalised for your CFCs anyway (you're driven in that direction when you use "extends"). Andy --- "Barney Boisvert" <[EMAIL PROTECTED]> wrote: > The static path issue is a PITA, in my opinion, although it's a perfectly > reasonable to do it that way from an implementation standpoint. In fact, > you pretty much have to do it that way. CF does a great job of hiding a lot > of those details from you, so when they shine through, they really stand > out. > > They do make modularization a lot nicer though, as long as you take care not > to reorganize your directories after the fact, or at least do it carefully > with search and replaces in between. > > --- > Barney Boisvert, Senior Development Engineer > AudienceCentral > [EMAIL PROTECTED] > voice : 360.756.8080 x12 > fax : 360.647.5351 > > www.audiencecentral.com > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Behalf Of Nathan Dintenfass > > Sent: Tuesday, July 22, 2003 11:05 AM > > To: [EMAIL PROTECTED] > > Subject: RE: [CFCDev] general thoughts on cfimport? > > > > > > I have been using CFIMPORT heavily of late and had no problems, though I > > have not done any heavy load testing around that issue (but since it's a > > compile-time issue I very much doubt there are any real performance > > implications). > > > > The one issue I've run into is that since CFIMPORT cannot be loaded with a > > dynamic path you end up potentially have issues if you want to reorganize > > your code base. This is really a minor problem, especially since a global > > find/replace would take care of it in most cases. > > > > I wish you could import CFC packages as well, perhaps with syntax like: > > > > createObject("component","prefix:component"); > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Behalf Of Robby L. > > > Sent: Tuesday, July 22, 2003 10:51 AM > > > To: [EMAIL PROTECTED] > > > Subject: [CFCDev] general thoughts on cfimport? > > > > > > > > > I know this isn't heavily related to cfcs, but I thought I would > > > ask to get > > > the general vibe. > > > > > > My latest application is heavily based on cfimport. I'm using it > > > for general > > > ui, display, forms, etc but I wanted to see if there was any > > > heavy downside > > > to it that would cause concern, now or down the road. > > > > > > Just trying to see if there is something out of hindsight that > > will cause > > > headaches tomorrow. > > > > > > Cheers > > > Robby > > > > ---------------------------------------------------------- > > You are subscribed to cfcdev. To unsubscribe, send an email > > to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' > > in the message of the email. > > > > CFCDev is run by CFCZone (www.cfczone.org) and supported > > by Mindtool, Corporation (www.mindtool.com). > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.501 / Virus Database: 299 - Release Date: 7/14/2003 > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email > to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' > in the message of the email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported > by Mindtool, Corporation (www.mindtool.com). ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
