I'm currently putting the finishing touches on an app that will be 'skinnable'. Skinnable includes not just colors and such a la WinAMP, but also layout (vert/horz menubar, left/right 'extras' pane, etc.).
I generate my menu content into a nasty collection of structs and arrays. The content doesn't depend on the page being viewed, but it is generated from a database. In each skin's files, the structs/arrays are distilled into actual HTML and JS for display. I'm running into a quandry as to where to put that code. My initial placement was in fbx_Settings.cfm. However, the menu content obviously has nothing at all to do with the application's execution, so it doesn't really belong in fbx_Settings.cfm. A friend and I were discussing it, and he suggested fbx_Layouts.cfm as the proper location. My feelings are that fbx_Layouts.cfm should be executed only after all the content is generated, and only presentation remains, but I'm lacking conviction. Really, it belongs in the same place as the app's fuses, executed during the content generation phase (after fbx_Settings and before fbx_Layouts), but there isn't any such place other than including it above the CFSWITCH in fbx_switch.cfm. I'm putting it in fbx_Layouts.cfm; is there a better solution? cheers, barneyb --- Barney Boisvert [EMAIL PROTECTED] 360-671-8708 (work) 503-267-2200 (cell) http://www.piersystem.com --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.368 / Virus Database: 204 - Release Date: 5/29/2002 ==^================================================================ 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 ==^================================================================
