Ah, yes, I've got it now! Just a little slow on the upbeat...

Anyway, if you place this in your myGloblals.cfm file, then #images# will
point to a directory called images below the nested fusebox:

<cfset images = "#GetDirectoryFromPath( GetCurrentTemplatePath() )#images\">

Hal Helms
== See www.ColdFusionTraining.com <http://www.ColdFusionTraining.com>  for
info on "Best Practices with ColdFusion & Fusebox" training, Jan 22-25 ==


-----Original Message-----
From: Steve Nelson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 14, 2000 1:30 PM
To: Fusebox
Subject: Re: the dot notation


Hal,

the problem Nat is having is if all requests go through the root
index.cfm file, then calling an image in a local circuit app with:

<img src = "images/localImage.jpg">

would always point to the /images directory under the root directory,
not a /images under the circuit directory.

make sense?

Steve

Hal Helms wrote:
>
> Nat,
>
> It seems to me you have two situations: one where the images are
> application-wide and the other where they are specific to a circuit app.
The
> application-wide one I do with a request.images variable set to a specific
> directory. The "local" images are just in a directory beneath the circuit
> app, so calling them is like this:
>
> <img src = "images/localImage.jpg">
>
> I'm not sure what the problem is, or am I missing something?
>
> Hal Helms
> == See www.ColdFusionTraining.com for info on "Best Practices with
> ColdFusion & Fusebox" training, Jan 22-25 ==
>
> -----Original Message-----
> From: Nat Papovich [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 14, 2000 11:52 AM
> To: Fusebox
> Subject: RE: the dot notation
>
> I got no question with using directory names instead of dots, but my real
> questions lie in the situation where someone uses purely cfinclude to call
> circuit apps. Is there anyone out there that does that? If you use
> cflocation to direct to circuit apps, or even cfmodule, I don't wanna hear
> about it - only cfincludes.
>
> As for the request.images_dir - it's a great plan because it will work
> whether you have images in the circuit, or in the root images dir, or even
> on a different server like you mention, Alan.
>
> Namaste,
>
> Nat Papovich
> Webthugs Consulting
> ICQ 32676414
>
> > -----Original Message-----
> > From: McCollough, Alan [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, December 14, 2000 7:47 AM
> > To: Fusebox
> > Subject: RE: the dot notation
> >
> >
> > I've got my images stored on a separate box, and use an
> > #request.images_dir#
> > to refer to the actual location of these guys. Its worked
> > like a champ. Fer
> > example, once upon a time the box with the images had to go
> > down for a day,
> > so I just copied the images to a different webserver, and
> > edited the value
> > of request.images_dir in app_globals.cfm. Worked slick and I
> > didn't even
> > have to restart CF or nuthin'.
> >
> > As for the dot notation and what not, I tend to avoid it. I
> > normally mark up
> > any calls for page elements as "#request.website_dir#/{the
> > subfolder}/whatever.cfm".  I've found it keeps things easier
> > to manage when
> > I'm looking for what came from where...
> >
> > Alan McCollough
> > Web Programmer
> > Allaire Certified ColdFusion Developer
> > Alaska Native Medical Center
> >
> > > -----Original Message-----
> > > From:       Nat Papovich [SMTP:[EMAIL PROTECTED]]
> > > Sent:       Wednesday, December 13, 2000 10:25 PM
> > > To: Fusebox
> > > Subject:    RE: the dot notation
> > >
> > > Well well well.
> > >
> > > > <cfset request.imagesroot="http://images.funkynat.com">
> > > > <cfoutput>
> > > > <img src="#request.imagesroot#/products/156.gif">
> > > > </cfoutput>
> > >
> > > If I'm building the products app as a standalone, I don't
> > think that I'm
> > > at
> > > http://images.funkynat.com/products. I think I'm a
> > images.funkynat.com.
> > > Requiring any given app to know where it lives in the
> > "rest" of the app I
> > > believe defeats the purpose of the dot notation and
> > cfincluding indexes.
> > > To
> > > allow an index to be cfincluded willy-nilly, it cannot rely
> > on anything
> > > outside it's own relative self. Am I right here? Can
> > someone who's built
> > > one
> > > of deez suckers step up and explain?
> > >
> > > Namaste,
> > >
> > > Nat Papovich
> > > Webthugs Consulting
> > > ICQ 32676414
> > >
> > >
> > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to