Evan, Are you wanting to know about wireframes or layouts? We normally use wireframes in the beginning of a project to discover more about what the client wants by giving them a clickable text-only rendition of the highlights of the application.
If you want to do layouts (processing of code AFTER all fuses in a fuseaction occurs), you can do this in a number of ways. Some people use conditional logic in their FBX_Switch.cfm file. I'm not a great fan of this, as it makes it harder to see an overall "map" of the application that we usually associate with the FBX_Switch file. With the FuseQ stuff John talked about, you do it directly in the switch like this: <cfcase value="a_fuseaction_request"> <cfinclude template="dsp_Something.cfm"> <cfset AddToQ( 'Layouts.blue AS LAYOUT' )> </cfcase> The inclusion of the words AS LAYOUT tells the Techspedition core file to run a fuseaction but to process it as a layout. Kind of a neat technique. John is putting something together to put up at www.techspedition.com. Give him a day or two to recover from the wild partying that Toronto inspired. Hal -----Original Message----- From: Evan Wilders [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 11:28 PM To: [EMAIL PROTECTED] Subject: Wireframes How would I go about using specific layouts for specific fuseactions -- or is that not a good idea? Evan __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com ==^================================================================ 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 ==^================================================================
