I think that in Bloc alain did it on purpose and not just by accident.
Alain may correct me:
An event is managed by the event loop and other. The idea is that
other objects do not register to an event.
it happens to me.
An announcement is raised and unknown object can register and get
access to it.
Other register to react to it.
So Event is not equal to Announcement
Stef
Le 27/7/15 23:57, Peter Uhnák a écrit :
Hi,
is there a good reason why not just rename Announcement to Event since
everyone is calling it that anyways?
Everybody (almost irrespective of language) understands what an event,
whilst Announcement is a new vocabulary.
Most people when subclassing will anyways do
Announcement subclass: MyEvent
and so forth.
Is there a benefit in naming it Announcement? Doesn't it just add more
confusion?
For example Bloc has
Announcement subclass: #BlAbstractEvent
and
Announcement subclass: #BlMorphAnnouncement
whilst Event is clearly favored.
BlMorphAnnouncement allSubclasses size. "5"
BlAbstractEvent allSubclasses size. "60"
(Why does Bloc has this separation anyways?)
Peter
