+ 1

and we should remove the old ones and a lot of old abstraction
� � � �MethodReference,
� � � �PseudoClass, FilePackage, and a lot more
I hope that we will get into that mode soon.

Stef

On Nov 16, 2011, at 3:55 PM, Fernando Olivero wrote:

> Please note that eventually the system is going to be using solely
> System announcements, instead of the old mechanism in place right now.
>
> Did you try hooking up to the SystemAnnouncements?
>
> For examples, check out Nautius.
>
> Fernando
>
>
>
> On Tue, Nov 15, 2011 at 9:02 PM, ezequiel lamonica
> <lamonicaezequiel@gmail.com> wrote:
>> Hello again,
>>
>> Now the problem is when I create a class that use Traits,
>> SystemChangeNotifier sends two messages to report this creation: 1st for
>> class added without traits, and 2nd for class modified to use this trait.
>> And this last message has Object as old class instead of ClassForTesting
>> without traits.
>>
>> For example:
>>
>> Object subclass: #ClassForTesting
>> � � � �uses: TSortable
>> � � � �instanceVariableNames: 'a'
>> � � � �classVariableNames: ''
>> � � � �poolDictionaries: ''
>> � � � �category: 'OOSCM-ClientImageTest'
>>
>>
>> Can I change those messages to use only one message that includes traits? Is
>> not this better?
>>
>> What do you suggest?
>>
>>
>>
>> -----
>> eze
>> --
>> View this message in context: http://forum.world.st/SystemChangeNotifier-and-Traits-tp4073962p4073962.html
>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>>
>>
>