but then it's not a "dir" it's a "path" to a "dir". should it then be called "imagesdirpath"? ugh. what happens when you've got Xmas images -- will one then have to do: imagesdirpath and Xmasimagesdirpath ? That's why I don't advise it. Keep it simple and to the point.
<cfset imagesdir = "images/"> <cfset Xmasimagesdir = "images/Xmas/"> I just find it easier to read these very quickly and know exactly what they mean. It also means I can pick and choose using a common "near the top level" images dir as well as circuit-specific images dirs, rather than having to re-write definitions and be thinking "ok what does this one mean when i'm in THIS directory?" Personally, I find it easier to have very simple definitions in the top-most fbx_settings files, ones that I can use over and over again without having to think about what they mean. For Patrick only: "the sky is green." ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 03, 2002 8:38 PM Subject: RE: images directory > > John Quarto-vonTivadar wrote: > > probably better would be to variable-ize the "images" > > directory pointer: > > <img src="#fusebox.rootPath##imagesdir#something.gif"> > > > > where you set images dir in the topmost fbx_settings as in > > <cfset imagesdir = "images/"> > > > And better yet: > > <cfset imagesdir = ="#fusebox.rootPath#images/"> > > Patrick > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
