Bidl,
It looks like you have got it right. Maybe a case of wording, but did you want a navigation menu to appear if the user is not logged in? If not, you can just leave your layoutFile = "layout_loggedInFalse.cfm" as layoutFile = "". Other than that, it looks good. -- Jeff -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 4:27 PM To: [EMAIL PROTECTED] Subject: RE: I'm on my way now, just need a quick overview on layouts Lee, What about a situation like this: I have a circuit named "Admin" which houses all actions related to the admin of the site. I would like to inlcude a list of links in the layout for this circuit that are only visible *once* the user is logged in. In this situation, is the code below an acceptable way to do this? <cflock timeout="10" throwontimeout="No" type="EXCLUSIVE" scope="SESSION"> <cfif NOT isDefined( 'Session.LoggedIn' )> <cfset fusebox.layoutFile = "Layout_LoggedInFalse.cfm"> <cfset fusebox.layoutDir = ""> <cfelse> <cfset fusebox.layoutFile = "Layout_LoggedInTrue.cfm"> <cfset fusebox.layoutDir = ""> </cfif> </cflock> BORKMAN Lee wrote: > As to your major point, bidl, to me it makes little sense to have a > child > circuit's layout *replace* the main circuit's layout, although it can > certainly be done. > > Better to create the implmentation structure of your application so that > it > actually reflects the nature of your conceptual structure, if you know > what > I mean. For example, if you have a set of circuits, each with its own > mutually exclusive layout, then, without knowing more about your app, it > looks to me as though all of those circuits are probably at the same > conceptual "level", in which case I would expect to create them all as > siblings, without choosing one of them to be the "parent". > > It's perfectly acceptable, and possibly the most common set-up, to have > the > home circuit do *nothing*. It's just a logical container (and possibly > a > global layout "wrapper") for the child circuits. > > In other words, this requirement of yours suggests to me that the > implementation structure you favour is actually at odds with the > conceptual > structure. > > Am I off the track here? > > See you, > LeeBB > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Hi there Lee (and Jeff), > > I think you've spelled it out for me with the diretion to set the home > circuit's fbx_layouts to "". That is what I needed. Does that mean that > > I can't have my main application files in a folder using one layout and > then a nested folder (containing another circuit) using a different > layout without setting the home ciruit's layout to ""? I suppose it's > no big deal to set up the application with folders on the same level, I > am just used to doing it the way I've described. > > > > IMPORTANT NOTICE: > This e-mail and any attachment to it is intended only to be read or used > by > the named addressee. It is confidential and may contain legally > privileged > information. No confidentiality or privilege is waived or lost by any > mistaken transmission to you. If you receive this e-mail in error, > please > immediately delete it from your system and notify the sender. You must > not > disclose, copy or use any part of this e-mail if you are not the > intended > recipient. The RTA is not responsible for any unauthorised alterations > to > this e-mail or attachment to it. > > > ============ ==^================================================================ 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 ==^================================================================
