2009/11/1 Lukas Renggli <[email protected]>: >> In current core image, Announcements is quite small (just around 10 >> methods totally) and i doubt it provides enough >> flexibility which would not require adding & reinventing additional >> useful stuff on top of it. > > I have used these announcements in many large projects and I never > needed to add anything. In fact, I would even vote to remove > AnnouncementSet as I never used it or saw it used anywhere. Initially, > I found it cool because the same trick is applied in the Exception > hierarchy. Major projects like OmniBrowser (and to some extent also > Seaside) use an even smaller subset of the functionality provided in > the core package. > > The only thing that is maybe missing are weak announcements. I guess > that could be useful, if Pharo provided a solid implementation of weak > objects. >
Announcements is just another implementation of observer pattern. And given that its quite simple to (re)implement by own, obviously, the question is, why anyone would want to use Announcements instead of making own? If Announcements provides more wide functionality in addition to observer pattern - then yes, you could say: it is better because in addition you have this and that. But if it so stripped to bare-bones, then where the benefits to use exactly Announcements? > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
