Sorry, I'm just now returned to a relatively old discussion. Hopefully people still feel like discussing. I've recently been made project manager of a very big, high-profile project (which I'm storyboarding in Fusebox, btw) and have had no spare time.
Anyway, I am suggesting a different issue than your last post, Hal. I know I have a very complex question. I hope I can explain it clearly. The comments made so far are that the Controller circuit for an application is very unique to an application, so you would rewrite it with each application. I'm saying, what if I have whole sub applications that don't need to have their Controller circuits rewritten? _If_ I want to use them in a larger application, _and_ I don't need new custom controller circuits for them to work, _and_ both sub applications contain a sub-circuit named "Menu" (for example), is there a good way to prevent conflicts and make the sub applications robustly drag-and-drop with MVC? Thanks for you input, Pete hal helms wrote: >Pete, > >The only fbx_circuits file that will be read is the home circuit's. Or >am I misunderstanding the issue you raise? > >-----Original Message----- >From: Pete Krueger [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, March 27, 2002 4:24 PM >To: [EMAIL PROTECTED] >Subject: Re: MVCs and re-using curcuits > > >Certainly, but what if two sub-circuits designed independently have the >same name in their fbx_circuits.cfm file. Obviously one will have to be > >changed to include them in the new, larger application's >fbx_circuits.cfm file. And when you change its name in the new, larger >application's fbx_circuits.cfm file, that sub-circuit's controller >circuits will have to be edited. Have you discovered a good way to >prevent this from happening? > >Pete > > >hal helms wrote: > >>Pete, >> >>Normally, the controller circuit is VERY specific to an individual >>application. It absorbs all the uniqueness of the application so that >>the View and Model circuits can remain largely unchanged. >> >>-----Original Message----- >>From: Pete Krueger [mailto:[EMAIL PROTECTED]] >>Sent: Wednesday, March 27, 2002 2:23 PM >>To: [EMAIL PROTECTED] >>Subject: MVCs and re-using curcuits >> >> >>Hello, >> >>For those of you experimenting with MVC and Fusebox, how does the >>Controller effect your reuse of circuits? I can imagine that I might >>have two circuits, a shopping cart ("cart") and a registration system >>("registration"). Each, when built independently, might have a model >>circuit called "User". If I drop these both in a larger application, >>say a portal, how do you resolve the names? Calls within a given >>circuit can use #fusebox.thisCircuit#, but both controllers would want >>to use compound fuseactions of "User.fuseaction". Is there a way to >> >set > >>things up so that they're drag-and-drop without having to change names >>in a controller circuit? >> >> >>Pete >> > ==^================================================================ 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 ==^================================================================
