Just thinking off the top of my head, but what about establishing a set of standard comments that your developers can use to comment their code....variables in, variables out, basic summary of procedure, etc. etc.
Users can then comment their own code as necessary. Your app would then run behind the scenes and scrape the source code for these comments, and insert everything into database for use in a nice, clean, manager's documentation application. This is sort of similar to the documentation capability the "///" gives you in .NET. On 7/12/06, Paul Ihrig <[EMAIL PROTECTED]> wrote: > > so we are going to write a new db app to document all of our code. > > things like where & why stored procs are used/unused.. > things like that. > > has any one seen an example of a cf app that does this. > basically every thing is getting so big, our managers manager, wants > to be able to see what is going on where > > any good examples. > right now it looks like a pretty simple thing to build. > but if i can plan it right it would be a pretty slick app. > > just wondering what bells and whistels i could add. > > -paul > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:5/messageid:210996 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5
