[Pharo-dev] What the state of unifying Beacon with SystemLogger?

Henrik Johansen henrik.s.johansen at veloxit.no
Wed Apr 20 03:37:30 EDT 2016

> On 19 Apr 2016, at 3:34 , Tudor Girba <tudor at tudorgirba.com> wrote:
> In the process I also added the possibility to remove Announcements from an AnnouncementSet and I would like to push this in Pharo 6.0. One thing I would work on is to add to Annoucements the possibility of filtering announcements based on instances not just types. This is a longer term plan.
AnnouncementSet is just a normal set, so it has always been possible to remove items, just not recommended.
Filtering on instances is in the same category of making actual delivery after subscription more dynamic; both also have the effect that it becomes even harder to reason about what is going to happen as a result of an Announcement without actually running the code.

IMHO, if the logic is "I want to handle this announcement some of the time", that is much easier to understand if handled explicitly in announcement handling code, rather than through state changes to the announcement delivery.

As I think Glamour is a poster child for, current usage patterns can already be hard to follow ;)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20160420/1a2aafe4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20160420/1a2aafe4/attachment.asc>

More information about the Pharo-dev mailing list