I'd only be guessing, but I think most of us put the core files in our top directory, 
ie our home circuit, and leave them out of the circuits underneath.  Of course, 
sometimes you want to develop a small circuit independently, in which case, it needs 
the full set of files.

Just remember, if you want a circuit to function stand-alone, it needs ALL of the 
files.

And regarding FB2  versus FB3, my own view (often controversial) is that you should 
try implementing your own simple FB1 or FB2 app before proceeding to FB3.  FB3 does so 
much of the hard work for you that you might wonder what is going on under the hood.

So I'd take a look at FB2.  Don't worry too much about the detialed implementation of 
FB2, but understand the basic high-level concepts:

  a.. Break an app into high-level functions (fuseactions/recipes)
  b.. Break the high-level functions into low-level pieces (fuses/ingredients)
  c.. Use a central switch statement to implement the fuseactions/recipes.
  d.. Don't let your fufes/ingredients call each other.
  e.. Copy all input parameters to a single scope.
  f.. Capture the output of your fuseactions into a temporary variable so you can 
separate the execution order from the diplay order.
All of these concepts are as true in FB3 as they were in FB2.

See ya,
LeeBB

----- Original Message ----- 

  From: [EMAIL PROTECTED] 


  Hi Lee,

  Thanks for the reply!

  I think what confused me a little was the tutorial on the halhelms site. 
   He took the core FB files and renamed it to suit the type of ciruit he 
  was building(UserManager).  It would seem that a more general title 
  would be more appropriate place to house the 'core' FB files.  
  Logically, it would seem like these core files should reside in a 
  separate folder and then individual circuits be placed in different 
  folders.  Is this the approach fro FB apps?  If not, what are the best 
  practices in this regard?  

  Thanks!
  Lee Borkman wrote:
  > Hi B,
  > 
  > Generally, the only files you need in a circuit are:
  >   a.. fbx_settings.cfm
  >   b.. fbx_switch.cfm
  >   c.. fbx_layouts.cfm
  > If you want a circuit to be the home circuit, then you need to add:
  >   a.. fbx_fusebox30_CF50.cfm (or whatever version you need)
  >   b.. fbx_circuits.cfm
  > All of these files can or should be changed to implement your 
  > application except the FB3 core file (ie., fbx_fusebox30_CF50.cfm or 
  > equivalent).
  > 
  > Within each circuit, the fbx_switch will usually define all of your 
  > fuseactions, which will actually be implemented by cfinclude-ing small 
  > fuses.
  > 
  > And if you're worried about "circuits vs fuses", just remember this:
  > Application -> Circuits -> FuseActions -> Fuses
  > Hoping that helps some,
  > LeeBB
  > 
  > ----- Original Message ----- 
  > 
  >   From: [EMAIL PROTECTED] 
  > 
  >   Hi All,
  > 
  >   I am really interested in understanding the fusebox methodology, but I 
  >   am getting a little hung up on the "circuits" vs. "fuses" and what files 
  >   
  >   are required for each.
  > 
  >   I downloaded the core FB 3.0 files and checked out the presentation that 
  >   
  >   build the simple USerManager app.  Now, is the UserManager app 
  >   considered a 'circuit'? If so, If I were to create another 'circuit' to 
  >   handle 'Contacts' for example, would I need to copy all those 'core 
  >   files' into another folder named 'Contacts' or is only one copy of the 
  >   core files required per entire FB application?  
  > 
  >   Also, I bought the 2.0 white papers last summer, but just never got 
  >   around to using/reading them, as I just had no time.  Now, is there a 
  >   similar document for 3.0, or is it just the one that exists on 
  >   fusebox.org?  3.0 seems on first glance to be a good bit different than 
  >   2.0, so I am wondering, would it be best to not read/study the doc I 
  >   have. 
  > 
  >   Finally, the 'fusedocs' is there a way to expedite their creation for 
  >   each template? And is the 'fusedoc' required?
  > 
  > 
  > 

  

==^================================================================
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
==^================================================================

Reply via email to