Hi Lee, the forums mini-app does have its own dedicated space in the portal layout (between the global header and footer), so layout issues are not a problem here. I found your sample portal very useful when I was working on my portal layout by the way, thanks.
My question is that, if I link to the forum in the same way as you link to one of your news articles in your basic portal example (e.g. <A HREF="index.cfm?fuseaction=#fusebox.XFA.one#">Article One</A>), how do I ensure that my XFA destination (the forum mini-app) leads to the mini-app being cfmoduled, and not simply linked to directly? I would like the mini-app to be cfmoduled rather than linked to directly as I am less likely to run into local variable overlaps that way. hope my explanation makes sense. thanks, John Lee Borkman wrote: > Hi John, > > When you say that the forums mini-app is "self-contained", what exactly > do you mean. Do you mean that it has its own dedicated space in the > portal layout, or does the forums app share a common content space in > the portal with other apps, any of which can "take control", so to > speak? > If you want multiple apps to each have their own independent application > flow, all within an integrated layout, then that's quite a task, and you > might be better off thinking of frames ;-( But if you want all of the > various apps to share a single common content space, then that's much > easier. See my sample Basic Portal and/or Protal and Frames apps: > http://bjork.net/index.cfm/fuseaction/content.display/page/portal_frames.htm > > > In the Basic Portal example, the CFMODULE calls to the various mini-apps > are all done from the home circuit's layout file. That layout file > creates the complete HTML wrapper which goes around the common content > area, ie around the stuff created by the requested target fuseaction. > > Hope that helps some, > LeeBB > > ----- Original Message ----- > > From: John Boyes > > I'm working on an FB3 intranet portal (first biggish FB3 app I've > built). Fairly standard; the portal will have global navigation header > and footers, and contains many "mini-applications" such as a forum. > Using the forum mini-app as an example, it is self-contained and > therefore I think I should call it using cfmodule rather than cfinclude > (to ensure that local variables in the portal circuit are not falsely > overwritten etc). > > My question is, where in my code is the most elegant place to put the > actual cfmodule call to the forum mini-app? > > Obviously I can't include the cfmodule call in my href link to the > forums app. > > One option I've thought of is to create a forum fuseaction in my > top-level portal circuit which cfmodules > the mini-app, and link to this fuseaction from my portal. > > e.g. on the display page: <a > href="#self#?fuseaction=#thisCircuit#.forum">Forums</a> > > and in the switch: > <cfcase value="forum"> > <cfmodule template="#self#" fuseaction="forum.display_forums"> > </cfcase> > > The other option I can think of would I be to link straight to the forum > circuit from my href on the display page, but I can't see how to > cfmodule rather than cfinclude in this case. > > am I thinking about this along the right lines? > > thanks > > John > > > ==^================================================================ 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 ==^================================================================
