The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
maybe the JDepend is what you looking for.
ReplyDeleteMaybe the Metrics plugin can do it? I haven’t tried it, but on the home page it mentions two coupling metrics and shows pretty graphs.
ReplyDeleteAnother similar tool CodePro - Dependency Analysis.
ReplyDeleteYou can use the Netbeans Profiler tools.
ReplyDeleteIf you choose the Memory mode you will be able to know Live Bytes /Live Objects / Allocated Objects and more per classes.
I think this way you can find out the classes you use the more or that use the more memory.
You have to run the app to know the results I don't know if your looking for a "static" way.