From: Mike Harrison ------------------------------------------------------ Jason, A long long time ago, in a text editor far far away.. You introduced me to a tool that would look at a directory full of PHP code and produce a nice html-ish output of what was where, how it all related, etc.. Lisa is in my office and asked me for the same thing. and I must confess, I do not remember what it was and have not used it in a long long time and no longer have it installed. But the force seeks that program again, so that it can do good on bad code. Not mine. this time.

=============================================================== From: Jason Brown ------------------------------------------------------ There are two that I use: http://www.phpdoc.org/ This one is great, but for the best usage you should be doing code comments in the @phpdoc format (most projects and frameworks use this commenting format). Without the comments it will still help to visualize structure. http://phpxref.sourceforge.net/ This one is better for things like: "This function calls that, is called by this, and is referenced in these files on these line numbers" etc. Does a good job of describing a code project even if you don't have any comments. I have used both to get a quick overview and grok the logic and flow of a framework or open source project. With phpdoc, I run nightly builds on some projects and keep internal documentation up to date that way. The build runs nightly, the documentation gets checked approximately monthly ;) Both need a crapload of RAM for a large project, I have had phpdoc use 5 gigs on a particularly large code base. There might be some newer or more up to date ones out there, but it is not a topic I have researched in at least 3 years and these two fit my occasional needs. --Jason

=============================================================== From: Lisa Ridley ------------------------------------------------------ Thanks to you both! should be doing code comments in the @phpdoc format (most projects and = frameworks use this commenting format). Without the comments it will = still help to visualize structure. "This function calls that, is called by this, and is referenced in these = files on these line numbers" etc. Does a good job of describing a code = project even if you don't have any comments. of a framework or open source project. documentation up to date that way. The build runs nightly, the = documentation gets checked approximately monthly ;) 5 gigs on a particularly large code base. not a topic I have researched in at least 3 years and these two fit my = occasional needs. it in a long long time and no longer have it installed.

=============================================================== From: Joshua Estes ------------------------------------------------------ Some other good tools to keep your code in check: PHP Mess Detector http://phpmd.org/ PHP