Think of it as a way of documenting what custom tag directories are being
used on a certain page. It really isn't as bad as you might think. If you
put them at the top of the page you can just make it part of a new document
template. Besides, it is a lot cleaner than using <cfmodule> for custom
tags, and really makes you think about how you categorize your tag
libraries.
Paul Kenney
WebMaster, CorporateWarriors.com
916-663-1963
-----Original Message-----
From: Gaulin, Mark [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 2:26 PM
To: CF-Talk
Subject: RE: Partitioning Custom Tags for multiple code lines?
>From the docs it looks like cfimport would not work so well since it only
affects the current .cfm file, so you can't set imports up in
application.cfm and have them work on all of your pages. Too bad.
Mark
-----Original Message-----
From: Raymond Camden [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 3:42 PM
To: CF-Talk
Subject: RE: Partitioning Custom Tags for multiple code lines?
> Is cfimport new to cfmx?
Yep. You can import JSP taglibs or folders of custom tags. One of the cool
things about using it for custom tags is that you can _really_ partition
your tags, ie, instead of:
<cf_securitylogonform>
<cf_template>
etc
you can have:
<security:logonform>
<design:mainTemplate>
etc.
> Also, tried to find wishlist on MM's site but didn't have any
> luck. I was thinking that a new cfapplication attribute
> would be the way to go too.
www.macromedia.com/go/wish used to work. Anyone know the new URL?
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
