Steven, whew, you jumped right from zero to 60 in under a minute! :)
if you were starting from scratch, then I'd suggest definitely investigating a MVC design pattern. Hal wrote some short articles on MVC, both with and without FuesQ. They are on the Techspedition.com site and I've linked them into the "FuseQ to the ResQ" article. MVC, rather than FuseQ, goes a long way towards achieving what you'd asked about; FuseQ just makes it easy with Fusebox. What you've described is quite do-able, even without MVC. You'll just have to think it through a bit, but it sounds to me like you've thought through the *problem* quite well already. OK, on to your actual question: *if* you are writing all these apps yourself, *then* you could create what you describe, particularly if you use MVC. FuseQ will help greatly in this regard. You are up against a small issue with Fusebox which is the umbrella directory structure you mentioned. I have a solution for that, unrelated to FuseQ, but it's not ready for prime-time yet. When it is I'll just fold it into the Techspedition core file. In the meantime if you are able to control all the parts of your app then you should be ok -- is the forums app at least a FB3 app? one thing you'll want to do is to define in each of the Bird/Dog/Cat apps, pointers to a circuit which has the common code in it, just like a pointer to a "queries" circuit . Try setting up a higher level circuit as the parent to all those, and having no fuseactions in it. All it does is direct the request into the appropriate Bird/Dog/Cat application ---- Original Message ----- From: "steven ringo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 17, 2002 8:10 AM Subject: FuseQ and sharing fuses among apps > Hi, > > Lets say I have made three applications: > > - Bird > - Cow > - Dog > > Each one of these apps is self-contained, having their own fbx core > files, index.cfm etc. > > To get to each of these, I would go: > bird.site.com/index.cfm > cow.site.com/index.cfm > dog.site.com/index.cfm etc... > > The directory structure looks like this: > > wwwroot > +----Bird > +----Cow > +----Dog > > > Now the tricky part: > I need to "include" a Forums application inside each of these apps, but > with > inheritance of layout, datasources, etc. > > The current way of doing things says make a copy of Forums under each > app. > This is not good as I have to maintain 3 instances of the same code. > > wwwroot > +----Bird > | +---Forums > +----Cow > | +---Forums > +----Dog > +---Forums > > > Ideally I would want to have: > > wwwroot > +----Bird > +----Cow > +----Dog > +----Forums > > and then map the Forums' set of fuses appropriately to each of the apps. > > Problem is I cant get "past the root" or a directory higher than the > apps's root > in the circuits file. > > "Normal" FB3 does not handle this situation. > > Does FuseQ handle this, and if so, how? I am looking to this line of > text by John QvT > for inspiration: > > "Heaven help you if you want all your query files to be in a > physical directory 8 directories up, 5 directories over, and > 17 directories down. You can imagine what that would look like! Double > Ugh!" > > Thanks all > > Steven Ringo > > ==^================================================================ 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 ==^================================================================
