Le 5/9/15 14:10, Stephan Eggermont a écrit :
On 05-09-15 08:52, stepharo wrote:
Since when? Where is the bug entry? Where is a reproducible case?
The easy ones:
16485 Class panes not refreshed when changing package (by Marcus)
16486 Nautilus doesn't update the method pane after adding a method (first time)
16487 Dropping methods on empty areas of class/method category pane raises SubscriptOutOfBounds
16488 Dropping a class from one browser to another package in another browser updates selected package+class in both
16489 Monticello browser doesn't update others after adding repo May be this is a ripple effect of the reducing the number of announcers that we started. We cannot get 50 different announcers in the systems. And may be we did not redo the initialization or something like that.
Are the fixes of yuriy addressing the nautilus one?
And there is a more difficult case where changing code in the debugger does not get to (all) nautilus browsers. I had two browsers open and changed code that was in the selected class but not visible in the browsers. One browser was correctly updated, the other was not.
This has happened for a few weeks now, and I thought this was known and related to the current Nautilus refactorings.
No Pharo is a complex system and we do not have enough tests.
Stephan