Hi Emilio. It's me!!
There's a neat little utility called FuseMinder. I'm really sorry to its
author, but I've forgotten who wrote it. I think Hal has a link to it from
his site. It takes the text output from various Mind-Mapping software (I
use MindManager), and turns it into a complete skeleton FuseBox app,
complete with Fusedocs in every template.
It's pretty darned cool, but I don't think it's going to help you deal with
FuseDocs AFTER you have begun filling in the skeleton.
I'm thinking about the XP ideas of documentation, or lack of it, now. It's
an appealing idea for a lazy programmer to think that maybe all of this
documentation is actually a BAD thing. Sometimes I think you shoudl do a
whiole development cycle to create the FuseDocs, the sign off on that
design. From then on, you don't change the spec, or if you do, you don't
try to keep the FuseDocs up-to-date. At the next cycle, you amend your docs
to reflect the code, perhaps. In general, I think that good FuseBox code
will be basically self-documenting - trivially small fuses, and a rigidly
formalised fusebox. FuseDoc really comes into its own, though, in team
development, at the very earliest stages. I must admit, though, when I'm
coding alone, on something small, I just spew out FuseBox code without much
planning. The discipline of FuseBox itself is just enough to keep me
heading in the right direction.
Still, enough of my dastardly secrets,
Lee.
-----Original Message-----
From: Emilio
To: Fusebox
Sent: 4/10/01 5:24 PM
Subject: SOT:Fusedoc survey
By a sake of weird timing I would also like to ask how you fellow FB
devotees a usage question. My focus is on Fusedocs and I am very
interested
to hear how you are creating them, managing them, maintaining them and
using
them AFTER coding has begun. DO you make any use of their content
outside
of first time coding and debuggging?
First would be, what programs (if any) outside of studio do you use to
create your fusedocs. I'll start off with some to get things going.
1) Notepad
2) Dreamweaver
Next I would like to know how you are developing them in terms of typing
them out, writing your responsibilities, attributes in and out...do you
do a
rough sketch on paper then simply copy your pseudo code right into CF.
Do
you have a central place to lookup all the variables you have created or
all
the queries. How do you keep it all straight in your head if you're a
typing machine?!
Last what are your likes and dislikes about using your program of choice
and
could the process be improved?
Reason you ask? Well Steve is correctly suggesting a time savings
through
better project development and more efficient programming techniques
right?
Well I'm interested in how we're getting the information out of our
heads
and into fusedocs, as that seems to be the bottle neck in my eyeyes.
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
