> All the examples I have seen either have a basic > template with dynamic content added via #Fusebox.layout#?
David, actually, what happens is that the fuseaction being executed generates *content* only. Fusebox does a good job of helping you separate content generation from layout generation In the example you asked about, this would be displaying the actual login form. Then, after the fuseaction is complete, the fusebox core file checks the file fbx_Layouts.cfm to see if it is supposed to apply any layout files. If so, it does -- the layout files will have the variable #fusebox.layout# somewhere in them which represents all of the content generated up to that point. Then the core file goes up one directory level and checks for layout again, and so on until it gets to the root of the application. So the more general some layout is for you, the "higher" in the directory structure is the layout file in which you will have it generated. Since the layout is "wrapped" like a birthday present from the inside out (or like a russian doll, picture attached), you get to determine what sort of layout is generated *AFTER* the content of the fuseaction is generated, even though that layout may appear to the end user to come *BEFORE* the content -- such as a logo on the top of the screen or a copyright notice on the bottom of the screen. For some detailed examples of how to do layout, you can review the Colored Layouts app I wrote for the FB3 release, which is at fusebox.org. You can also look at Hal Helms' "Grandparent" app which uses a family metaphor. But if you happen to be from West Virginia, then don't use the family metaphor since FB3 doesn't allow multi-aliasing of circuits as 'Sister' and 'Wife' . :) (that was just a joke). There will also be a book out on FB3 at the end of May, and another one at the end of June; you can read more about both of them elsewhere on this list as those dates draw closer. If you are located near Toronto there is a large conference coming there the first week of May called CF-North; it's the second largest CF conference of the year, and likely the second-largest Fusebox conference of the year as well. GO if you can (www.cfnorth.com), there will be a Open Methodology presentation as well as a Beginner's Fusebox session that you will find useful and by then you will likely also be ready for a few advanced topics here and there. hope that helps, ----- Original Message ----- From: "David Grabbe" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, April 14, 2002 11:36 AM Subject: Newbie Q: Layouts and display files > Hello all, > > I'm BEGINNING to understand the basics of FB (3), but am stuck on the right > "fusebox approach" to handle a situation. > > The website I am working on has a central template which will be the basis > of every page. When the site first comes up, it will display this template, > and in one section (table cell) will be an area for a current user to enter > his/her username and PW. But this is the only time this dsp file should be > displayed. So how do you define and manipulate which dsp files are included > at different times? All the examples I have seen either have a basic > template with dynamic content added via #Fusebox.layout#? Also, how are > layout files and display files related? > > TIA, > David > > ==^================================================================ 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 ==^================================================================
