Smalltalk › Pharo › Pharo Smalltalk Developers

announcer "dispersion"

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

stepharo

announcer "dispersion"

Hi

I was analysing the implementers of announcer and I think that there are
far too many of them.
To me this is the sign that we are doing something wrong.
I would like to introduce an announcer in Model and make sure that most
of the direct subclass
of Object implementing an announcer take benefits of the Model one.

What do you think?

Stef

stepharo

Re: announcer "dispersion"

In fact I was thinking about the solution: add a new AnnouncingModel
class unrelated to Model
or add announcer to Model. Now I think that the second solution is
better because we have many subclasses
of Model implementing Announcer and I do not know if they are not using
some behavior of Model too.

Le 21/8/15 21:44, stepharo a écrit :

> Hi
>
> I was analysing the implementers of announcer and I think that there
> are far too many of them.
> To me this is the sign that we are doing something wrong.
> I would like to introduce an announcer in Model and make sure that
> most of the direct subclass
> of Object implementing an announcer take benefits of the Model one.
>
> What do you think?
>
> Stef
>
>
>

Thierry Goubier

Re: announcer "dispersion"

Le 22/08/2015 09:56, stepharo a écrit :
> In fact I was thinking about the solution: add a new AnnouncingModel
> class unrelated to Model
> or add announcer to Model. Now I think that the second solution is
> better because we have many subclasses
> of Model implementing Announcer and I do not know if they are not using
> some behavior of Model too.

Isn't an announcer used to replace some of the uses of the dependency
changes observer pattern, in complex cases (where the observed object
can emit multiple types of changed symbols)?

Thierry

>
> Le 21/8/15 21:44, stepharo a écrit :
>> Hi
>>
>> I was analysing the implementers of announcer and I think that there
>> are far too many of them.
>> To me this is the sign that we are doing something wrong.
>> I would like to introduce an announcer in Model and make sure that
>> most of the direct subclass
>> of Object implementing an announcer take benefits of the Model one.
>>
>> What do you think?
>>
>> Stef
>>
>>
>>
>
>
>
>

stepharo

Re: announcer "dispersion"

Le 22/8/15 19:36, Thierry Goubier a écrit :

> Le 22/08/2015 09:56, stepharo a écrit :
>> In fact I was thinking about the solution: add a new AnnouncingModel
>> class unrelated to Model
>> or add announcer to Model. Now I think that the second solution is
>> better because we have many subclasses
>> of Model implementing Announcer and I do not know if they are not using
>> some behavior of Model too.
>
> Isn't an announcer used to replace some of the uses of the dependency
> changes observer pattern, in complex cases (where the observed object
> can emit multiple types of changed symbols)? yes it should.

This is how can we get there. I hope that Bloc and Brick will address.
Now we should continue to improve our implementation.

> Thierry
>
>>
>> Le 21/8/15 21:44, stepharo a écrit :
>>> Hi
>>>
>>> I was analysing the implementers of announcer and I think that there
>>> are far too many of them.
>>> To me this is the sign that we are doing something wrong.
>>> I would like to introduce an announcer in Model and make sure that
>>> most of the direct subclass
>>> of Object implementing an announcer take benefits of the Model one.
>>>
>>> What do you think?
>>>
>>> Stef
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>