I'm not sure, maybe this is exactly the point. I'm referring to situations
like this nested circuit thing below....
I guess I'm just looking for a solid anchor to stand on when referencing up
or down through the structure...
circuit1 -- index.cfm (1)
|--blocks (1) dsp_something_for_wholepage.cfm
|--actions (1)
|--queries (1)
|--images (1)
|--circuit2 -- index.cfm (2)
|--blocks (2) -- dsp_wholepage.cfm
|--actions (2)
|--queries (2)
|--images (2)
|--circuit3 ... ad nauseum
so I <cfset #attributes.fuseroot# = "/circuit1"> ... cool
so now, I'm down in index.cfm(2) and I want to cfinclude a dsp file from
blocks (2)... and I want it to get some image from images(1) or include some
static text from blocks(1)... where am I? I *was* in index.cfm(1) and I
cfinclude'd my way into index.cfm (2). index.cfm(2), by extension, wants to
execute the fuseaction like <cfinclude template="blocks/dsp_wholepage.cfm">
... but this is all happening *within* index.cfm(1)! right? The way I've
referenced it, I'd think that dsp_wholepage.cfm lives in blocks(2) and not
blocks(1)...
to further complicate it, when I do include dsp_wholepage.cfm (from w/i
index.cfm(2) from within index.cfm(1)), I want to tell it another hunk of
code to be cfincluded into itself... one that actually *does* live in
blocks(1)... so now I'm saying to get that dsp file from "../../blocks" ..
should I be saying #attributes.fuseroot#/blocks to reference items in
blocks(1) and #attributes.fuseroot#/circuit2/blocks for blocks(2)? does it
matter "where I am" when I say it? my head is going goofy over this...
I know this is lame and it should be *so* simple... why can't I get it?
I'm about ready to hang up my keyboard over this lameness of mine. Maybe I
just need a refersher in the basics of mapping.... maybe this has nothing at
all to do with FB or nested anything.
going to cry...
Peter
~~ -----Original Message-----
~~ From: Jason Lotz [mailto:[EMAIL PROTECTED]]
~~ Sent: Wednesday, September 13, 2000 1:21 PM
~~ To: '[EMAIL PROTECTED]'
~~ Subject: RE: Path Of Enlightenment
~~
~~
~~ Peter,
~~ I don't think I am understanding your question correctly. What are you
~~ trying to do that you can't do with #Attributes.Fuse_Root#?
~~
~~ Jason
~~
~~ -----Original Message-----
~~ From: Peter Terhorst [mailto:[EMAIL PROTECTED]]
~~ Sent: Wednesday, September 13, 2000 12:28 PM
~~ To: [EMAIL PROTECTED]
~~ Subject: Path Of Enlightenment
~~
~~
~~ There was once a time when I thought I had a handle on this web
~~ application
~~ development thing.... sometimes I do have to wonder though, when
~~ seemingly
~~ simple things defy my understanding. I hope that someone is
~~ willing to help
~~ me understand this bit of trivia.
~~
~~ I've always used relative paths to my cf templates .. hell..
~~ before fusebox,
~~ my directory structures were nearly irrelevant - but now, well into the
~~ bardo of fusebox, the whole structure becomes clouded - this traveler
~~ becomes confused as to what hunk of code is actually in control
~~ at any given
~~ moment, which makes knowing where my files are all the more difficult.
~~
~~ I'm writing my first application with nested fusebox circuits
~~ and although I
~~ feel I have the basic flow of the thing down, I am repeatedly hitting on
~~ "Missing Include"'s and references to missing this' and that's that seem
~~ like they are where they should be.
~~
~~ Can someone please tell me:
~~ 1.) What paths to virtual directories do I need in my web server?
~~ 2.) what mappings do I need to find my cfincludes?
~~ 3.) what variables should I be defining (and redefining at sub-circuit
~~ levels) so that I can find "myself" and my place in the
~~ directory universe?
~~
~~ can code from one circuit easily access code from a "higher or lower"
~~ circuit plane of existence?
~~
~~ I'm obviously trying to avoid the dreaded "../" and hellishly long path
~~ names tied to my image src's, links and form actions... is there
~~ some simple
~~ primer I may discover that lets me see the light and achieve a meaningful
~~ and lasting hierarchical nirvana?
~~
~~ please, kind guru's - enlighten me.
~~
~~ pts
~~
~~ -----------------------------------------------------------------
~~ -----------
~~ --
~~ To Unsubscribe visit
~~ http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/f
usebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
