Phil, this is laziness on my part. I assume that a fuseaction is going to be
passed out and don't bother documenting it. However, it would look like
this:
--> XFA.onSubmitForm: a FUSEACTION
--> XFA.onCancelForm: a FUSEACTION
<-- fuseaction: an XFA
Hal Helms
Team Allaire
[ See ColdFusionTraining.com for info on "Best Practices with ColdFusion &
Fusebox" training ]
-----Original Message-----
From: Phil Spitler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 08, 2001 5:22 PM
To: Fusebox
Subject: FuseDocs w/ XFAs
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
