>>But enough ranting. My pet-peeve is not that comments are necessary, but aid in helping others to understand the direction of the coders' intent. So that people like myself can use their tools without having to strain in reading and implementing it.
>
>Good point. But what I usually miss even more is the general overview of a project design. I guess that is because of time contraints (like manuals often face the same fate), and the question how to do it so it is really useful. A graphical overview would be great, but projects are generally too large to be able to fit into a picture. A Word document is difficult to structure in a way that you could find what to look for. But it would be great to be able to view the project in macro style, and then drill down into modules, viewing all related classes and then drill into micro style and see the properties and dependencies. I never came to the point to be able to envision how that could be accomplished.

I've often thought the same, how handy it would be to have some sort of tool to visualize a new (to me) system to be maintained, or how a new (to me) framework works. In effect, a graphical Project Manager. Integration with a debugger would be nice as well, although some existing debugger features such as call stacks are quite handy. Maybe borrow some features from debuggers for other languages that are better than VFP's.

Dare to dream, dare to dream...