Fusebox and good fusedocs. At least for vanilla FB applications. Makes jumping into code amazingly simple.
For CFC-based apps, CFCdoc is a great tool for generating javadoc-like docs for all your CFCs. http://www.spike.org.uk/projects/cfcdoc/ Of course, both of those are code-level docs, but if you're the developer, thats presumably what you're considering writing? The requirements docs and stuff should be done back before you start coding. cheers, barneyb On 7/26/05, Paul Roe <[EMAIL PROTECTED]> wrote: > I don't know about you guys but it's been a long time since I worked > from a requirements document or had a formal code review. > > With that in mind I was wondering what everyone in this community does > to document their cf applicaitons. I know I could go through and > write the standard package of requirement docs and funny looking uml > diagrams, but what is really usefull? What do you guys do for > documentation and what do you find usefull when maintaining someone > else's code? > > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
