RE: Simple question on passing attribute.fuseaction into nested fusebox

[BORKMAN Lee]

Hi Jerzy, there are a number of sample apps at various locations, including Hal's site and bjork.net, but you can find links to most of them at www.fusebox.org.   As for the details of the older XFB code, the standard answer is  "I'll help you out when I get a moment, but right now I can't exactly recall the finer points, because I don't use it every day, or even every month.  If you were asking about FB3 then I'd probably have the answer sitting hear at the fron on my head."   But I do recall the faTranslated flag.  It's there to ensure that the lower-level nested circuits do not attempt to re-translate the already-translated fuseaction.  So the top CF_nesting tag does the translation, and sets faTranslated to true.  Does that make any sense? (I hope I got that right).   See ya round. You'll love FB3,   LeeBB -----Original Message----- From: Jerzy Kalat [mailto:[EMAIL PROTECTED]]   Any small FB3 application, where I could go through the source code?   And Yes :-) I would like to know what a heck was going on with this code. Also I could not understand reason of faTranslated variable in index.cfm fimes, as I did not see passing it as parameter, so it is always equal to deafaul value of  False.    ----- Original Message ----- From: BORKMAN Lee   I believe that that tutorial is an early example of XFB (eXtended FuseBox), which has now been superceded by FB3.  I'd suggest you don't try too hard to figure out what's happening in XFB, as all of that has been much simplified and tightened in FB3.  I would look at a simple non-nesting FB2 app first, then go straight to FB3.   But if you are really keen, let me know ;-)   -----Original Message----- From: Jerzy Kalat [mailto:[EMAIL PROTECTED]] Hi,   I am new into FB and we did not install FB into CF server yet, so all I can do is to go through example source.   I am looking at SimpleContactManagerFB, which I took from www.halhelms.com/OnlineCourses/BasicFusebox   In the home application index.cfm, the default attributes.fuseaction = "usr.home", after applying mapping from Circuits.cfm, attributes.fuseaction = "SimpleContactManagerFB.UserManager.home" and after removing the first element it become attributes.fuseaction = "UserManager.home".   Then we are redirecting into nested fusebox as follow: <cfinclude template="UserManager/index.cfm"> So far everything is clear.   My questions are: 1. Are we passing into UserManger/index.cfm value of attributes.fuseaction? 2. If yes, something does not make sence as the value of attributes.fuseaction is "UserManager.home", but I think it should be "home" only.   I think I am missing something here :-(   Any hints?   ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================ IMPORTANT NOTICE: This e-mail and any attachment to it is intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it.