Thanks for your response. Not sure what IIRC means?
The circuits file handles creating the circuit-to-directory mapping structure. The real heart is that fbx_Fusebox_XXX file-set. I loathe to change that behavior. An observation about FB3: There is resonable user-documentation, but no analyst documentation. Thus some of the design intents can be lost. The nice thing is I can easily change how it works, but the danger is I don't know why it was built that way. I have been using FB for CF and PHP for a while. Generally I am pleased with the integration ease. Most of what I end up building rarely needs that MVC overhead so the hub-n-spoke fusebox ideas is OK. I have posted this on the fusebox.org forums site, but I usually have to troubles asking the correct question the first time. jack -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of S. Isaac Dealey Sent: Friday, February 28, 2003 5:24 PM To: [EMAIL PROTECTED] Subject: Re: Fusebox 3 question on fbx_fusebox_XXXX IIRC the fbx_fusebox_xxx file has already created the _fb and fusebox structures by the time it includes the fbx_settings files, so in order to change the attributes.fuseaction variable you have to do this before the variable is coppied into those structures... I haven't ever tried to do that before, and in all honesty I haven't been doing any Fusebox work on my own recently (occasional client work), but you might try making that change in the fbx_circuits.cfm file. I realize that's probably going to feel as wrong as editing fusebox.fuseaction, but if your attributes.fuseaction value is changed, then it has the potential to change the circuit also since that's the first half of the dot-delimited list variable. hth s. isaac dealey 954-776-0046 new epoch http://www.turnkey.to lead architect, tapestry cms http://products.turnkey.to tapestry api is opensource http://www.turnkey.to/tapi certified advanced coldfusion 5 developer http://www.macromedia.com/v1/handlers/index.cfm?ID=21816 > Per the script doumentation: > Section Seven includes the root fbx_settings.cfm file. > Section Eight massages attributes.fuseaction and begins > the aliased lookup > process. > Section Nine includes nested fbx_settings.cfm files > top-to-bottom. > ----------------------- > I am wanting to override a fuseaction based upon saved > values. > I noticed that when I tried to include an override to > attributes.fuseaction, > it would only work > in the main circuit. > When down in the circuit list, I have to override > fusebox.fuseaction. Which > doesn't feel right. > (Perhaps not knowing what should be public/private here is > the source of my > "bad feeling about this".) > Now I can used the isHome/isTarget circuit section in the > fbx_Settings file > to do the override in a (mostly) controlled manner. My > goal is to write no > code that cannot stand on its own circuit. Each > sub-circuit should be in > control of deligating its behavior. Or perhaps another > way of saying this: > the circuit closest the the destination should make the > call. > Here is an example, imagine a section that can open to > display information > in different formats; say calendar, sorted task list, gant > chart. I can > used a client-side variable to store the users default > view formation (in > the form of a fuse action.) When I enter that circuit > with an > "default-action" I want the circuit to do whatever the > users-default circuit > is. > I have used FB3 to build up a simple but broad set of > applications. FB3 > acts a the glue that binds them together. > This way I can reuse these pieces elsewhere or even by > themselves. As most > to the appications are indenpendent of each other, it > allows me to test > easily and cut down on the possibility of interaction. > So...all of that said: What problems could I be getting > into doing this > solution? AND > Is there a better way to do this in the FB3 framework.? > AND So far most of > my work in only two levels deep, anyone have any example > that get deep? > thanks in advance, > a confused jack-hopper > ----------------------------------------------- > To post, send email to [EMAIL PROTECTED] > To unsubscribe: > Send UNSUBSCRIBE to [EMAIL PROTECTED] > To subscribe / unsubscribe: http://www.dfwcfug.org ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To unsubscribe: Send UNSUBSCRIBE to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To unsubscribe: Send UNSUBSCRIBE to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org
