Stan Shepherd wrote
VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074]
Image: PharoCore1.0rc1 [Latest update: #10500]
actually:
pharo1.0-10500-rc1web09.12.1
Class browser used (if applicable):O2PackageBrowserAdaptor
Steps to reproduce:
1.Open O2PackageBrowserAdaptor
2.Right click (Linux) on a class
3.Refactoring scope, package
BrowserEnvironment(Object)>>doesNotUnderstand: #forPackage:
Receiver: Smalltalk
Arguments and temporary variables:
aMessage: forPackage: a PackageInfo(Morphic)
exception: MessageNotUnderstood: BrowserEnvironment>>forPackage:
resumeValue: nil
Receiver's instance variables:
label: nil
searchStrings: nil
OR2CmdPackageEnvironment>>environment
Receiver: an OR2CmdPackageEnvironment
Arguments and temporary variables:
package: a PackageInfo(Morphic)
Receiver's instance variables:
target: O2ClassNode<Morph>
requestor: an O2EnhancementColumn(Morph)
...
DavidRoethlisberger wrote
Hi, this did fix that bug. Now it opens a OR2PackageBrowser that:
OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols
(left click on a class)
OBClassCategoryNode(Object)>>doesNotUnderstand: #isPackage
(right click package)
Is this:
Simon Denier wrote
However, the primary annoyance right now is the dichotomy between the OB new framework and the O2 derived for David's work. The problem is that now, whenever the tools changed in OB (especially refactoring support), O2 can not follow and it breaks the tools in the package browser.
?
i.e. is it sensible to report each bug in this area?
...Stan
Locked
