2013/7/21 Stéphane Ducasse <stephane.duca...@inria.fr> > Announcer subclass: #Customer
And what I should do if I want Customer which can trigger events? Do you think "EventSource subclass: #Customer" make any difference? Or do you think we should never use inheritance to make domain announcer classes? What the existed alternative? I don't want always add announcer instance and couple equal methods any time I need it. In practice in both cases my domain classes will never override methods from "events support superclass". And to me name "Announcer" is exactly events source. Is my english so bad here? Maybe we should rename it to "AnnouncerMediator" and real Announcer class? Best regards, Denis
