We have used documentation that is pre-fusedoc. The documentation is in the
templates but not in the method as described by Hal Helms. As far as the
changing requirements; we all know that clients do at times ask for more and
more. Especially when they get a new ideal in the middle of the night. Even
if it is going to cost more.
Now I'm a true supporter of the fusebox methodology which should also
include fusedocs. Now I'm new to fusedocs verbiage and format. And I've
never had to use this style of documentation anywhere I've worked. I have
used something like this in Pascal and other languages. But not this style.
So as far as I see it I have two choices. One forget about fusedocs on this
project and stick with the old structure & style to get the job done. Or
two add it in this current site in development.
Now I am still thinking about both options. And I didn't want to start a
civil war or become a target. Sorry that I asked in the first place.
Lee Foster
L3 Enterprise
-----Original Message-----
From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 12:24 PM
To: Fusebox
Subject: Re: FuseDoc's and WireFrame
> But I could easily spend
> a day or more inserting this into this site. And it keeps changing on a
> weekly bases.
should we imply from this that you are already coding even though the specs
are not complete? If so, *that* is the (on-going) problem, rather than the
time it would take to write fusedocs post-coding.
Of course, one cannot turn back the clock on this particular project. But I
think the most important point to gather is that, had the fusedocs been
written before coding started, not only would the fusedoc be already done
(obviously) but the coding itself might already be complete. Certainly
fusedocs that are written before coding turn out to require much less
editing if any, once coding starts. Tweaks on individual templates and the
index.cfm here and there is all -- otherwise the C++ client you've got is
scope-creeping you.
> If there isn't an application like that one I'm talking about. It would
be
> a good project to be done in the future. Especially if it could look at
the
> template and figure out most of the text that should be in the fusedoc.
And
> to tie in WireFrame and maybe a few other things. This would help a great
> deal.
There are any number of different helpful tiny apps like what you describe
floating around. What people were hoping for was something along the idea of
"fusebox studio" which someone talked about on here a few months ago, but
which has proven to be vapor-ware. It's a shame because a simple overall
structure might have been sufficient for other people to pick up the slack
and expand and add in xtra modules, Borkman is exceptionally good at that
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
