[I'm moving this to the new [EMAIL PROTECTED] list...]
EBNF stands for Extended Backus-Naur Form. It's a geek way of specifying a
language. I just mean that there's a clear spec right now on Fusedoc that
shouldn't be lightly changed. That's not to say someone couldn't create
their own version of a documentation/PDL system (which is what Fusedoc is).
As for the quest for cool tools, let me tell a story on myself. I'm trying
to learn to cook and I must say, I suck at it. So I went through a period of
trying to buy cool tools that would make me an instant cook. You probably
know this already: They didn't work--although I *do* have some cool things
in my kitchen now! I'm afraid I think the desire for a cool tool for
Fusedocs is a bit like my quest to buy cooking competence. That's just my
opinion, of course.
-----Original Message-----
From: Emilio [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 8:36 PM
To: Fusebox
Subject: RE: XML FuseDocs
While I don't see the need for XML-based docs (and see a good many reasons
NOT to do it), if you DO want to create something, please don't call it
Fusedoc--it will just create confusion. Fusedoc is a specification and has a
EBNF definition.
Sorry, what does EBNF mean??
I agree with you ( unfortunately :-} ) as I find designing the schema a
chore and then keeping two copies of everything seems a little messy. Is it
possible then, ( cfstudio guru's answer here ) to add tag insight or
auto-completion for the fusedoc process? Is it really just a matter of
creating a bunch of additions to the auto-completion section? that seems
like too much work!!
How can we make creating and maintaining Fusedoc's easier? Or is it that
summer is here and I'd rather be sunning?
Cheers,
Emilio
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
