Hi,
In reference to the below from Nat, has anyone ever considered making
fusedocs an xml base document? I recently started doing this with my
fusedocs so that later (ie when I get around to it) I can write a little
program to go in and parse the xml and create some sort of README document
or whatever I decide to do with it. You could this way also use a DTD to
have typical types of inputs/outputs defined.
This might not answer all questions but I was just wondering...
Derek
----- Original Message -----
From: "Nat Papovich" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Wednesday, May 30, 2001 9:01 AM
Subject: Re: Fusedocs Q
> Patrick -
>
Fusedocs can be
> long and involved and must be well written to get business rules and
> processes into code, including any algorithms for determinig figures,
rates,
> scores, or whatever your business may be.
>
> NAT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
