methodDisplayStringForClass: class selector: sel
^ String streamContents: [ :s |
s nextPutAll: class name ;
nextPutAll: ' ' ; nextPutAll: sel ;
nextPutAll: ' {' ;
nextPutAll: ((class organization
categoryOfElement: sel) ifNil:
['']) ;
nextPutAll: '} ']
"
nextPut: $[ ;
nextPutAll: (PackageOrganizer default
mostSpecificPackageOfClass:
class ifNone: [PackageInfo named: '**unpackaged**']) packageName ;
nextPut: $]]."
On Jul 9, 2009, at 11:10 PM, Michael Rueger wrote:
> Lukas Renggli wrote:
>>> OUCH!!!! That's quite an example; just for giggles, I started up a
>>> 3.9 polymorph image and retraced my steps (via message names, same
>>> as in Pharo) and had a prompt reply. After doing that, I found
>>> that Pharo (win32) had indeed completed the task.
>>
>> Again, this has nothing to do with Pharo, OmniBrowser or Polymorph.
>>
>> This is PackageInfo that is so slow when trying to find out the
>> owning package of each of the 6334 methods. If the display of the
>> package for every method is removed the sender browser opens almost
>> instantly.
>
> Then we should remove or at least temporarily disable it. The user
> doesn't care why something is slow.
>
> michael
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
