> Haha, He will not discuss, but we can :). :)
> > The migration is also painful right now because system events are a mess. We > have SystemChangeNotifier and SystemAnnouncer, and there is a nice hack to > keep both working. SystemAnnouncer is registered to SystemChangeNotifier and > old system events are magicly coerced, transformed(whatever name you want to > put) into system announcements. And RPackage suffers because some clients of > it, sends inconsistent events like: > > - method recategorized when the method was removed > - a method removed event with an obsolete class that has no information > - recategorizations with categories in nil??? > > So, my heart tells me that we have to clean that slowly also to lower the > system's entropy. > I've already moved some SystemChangeNotifier users to System announcer, there > are left the senders of #notify:ofAllSystemChangesUsing: and some tests. So, > there is a nice spot to attack. > Once events are tammed, the Rpackage integration with the rest of the system > will be cleaner and clear. oh yes :) I really appreciate your systematic effort to help. Indeed if we can remove Change notifier and revise the announcements raised it will make our life easier. Stef
