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 > -- Pete Krueger Web Applications Programmer University of Maryland University College [EMAIL PROTECTED] ==^================================================================ 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 ==^================================================================
