Look at HalHelms.Com under his dot notation for nested fuseboxes. I had
the same problem, I had to switch fuses then call the fuseaction of the
fuse I switched to. With nested fuses it works great and they can be
used on their own. Now I am redoing my entire application.
Then a second thing happened. I used the DevNotes custom tag and it
places notes on each page for development(I recoded it in a couple
hours to do the dot notation and be able to call it as a custom tag
within the larger app using cfmodule.(Put it in the dsp_footer.cfm file
so it appears on each page).
The devnotes tag uses the base fuseaction to save to comments to in its
db. So a fuseaction of members.login would be the same as clients.login
because you basically have the same base fuseaction login (although the
app will go to the appropriate fuse or fusebox). So I changed them to
be members.mbrlogin and clients.cllogin just for devnotes. I will turn
off the cfif statement on the site so that you can see the devnotes
without being logged in as an administrator. And you can see how the
dot notation switches between fuseactions, although I cannot let you
into the site to see it switch fuses (but you can imagine from there)
http://cliniweb.isu.edu
----- Original Message -----
From: "Nelson Winters" <[EMAIL PROTECTED]>
Date: Friday, January 19, 2001 2:49 pm
Subject: Who's fuseaction is it anyways?
> I don't know if my thinking is all screwed up or what, but is it
> possible/smart to nest fuses (pardon me if I use incorrect
> terminology)?What I mean by this is invoking via a custom tag a
> fuse from within another
> one fuse. The problem I'm having difficulty resolving is how to
> resolveproblems when there is contention between two fuses for a
> fuseaction. For
> example, a web-based PIM that has both a calendar and an email client
> displayed on one screen. If the user want to view a different
> month in the
> calendar or folder in the email client, the request is going to
> call the
> main page and the pass a fuseaction such as "change_month" or
> "change_folder". How do the fuses know who needs to do what?
> Also, how do
> you maintain the "state" of the other fuses (i.e. just change the
> calendarand remain in the current email folder.)
>
> A few solutions that I see to this are:
>
> 1. Don't do this
> 2. Use frames and popup windows and keep each fuse separate from
> each other
> 3. Add a fuse paramater (i.e.
> fuse=calendar&fuseaction=displaymonth&month=march).
>
> Solutions 1 & 2 are obviously not solutions. Solution 3 might
> work with the
> use of some sort of fuse structure to store active settings such as:
>
> Fuses.Self = "fuseaction=PIM&view=advanced&style=santefe"
> Fuses.Calendar = "fuseaction=displaymonth&month=march"
> Fuses.Email = "fuseaction=search&keyword=macromedia+merger"
>
>
> Hopefully someone can set me straight on this,
>
> Thanks,
>
> Nelson
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
