I agree completely, Patrick. My first thought when creating the spec was to
make it XML based, but in looking how BIG it would be and how much harder to
read it would be, I rejected the idea. The purpose of Fusedoc is to provide
a human coder the information they need to write the fuse. I wrote a parser
for Fusedocs once (mainly because I wanted a little mental break from
working on Rooms To Go) and though it was cool, I never actually used it.
Machine parsing may have benefits--I especially think the idea of combining
the Assert tag with the Fusedoc makes sense--but the primary benefit is for
human readers.
Hal
-----Original Message-----
From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 8:04 AM
To: Fusebox
Subject: RE: Fusedocs Q
I had thought about basing it on XML-Schema[1] at one point. That
would be much easier to parse, but not nearly as easy to read.
[1] http://www.w3.org/TR/xmlschema-2/
> -----Original Message-----
> From: Derek Hamilton [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 30, 2001 2:18 PM
> To: Fusebox
> Subject: Re: Fusedocs Q
>
>
> 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
