Re: [Pharo-project] SystemChangeNotifier and Traits
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.
+ 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.
On Wed, Nov 16, 2011 at 1:14 PM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
+ 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.
PseudoClass, FilePackage, may indeed be poor. But IMO MethodReference is central and extremely useful.
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.
-- best, Eliot
On 16 November 2011 23:47, Eliot Miranda <eliot.miranda@gmail.com> wrote:
On Wed, Nov 16, 2011 at 1:14 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
+ 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.
  PseudoClass, FilePackage, may indeed be poor.  But IMO MethodReference is central and extremely useful.
Yes. There's already a replacement for it in Ring model.
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.
-- best, Eliot
-- Best regards, Igor Stasenko.
On Wed, Nov 16, 2011 at 8:44 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 16 November 2011 23:47, Eliot Miranda <eliot.miranda@gmail.com> wrote:
On Wed, Nov 16, 2011 at 1:14 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
+ 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.
PseudoClass, FilePackage, may indeed be poor. But IMO MethodReference
is
central and extremely useful.
Yes. There's already a replacement for it in Ring model.
But the name is important. I don't want to have to rewrite everything because the name changes. If the name stays the same then is this a replacement?
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.
-- best, Eliot
-- Best regards, Igor Stasenko.
-- best, Eliot
RGMethodDefinition.
PseudoClass, FilePackage, may indeed be poor. But IMO MethodReference is central and extremely useful.
Yes. There's already a replacement for it in Ring model.
But the name is important. I don't want to have to rewrite everything because the name changes. If the name stays the same then is this a replacement?
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.
-- best, Eliot
-- Best regards, Igor Stasenko.
-- best, Eliot
Eliot We did more than our homework. We have a full code model that is polymorphic with Smalltalk object counterparts. methodReference should be removed because we have much better. Veronica worked at least 4 months on ring and it is good. Stef On Nov 16, 2011, at 10:47 PM, Eliot Miranda wrote:
On Wed, Nov 16, 2011 at 1:14 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: + 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.
PseudoClass, FilePackage, may indeed be poor. But IMO MethodReference is central and extremely useful.
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.
-- best, Eliot
On Thu, Nov 17, 2011 at 9:43 AM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
Eliot
We did more than our homework. We have a full code model that is polymorphic with Smalltalk object counterparts. methodReference should be removed because we have much better. Veronica worked at least 4 months on ring and it is good.
Is the name the same? Is the replacement still called MethodReference?
Stef
On Nov 16, 2011, at 10:47 PM, Eliot Miranda wrote:
On Wed, Nov 16, 2011 at 1:14 PM, Stéphane Ducasse <
stephane.ducasse@inria.fr> wrote:
+ 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.
PseudoClass, FilePackage, may indeed be poor. But IMO MethodReference is central and extremely useful.
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.
-- best, Eliot
-- best, Eliot
What code relies on it? Because you could add a the globals pointing to MethodReference? Stef
On Thu, Nov 17, 2011 at 9:43 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: Eliot
We did more than our homework. We have a full code model that is polymorphic with Smalltalk object counterparts. methodReference should be removed because we have much better. Veronica worked at least 4 months on ring and it is good.
Is the name the same? Is the replacement still called MethodReference?
Stef
On Nov 16, 2011, at 10:47 PM, Eliot Miranda wrote:
On Wed, Nov 16, 2011 at 1:14 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: + 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.
PseudoClass, FilePackage, may indeed be poor. But IMO MethodReference is central and extremely useful.
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.
-- best, Eliot
-- best, Eliot
participants (4)
-
Eliot Miranda -
Fernando Olivero -
Igor Stasenko -
Stéphane Ducasse