On 17 July 2011 22:35, Lukas Renggli <renggli@gmail.com> wrote:
IMHO, the goal of Pharo should be to provide a minimal Smalltalk system where people Pharo can load what they need. Instead Pharo keeps on growing. I would prefer a system where I can decide myself what libraries and tools I want to use. I am sure that the current Announcement implementation can be fixed, but does it really make sense that the core team bothers about something that could be external?
No, Lukas. Announcements is not external and not about growing the system. It is still about shrinking it. As you may know, historically there's a lot of different event delivery mechanisms in image. Some of them: Object>>changed SystemChangeNotifier Morphic ActionSequence/WeakActionSequence and i am sure i missed couple more. And we're planning to replace all of them with single but solid Announcement framework. So, it will clean a lot of places and instead will shrink system considerably. That's why we wanting to have a solid foundation - a robust announcements framework.
Lukas
-- Lukas Renggli www.lukas-renggli.ch
-- Best regards, Igor Stasenko AKA sig.