It would be helpful to visualize the "weight of usage" of each header file in the project or the whole workspace:
* The include file name in the graphical node has a bolder and/or bigger font type the more often the header file was parsed during a full rebuild.
* Find the most frequented sections of the include graph across all dependent modules.
Sure there may be manual workarounds and with some research you can fiddle your ways to the answers as well. But it takes time, is mostly unreliable and distracts the developer from the actual goal - implement software.
Whats is more problematic are those #ifdef conditional source code sections. You don't have one, but a set of possible source codes to cope with. Visual Studio does this in 2005 nice for syntax coloring. For example - You change a #define and affected code passages are greyed out (Wonderful). Greatly enhances the reading of the source code.
Crossreference: As an "Eclipse/Visual Assist X user" i was searching for crossreference features in the RMB popup menu . I definitely need more time to learn TheIDE before i can comment on this.
Generally "analysing source" workflow in SNIFF+ had the popup panel/windows overkill problem. After some time your destop was filled with all kinds of views. The docked panels of todays IDEs do a better job there. But on the other side this way you "naturally" build a stack of panels which you can traverse back and forth by opening and closing them.
(in TheIDE you could optionally use the editor split view to display the graph in one side.)
Yes I realize now, I miss SNIFF+
The final, generally true statement: Damn if I had more time i would do this by myself
Members
Pages
Help
Register
Login
Home
. I definitely need more time to learn TheIDE before i can comment on this.
