On Sat, Jun 16, 2012 at 2:44 PM, Sean P. DeNigris <[email protected]>wrote:
> > Stéphane Ducasse wrote > > > > sorry but I do not have the energy to discuss that publicly and via > email. > > The problem is that lot of people want a lot… and my energy is limited. > > > > I understand your frustration, but if we can't discuss important new > features on the developers list... wt#$@?! > 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. > -- > View this message in context: > http://forum.world.st/PackageOrganizer-packages-vs-categories-tp4635069p4635097.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >
