Good! :) But really one day we will have to fix all the classes without comments. can you please add it to the bugtracker. I will harvest it and put it in the same package as the inspector. Stef On May 22, 2009, at 6:44 PM, Steve Wirts wrote:
Stef,
I've renamed a few methods for clarity, utilized Morph>>flashBounds method for flashing, added a class comment, and 2 examples. is it at least a C- instead of D+ now? :)
let me know what else I should do?
On Fri, May 22, 2009 at 11:27 AM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote: Hi steven
at the minimum you should comment the class and have some examples methods that illustrate its purpose. ;) and it would be to be able to invoke it from the inspector/explorer? Then it would be good that the comments tell the user a little scenario so that we can learn and improve from it so far I had to read the cs file to see that you changed the debug menu and But for example I do not see how I can get one particular object to flash
On May 22, 2009, at 5:14 PM, Steve Wirts wrote:
I've enhanced a few things to make use of existing tools as per an early thread.
Is there any chance this simple enhancement can get integrated into the main stream of developement? It really is quite usefull in understanding a complex morph composition. < ViewHierarchyExplorer .st>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
< ViewHierarchyExplorer .st>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project