My gut reaction without seeing any of your code is that if you need different navigations for different fuses, they might really be two different circuits. This is especially true if you're using navi1 and navi2 in multiple places, i.e. three fuseactions use navi1 and four use navi2. Then each new circuit would have it's own layout files (one with navi1, the other navi2), and both would be subcircuits of another circuit who's layout file contains all the HTML common to both circuits.
Pete -- Pete Krueger [EMAIL PROTECTED] Alexander Zuraj wrote: > ...got that! But where do I put the logic for different layouts? Let's > say if I want a different menu for another fuseaction (in the same > circuit...? > > ...in FB2 my fusactions looked something like this: > > <cfcase value="action1"> > <cfinclude template="blocks/dsp_navi1.cfm"> > <cfinclude template="blocks/dsp_content1.cfm"> > </cfcase> > <cfcase value="action2"> > <cfinclude template="blocks/dsp_navi2.cfm"> > <cfinclude template="blocks/dsp_content2.cfm"> > </cfcase> > > ...in FB3: Do I have to provide a variable from my fbx_switch file, > that tells the layout file which menu to display? ...or what do I do? > > > > Erik Voldengen wrote: > >> dsp files should simply contain display code. They can contain HTML >> or anything >> >> else you want them to contain. The idea is to separate display code >> from action >> >> code. >> >> >> >> All output from your application is saved to a variable named >> fusebox.layout. >> >> >> Layout files are specified in the fbx_layouts.cfm file. This is the >> file the fusebox >> >> API includes after all the code has been run. In the most simple >> example, >> >> your site has a single layout file, containing a header and footer. >> This file also >> >> evaluates that fusebox.layout variable. So it'd look like: >> >> >> >> <html> >> >> <body> >> >> #fusebox.layout# >> >> </body> >> >> </html> >> >> >> >> So layout files mean you don't need to put a header and footer in all >> your dsp_ files. >> >> But they can still contain anything you want them to. >> >> >> >> If you would like to look at some really simple sample code, you can get >> >> it at http://www.erikv.com/downloads.html >> >> >> >> -Erik >> >> >> >> -----Original Message----- >> From: Tom Schreck [mailto:[EMAIL PROTECTED]] >> Sent: Thursday, May 02, 2002 9:30 AM >> To: [EMAIL PROTECTED] >> Subject: dsp_XX files vs layout files >> >> I?m well into developing my first major FB3 app and need some >> clarification on dsp_XX files and layout files please. My >> understanding is the layout files govern the output to the browser, >> where as the dsp_XX files generates the output that will be >> ?given? to the layout file to display as appropriate. I?ve read >> somewhere >> the dsp_XX files should not have HTML, the layout files should have >> HTML only. My approach has been the dsp_XX page produces a result >> that will be displayed somewhere in the layout page. The result >> almost always is a HTML table containing data produced by the fuses >> associated to the fuseaction. The result is ?given? to the layout >> page to be displayed using #fusebox.layout# variable. Is this >> correct? If the dsp_XX file is not suppose to have HTML markup, >> then the layout files will get bloated, right? >> >> >> >> Thanks - >> >> >> Tom Schreck >> >> 817-252-4900 >> >> [EMAIL PROTECTED] >> >> >> I have not failed. I've found 10,000 ways that won't work. >> >> >> - Thomas Edison >> >> >> > > -- Pete Krueger Web Applications Programmer University of Maryland University College [EMAIL PROTECTED] ==^================================================================ 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 ==^================================================================
