As a negative to this positive, every CFM that wants to use this format has to have a cfimport, while cf_/cfmodule just works fine. This is a very minor negative though. Just making sure you know.
On 3/12/07, Ben Nadel <[EMAIL PROTECTED]> wrote: > CFImport allows you to create tag prefixes. You can also use a template > path (which cf_tagname does not have). I think it's a very elegant way > to group tag functionality. > > > ...................... > Ben Nadel > Certified Advanced ColdFusion MX7 Developer > www.bennadel.com > > Need ColdFusion Help? > www.bennadel.com/ask-ben/ > > -----Original Message----- > From: Jamie Jackson [mailto:[EMAIL PROTECTED] > Sent: Monday, March 12, 2007 3:39 PM > To: CF-Talk > Subject: cfimport vs. cfmodule/cf_MyTag for Custom Tag Calls > > I (think) I've seen folks recommending <cfimport> over <cf_MyTag> and > <cfmodule template="MyTag"> for custom tag calls. > > I usually use a custom tag for header/footer inclusion like this > <cf_MySiteHeadFoot ...> my body </cf_MySiteHeadFoot> > > But was wondering if there's an advantage to cfimport. (Also, does > cfimport allow cf-mapped paths now? I read that it didn't used to, at > least.) > > Can someone straighten me out as to the pros and cons of <cfimport>, > <cf_MyTag>, and <cfmodule>? > > Thanks, > Jamie > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2. Free Trial http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:272397 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
