Hi Tim, THanks for the reply. ALl your suggetions are appreciated. Not sure I am clear on this: ************************** Only one full copy of the core files is required, if you don't plan on calling any of your nested circuits directly. You must have a minimum of an fbx_settings and fbx_switch in each circuit directory. If you want to have a nested layout wrapped around the content generated by that circuit you must also have a fbx_layout template. **************************
When you say calling directly, you mean calling the nested circuits throug the main index.cfm file, right? I thought you had to call them this way? So does that mean you can have several individual FB apps, each hanving their own set of core files, OR call circuits directly? Doesn't the former defeat the prupose of using the FB method? Sorry, if I am confusing the issue here. Timothy Heald wrote: > Please read the inline comments :) > > > 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. > > A circuit is a grouping of like functionality. It could be compared to > a > class. A fuse on the other hand is an atomic piece of code. A template > that does one thing, and one thing only, it just does it very well. > Well > that's the goal at least. > > > 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? > > Only one full copy of the core files is required, if you don't plan on > calling any of your nested circuits directly. You must have a minimum of > an > fbx_settings and fbx_switch in each circuit directory. If you want to > have > a nested layout wrapped around the content generated by that circuit you > must also have a fbx_layout template. > > > 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. > > I was unaware that there were FB 2 white papers available. Do you mean > the > book? That aside you can purchase the white paper, and the conference > in a > box at http://www.halhelms.com/index.cfm?fuseaction=buy.shop Also on > the > FB.org site there are a lot of resources at > http://www.fusebox.org/index.cfm?fuseaction=learn.resourceList. I would > suggest getting Kathryn Butterly's excellent newbie guide at > http://bombusbee.com/index.php?fuseaction=downloads. There is also a > lot of > information on the FB 3 PHP Standard there. > > > Finally, the 'fusedocs' is there a way to expedite their creation for > > each template? And is the 'fusedoc' required? > > There are various tools and papers on how best to fusedoc your app. > Anytime you are looking for something about FB 3 I would suggest you go > to > http://www.fusebox.org/index.cfm?fuseaction=learn.resourceList first > look > around follow the links, and then if you run into something shoot us > e-mail > here. I have found that the people on this list will always go the > extra > mile (or kilometer) to help you, no matter if it's your first day, or > your > already an expert. I think you will find that the current standard and > the > supporting community will be tools that will make you a much better > developer. > > I hope this has helped you out some, and again if you have any questions > just shoot off an e-mail, and someone will be here to help. It's almost > like we have a 24 hour customer support line :) > > Tim Heald > ACP/CCFD :) > Application Development > www.schoollink.net > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > > ==^================================================================ 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 ==^================================================================
