I'd recommend that you call the fuseaction in question, rather than copy the file itself.
You would do this using the <do action="circuit.fuseaction" /> verb. That way the core files will take care of making sure your dependencies are all there, and you will have very little editing to do. Even if the logic is similar but not identical it might be easier to add conditional logic to the original circuit that would expose your new functionality, rather than essentially duplicating functionality in your application. -----Original Message----- From: Mike Kear [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 25, 2007 10:52 AM To: CF-Talk Subject: Re: Fusebox - is there a trick to following the flow? Thanks for your suggestion Phillip. Actually what I am currently tasked with is duplicate part of the functionality of one circuit in a new circuit. At first sight, all i have to do is copy that circuit to a new folder, tweak the circuit.xml.cfm files a bit and change the dsp files to show the new presentation stuff since the business logic is much the same. Not identical but quite similar. However the existing circuit uses lots of other circuits - reusing code as it's supposed to. So figuring out what they all do is not easy. A fuse for example might have 6-8 <do actions, and i need to konw what each is doing in order to figure out fi they're relevant to this task or not. Or if i have to write new versions of them for this new task. And each of those other fuses are usually on the controller circuits.xml.cfm, and call the model and/or view fuses. In order to follow the flow through one fuse on my new app, I sometimes have to open 20-30 files spread out over the 46 circuits in the main site, just to figure out what is being done by what. That's my current problem. Just learning how to follow the flow of the app so I know what files I need to keep, what i need to re-write, and what dont do anything at all for this app. A quicker way to work out what's doing what would give me more sleep, more deadlines met, and a happier client. Given time, I can learn this monster easily and get the hang of it. But will the client wait that long? Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On 7/26/07, Phillip M. Vector <[EMAIL PROTECTED]> wrote: > It wasn't that steep when I tried learning it, but then again, I learned > on FB3. :) > > The idea is that you only open up 1 circuit.xml file at a time. trace > down the error that's causing a fuseaction to go kaput and then move > onto the next. > > It shoulds like you are opening all the pages that have errors and > trying to fix them all in one fell swoop. You can't do that with fusebox > (and not lose your sanity). Just fix each problem one at a time until > the whole app works. > > Hopefully, that helps. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion is delivering applications solutions at at top companies around the world in government. Find out how and where now http://www.adobe.com/cfusion/showcase/index.cfm?event=finder&productID=1522&loc=en_us Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:284550 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
