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
, 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
Shannon,
In some ways you are right, but for code reuse I still believe the
custom tag is the way to go.
Say you put the code in /webroot/myIncludes/myReusableCode.cfm.
Someone working in /webroot/Application1/SubApp1/report would have to
use either cfinclude template=../../myIncludes
snip
I think components still make the most reusable choice for things like
this.
I throw all my utility type functions into one cfc and call the correct
function according to what is required, even if no input is required it
still has the desired affect of doing xyz. These don't change often so
for sharing code
in-house so I could see whatever method I choose turning into a sort of default
method of code reuse (even when not appropriate). Also, I'm thinking if I'm
really going to approach this properly I need to request a mapping to a folder
above the web root rather than simply throwing
However, my secondary concern is that we do not have a process for sharing
code in-house so I could see whatever method I choose turning into a sort of
default method of code reuse (even when not appropriate).
If that is the case, I would recommend making it a custom tag and sticking
into a sort of
default method of code reuse (even when not appropriate). Also, I'm thinking
if I'm really going to approach this properly I need to request a mapping to
a folder above the web root rather than simply throwing in a new folder and
calling it cfincludes. Mappings always turn
. cf_getMyLink relativePath=/path/to/mytemplate.cfm
environment=development / seems fairly straightforward.
From: Gerald Guido gerald.gu...@gmail.com
Sent: Tuesday, May 11, 2010 11:18 AM
To: cf-talk cf-talk@houseoffusion.com
Subject: Re: Which code reuse method
...@wanax.com]
Sent: Tuesday, May 11, 2010 12:32 PM
To: cf-talk
Subject: Re: Which code reuse method?
+1 to making it a custom tag in the server's default custom tag
directory.
Definitely a custom tag or a
cfc seem like overkill.
Custom tag is just that: a bit of code that can be called
Great tips, thanks all!
~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion
Archive:
over the place.
A cfc does seem to be going overboard to me. I like the UDF Idea
personally.
-Original Message-
From: Shannon Rhodes [mailto:shan...@rhodesedge.com]
Sent: Tuesday, May 11, 2010 10:56 AM
To: cf-talk
Subject: Which code reuse method?
I'm probably overthinking this, but I
My favourite line from that doc:
Do not use client scope.
I'm glad I'm not alone in avoiding it completely...
On 12/2/05, Dawson, Michael [EMAIL PROTECTED] wrote:
We are working on a new intranet that will locate the CFCs, custom tags
and includes, outside the web root just for this purpose.
On 30/11/05, Aaron Rouse [EMAIL PROTECTED] wrote:
I know of a couple of in house frameworks that do just this. One for
example uses a lot of different custom tags for its CMS and that CMS is
used
for 20+ sites. Instead of copying that pack of tags to each site they all
point to a common
[mailto:[EMAIL PROTECTED]
Sent: Thursday, December 01, 2005 4:17 AM
To: CF-Talk
Subject: Re: Code reuse ideas?
On 30/11/05, Aaron Rouse [EMAIL PROTECTED] wrote:
I know of a couple of in house frameworks that do just this. One for
example uses a lot of different custom tags for its CMS
: Thursday, December 01, 2005 4:17 AM
To: CF-Talk
Subject: Re: Code reuse ideas?
On 30/11/05, Aaron Rouse [EMAIL PROTECTED] wrote:
I know of a couple of in house frameworks that do just this. One for
example uses a lot of different custom tags for its CMS and that CMS is
used
for 20+ sites
/coding_standards/structure.htm
l
M!ke
-Original Message-
From: Phill B [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 01, 2005 9:16 AM
To: CF-Talk
Subject: Re: Code reuse ideas?
Sounds like this is the best thing to do. I'm pretty positive that I
will have to abstract my code a little bit more
I don't know how I missed that page. Thanks Michael
On 12/1/05, Dawson, Michael [EMAIL PROTECTED] wrote:
We are working on a new intranet that will locate the CFCs, custom tags
and includes, outside the web root just for this purpose.
MACR's best-practice document shows a common directory
mac jordan wrote:
On 30/11/05, Aaron Rouse [EMAIL PROTECTED] wrote:
I know of a couple of in house frameworks that do just this. One for
example uses a lot of different custom tags for its CMS and that CMS is
used
for 20+ sites. Instead of copying that pack of tags to each site they all
Hey every one,
I have around 9 web sites that all use copies of an original set of
code. I have converted most of the code to use CFCs which has been a
big help. I'm still having a hard time with some of the other code
that is used on all the sites.
So, I was thinking of mapping a directory on
Any one have any thoughts on this? Am I not make any sense?
On 11/30/05, Phill B [EMAIL PROTECTED] wrote:
Hey every one,
I have around 9 web sites that all use copies of an original set of
code. I have converted most of the code to use CFCs which has been a
big help. I'm still having a hard
I know of a couple of in house frameworks that do just this. One for
example uses a lot of different custom tags for its CMS and that CMS is used
for 20+ sites. Instead of copying that pack of tags to each site they all
point to a common spot that stores just one copy of them. That way when a
Thanks Aaron. Did you notice any downside to this? Anything that you
could share is helpful.
On 11/30/05, Aaron Rouse [EMAIL PROTECTED] wrote:
I know of a couple of in house frameworks that do just this. One for
example uses a lot of different custom tags for its CMS and that CMS is used
for
If you think about it, this is exactly what frameworks do. For instance, with
Mach-II you map a directory to the Mach-II framework folder, and all of your
Mach-II apps use that directory for the core files.
The disadvantage is that your shared files are just that- shared. You need to
make
Code Reuse
-- How to make a reusable component to provide more
value to customers?
Hope the topic is not OT. I'm not sure if Dr. Carma
McClure's claim that software reuse is the best
answer to the decade-old software crisis
is all that accurate. But I'm a firm believer in code
reuse, probably
Code Reuse
-- How to make a reusable component to provide more
value to customers?
Hope the topic is not OT. I'm not sure if Dr. Carma
McClure's claim that software reuse is the best
answer to the decade-old software crisis
is all that accurate. But I'm a firm believer in code
reuse, probably
25 matches
Mail list logo
