Thanks for the input on this.
Ian
[EMAIL PROTECTED] wrote:
>
> Just the ones relevant to the fuse. Yes, otherwise, that would be
> unmanageable. You notice that I also cheat a bit and don't include the
> variable "fuseaction" which is always incoming (and usually outgoing as
> well).
>
> Hal Helms
> == See www.ColdFusionTraining.com <http://www.ColdFusionTraining.com> �for
> info on "Best Practices with ColdFusion & Fusebox" training, Jan 22-25 ==
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 15, 2000 11:59 AM
> To: Fusebox
> Subject: Fusedoc question
>
>
> After running my site with a partial fusebox implementation for several
> months I have decided to rebuild it "correctly". I am writing the fusedocs
> for my files and have a question: when youlist persistent variables in the
> doc, do you list every one that is available or do you just list the ones
> that are relevant to the specific fuse?
>
> I am curious because it might make future modifications easier for a
> newcomer if you list all persistent variables. However, this list could get
> pretty huge for every fuse. Thoughts?
>
> Ian
>
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
