RE: dsp_XX files vs layout files

[Tom Schreck]

Hi Lee- The light’s starting to turn on now.  This is so cool.  I’ve been developing FuseBox apps for a couple of years, but I took FB2 and came up with my own approach.  I’m very impressed with FB3.   Thanks -   Tom Schreck 817-252-4900 [EMAIL PROTECTED]   I have not failed.  I've found 10,000 ways that won't work.   - Thomas Edison   -----Original Message----- From: Lee Borkman [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 9:50 AM To: [EMAIL PROTECTED] Subject: Re: dsp_XX files vs layout files   Hi Tom,   Certainly you can just have a mirror of your fbx_switch's CFSWITCH block, but I prefer to let the fuseactions in the fbx_switch provide information/data/metadata about themselves, that is then used by the fbx_Layouts to choose the appropriate layout.  Examples of the kind of metadata I'm talking about would be: priority, content-length, due-date, numberOfRecords, author, etc.   If you are going to have a one-to-one relationship between fuseactions and layouts, then the layouts may just as well be part of the fuseaction.  You are just creating a maintenance hassle by duplicating the CFSWITCH.   At all times, I ask myself "what is it about particular content, as opposed to particular fuseactions, that makes me want to use one layout or another?".  Define a set of metadata that reflects this.  Set the metadata in the fuseaction; respond to the metadata in fbx_layouts.   Have fun, LeeBB     ----- Original Message ----- From: Tom Schreck   Thanks for the feedback.  Nice to know I’m on the right track.  To set different lay_XX files in fbx_Layout, do you do another cfcase with expression set to fuseaction?    Thanks -   ...   -----Original Message----- From: Erik Voldengen [mailto:[EMAIL PROTECTED]]   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.  ... ==^================================================================ This email was sent to: [EMAIL PROTECTED]   EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bWanp4 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 ==^================================================================ ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================