Re: [Pharo-users] MethodName
Hi everybody I came back with a new version of Method Name with a better Package Chooser and more choices about the search :) I hope it's useful but if there is some behaviour you would like the Method Name implements, just let me know Gofer new squeaksource: 'PharoTaskForces'; package: 'MethodName'; load. Thank you Ben
On Wed, Aug 25, 2010 at 1:25 AM, Benjamin Van Ryseghem < benjamin.vanryseghem@gmail.com> wrote:
Hi everybody
I came back with a new version of Method Name with a better Package Chooser and more choices about the search :)
I hope it's useful but if there is some behaviour you would like the Method Name implements, just let me know
Gofer new squeaksource: 'PharoTaskForces'; package: 'MethodName'; load.
Hi Ben. This is muuuch cooler :) There are 2 things I suggest you: 1) Whenever you send something in order to let people to test is, send in which Pharo version should we load it. It is not enough saying Pharo 1.2 for example. Maybe you need to say 12XXX because in THAT version NullStyler was integrated. 2) You should send this kind of mails to pharo-project@lists.gforge.inria.fr instead of pharo-users@lists.gforge.inria.fr Bugs I found: - Search a "class name" and put "ImageSeg*". You will see a list of results. Selet ImageSegment for example. Then, select again "selector" instead of "Class names" If you then click again in of the resulted classes, there is a DNU UndefinedObject doesNotUnderstand: #methodClass. In MethodNameUI >> sourceCode where it does: self selectedClass value methodClass I attach PharoDebug.log
Thank you
Ben
_______________________________________________ Pharo-users mailing list Pharo-users@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
participants (2)
-
Benjamin Van Ryseghem -
Mariano Martinez Peck