Adam Churvis has come up with an interesting idea where he takes the
responsibilities of the wireframe and the exit points of the wireframe and
makes those the starting point for his Fusedocs. I think that makes a lot of
sense.
As for Emilio's question, I keep the Fusedocs pretty religiously up-to-date.
I really see these as the defining documentation/comments for the fuse and
seldom do any in-line commenting on the code itself. I usually do the fuses
prior to the fusebox itself and construct the fusebox by looking at the
Fusedocs for individual fuses. I know others do it the fusebox first and
that works great also. For large projects, I usually create a pretty
thorough schematic using Visual Mind. (You can see a partial image of a
schematic for an app I'm doing for a book at
www.halhelms.com/public/booksbyhal.jpg.) This really helps me keep track of
things and lets me work out most of the naming stuff ahead of time.
Hal Helms
Team Allaire
[ See www.halhelms.com <http://www.halhelms.com> for info on training
classes ]
-----Original Message-----
From: Daniel J O'Keefe [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 9:14 AM
To: Fusebox
Subject: RE: Fusedoc survey
A thought for the crowd. Would there be any practical use to combining
fuesdocs and the wireframe application?
Dan
-----Original Message-----
From: Emilio [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 3:24 AM
To: Fusebox
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
