From the standpoint of wanting to fix them, I really don't see the point in expanding the tree past the first level, but sure. As long as you have a right-click menu-item on each to open a browser on the method for easy fixing of the deprecated call site ;)
Personally, I'd prefer a tree like in the picture attached, to me at least that's more intuitive. Cheers, Henry On Dec 9, 2009, at 12:19 31PM, Alain Plantec wrote:
Henrik Sperre Johansen a écrit :
+2 Even better if there's a button in each row to open a list of the methods that have been recorded as calling the deprecated version :D
Henry
Hi Henry, Maybe something like that (see screenshot):
Each root shows a deprecated method call. Here, 3 calls to the same deprecated method but from different paths. The occurence show how many time the deprecated method has been called with the same caller chain. 23 times for Try1>>call -> Try2>>call 2 times for Try2>>call 3 times for Try3>>call -> Try1>>call -> Try2>>call
So, you see exactly which deprecated methods were called, from where and how many times.
Alain
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
<DeprecationsTree.png>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
