>>>>>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...
>>
>>I have offen dreamed of writing a PM replacement tool that would allow me to organize code and classlib into modules and sub-modules. Perhaps with a tab interface so I can see multiple project files in a single Solution. The ability to drill-down into the classes and procedure files and see the methods within. The Class Browser aids in this, but only show user defined PEM, not the native PEM that have changed. (I fixed this once, but lost the code somewhere).
>>
>>Also, a tool that would graphically display a class and the methods with their drill-downs dependencies. Like the call stack, but at design time.
>>
>>Perhaps for my next pet project.
>
>Have you taken a look at the Project Explorer in VFPX that Doug Hennig built?
>
>Tamar

Yes, but I have not used it as a main PM, yet. I will revisit it. Thanks