To answer a bit of your question:
If I see 'Rules.MyFuseaction' in the fbx_switch file, that doesn't seem to help me know that that request has to do with some aspect of administration?? I usually name my subcircuits with a name that gives me the path, so in your case, I would use: <cfset fusebox.Circuits.adminRules="myApp/Administration/Rules"> HTH, Kathryn -----Original Message----- From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Friday, April 19, 2002 10:35 AM To: [EMAIL PROTECTED] Subject: still a bit confused Hi All, I am still somewhat confused... This example is from bombusbee.com and is in reference to the fbx_circuits file: ============================================================ Example The following is a sample of the code in a fbx_Circuits file: *<cfset fusebox.Circuits.Home="myApp"> *<cfset fusebox.Circuits.Admin="myApp/Administration"> *<cfset fusebox.Circuits.Rules="myApp/Administration/Rules"> *<cfset fusebox.Circuits.Front="myApp/FrontEnd"> This allows all references to specific folders to be made using aliases. To call the Fuseaction named 'myFuseaction' in the folder myApp/Administration/Rules, you would call the index.cfm file as follows: index.cfm?fuseaction=Rules.myFuseaction ============================================================ Now in my fbx_switch file, i would handle this request...how? LIke this: <cfcase value="RUles.MyFuseaction"> <!--- includes here ---> </cfcase> THis is why I am confused: This isn't clear to me: "To call the Fuseaction named 'myFuseaction' in the folder myApp/Administration/Rules..." I thought fusactions 'lived' in the fbx_switch file. That is to say, fuseactions are comprised of various cfm files which handle some specific task, which is a subset of a larger grouping such as a login app, or registration app(which would be a circuit). Within the fusactions are the atomic elements(files) which when grouped, perform a certain task related to the larger app(or circuit). So how is it that a fuseaction is in a folder somewhere?? I can see that all the atomic level files related to the "login" app would be in one circuit, perhaps name, "Login". But, I dont see how the fuseaction is in the folder as the bombusbee sample describes. ALso, in a complex application, where is the logic in using the aliases to name circuits? If I see 'Rules.MyFuseaction' in the fbx_switch file, that doesn't seem to help me know that that request has to do with some aspect of administration?? I know I am way off here and I just need someone to turn the light on for me. Tell me what I am missing :) Thanks! bidllc ==^================================================================ 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 ==^================================================================
