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
