I don't worry about doc'ing the fuseaction variable. It's Fusebox, so I know
my coders understand that the variable "fuseaction" must be passed out.
Thus, a Fusedoc Attributes section for a fuse that has two exit points, btnOK
and btnCancel, would look like this:
|| Attributes ||
--> XFA.btnOK: a FUSEACTION
--> XFA.btnCancel: a FUSEACTION
And somewhere in the fuse there would be something like this:
<input type="button"
name="btnOK"
value="OK"
onclick="document.location('#request.self#?fuseaction=#attributes.XFA.btnOK#')"
<input type="button"
name="btnCancel"
value="Cancel"
onclick="document.location('#request.self#?fuseaction=#attributes.XFA.btnCancel#
')"
- Jeff
[EMAIL PROTECTED]
On 8 Mar 2001, at 17:22, Phil Spitler wrote:
> I'm designing a new app and am fusedocing like a good fuseboxer. I recently
> started using XFAs and am wondering if someone could give me a good example
> of a fusedoc w/ XFAs envolved.
>
> My main question is...
> If the fuseaction that is being sent out is a variable that is passed in as
> an XFA, how do you properly document the fuseaction that will be passed out?
>
> Thanks,
> Phil
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
