at the time, there had to some place to put a default fuseaction. One argument is that it should be in the fbx_settings file of the root because, after all, that is where things that are application-wide should be set. The other argument is that it should be put in the index.cfm before the core file is loaded -- that let's fbx_settings be loaded at the same time other ones are but shoots it in the foot as far as being a "configuration"-type file. This is a very delicate subject since there are very good arguments on both sides. I think one might well argue for a single "configuration" file at the root of the app, distinct from the fbx_settings which would refer only to the root circuit *as a circuit*. Definitely something for the standards committee to bat around and experiment with.
> Question: why does fbx_circuits come before fbx_settings? > > Here's my dilemma: I have gotten into the habit of creating a structure that > contains all of the variables that are needed for the current request. Most > are constants, but some may change depending on the nature of the request. > with the Techspedition core file, this takes a double approach. The fbx_settings file is loaded once in its usual place. That takes care of loading the default fuseaction. Then when the rest of the fbx_settings file are loaded that file is loaded again so that any fuseaciton in the FuseQ can act the same way regardless of whether it was called in teh FuseQ or called independently as in "standard" fusebox. Because of that you could do a test in your top-level fbx_settings file that only does the stuff you mention that you like to do on those occasions when the fbx_settings file is called that very "first" time, or on those occasions where it's called in a true "circuit-ish" way. Since all of your FB3 standard code will run under the Techspedition core file right outta the box, it's all upside -- you get to do everything you would get to do with the standard core file, plus a whole lot more. ==^================================================================ 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 ==^================================================================
