Greg,
I would set the variable to the Attributes scope. I haven't gotten
friendly with that newfangled Request scope thing yet. My general rule of
thumb is that if a variable being set within an act_ file and is targeted
to be used within another act_ or dsp_ file, that variable should be set to
the attributes scope. Its a way to indicate that the variable is being
used across "boundaries" and is part of an interface.
my $.02,
Kevin
--------------------------
Kevin Marshall
Certified ColdFusion Developer
eCalton.com, Inc.
Vero Beach, FL
www.ecalton.com
[EMAIL PROTECTED]
561.569.4500
"Greg Wolfinger"
<GWolfinger@compuvi To: Fusebox
<[EMAIL PROTECTED]>
sions.net> cc:
Subject: Variable Scoping
11/14/00 02:14 PM
Please respond to
fusebox
This is a multi-part message in MIME format.
------=_NextPart_000_0007_01C04E45.4397B6A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey Guys:
I've just started to research the fusebox methodologies and have found =
them very helpful. I picked up a copy of the new book when I was at the =
developer conference last week. The only part that is really throwing =
me off is the variable scoping.
It says to use the Attributes and Request scoping for variables. Say I =
had a action file (act_nav-trail.cfm) that is used like a custom tag to =
create or append a session variable that keeps track of the users =
navigation throughout the site.
That action file spits back to the calling template (i.e. the index.cfm =
file) a variable called navTrail that is then passed to my display =
(dsp_nav-trail.cfm) file. In the action file should I set the variable =
to Caller.Request.navTrail or Caller.Attributes.navTrail or just =
Caller.navTrail?? Thanks, also if you know of any really good visuals on =
the web that helps dipict the fusebox scoping methodologies it would be =
most appreciated.
Best Regards,
Greg
------=_NextPart_000_0007_01C04E45.4397B6A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hey Guys:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I've just started to research the =
fusebox=20
methodologies and have found them very helpful. I picked up a copy =
of the=20
new book when I was at the developer conference last week. The =
only part=20
that is really throwing me off is the variable scoping.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>It says to use the Attributes and =
Request scoping=20
for variables. Say I had a action file (act_nav-trail.cfm) that is =
used=20
like a custom tag to create or append a session variable that keeps =
track of the=20
users navigation throughout the site.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>That action file spits back to the =
calling template=20
(i.e. the index.cfm file) a variable called navTrail that is then passed =
to my=20
display (dsp_nav-trail.cfm) file. In the action file should I set =
the=20
variable to Caller.Request.navTrail or Caller.Attributes.navTrail or =
just=20
Caller.navTrail?? Thanks, also if you know of any really good visuals on =
the web=20
that helps dipict the fusebox scoping methodologies it would be most=20
appreciated.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Greg</FONT></DIV></BODY></HTML>
------=_NextPart_000_0007_01C04E45.4397B6A0--
------------------------------------------------------------------------------
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.
