<snip>Custom tag is just that: a bit of code that can be called in a single tag, that's all. Nothing 'overkill' about it to implement for a simple computation. <cf_getMyLink relativePath="/path/to/mytemplate.cfm" environment="development" /> seems fairly straightforward.</snip>
I somewhat disagree. The easiest way to deal with a straightforward code snippet that takes no input parameters is a simple cfinclude. I can copy/paste the code directly from the page for which it was originally written, and then done. With a custom tag, there is a tiny bit extra to consider (scope issues are different, handling the lack of an end tag). It's not that it's a big deal, I'm just wondering what the advantage would be. In this case, the advantage may well be simply the need to demonstrate code reuse to other developers who may use includes inappropriately---that is a compelling case. <snip>If that is the case, I would recommend making it a custom tag and sticking it in the custom tags folder in the CF admin.That way it is avalible to everyone with out having to deal with mappings and all that.</snip> I'm unclear here...developers do not have access to the Administrator (only management), so I guess I'd need to make the case that they need to create a custom tags folder for us? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:333644 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
