hi tom, i think almost all of us generate html in our dsp fuses. roger b goes to some extremes with his own fb-based architecture, which does sound interesting, but that's not the norm. the trick, though, is to only generate the html associated particularly with a single fuseaction, within that fuseaction. identify the html hunks which are common to each circuit and put those in the layout. identify the elements within the layout that vary fom fuseaction to fuseaction. one of these changing elements will be the output of your fuseaction (ie dsp files). the other chasnging elements will probably be set as variables by the fuseaction, and then used by the layout (eg, title).
that making any sense? leebb ps., excuse the one handed typing, squirmy baby in other hand. Tom Schreck wrote: > 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? > ==^================================================================ 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 ==^================================================================
