I had troubles myself seeing how this can contribute to SystemLogger. It looks a lot like âI donât like yours here is mineâ. But if you remember that is the same reason why you've started SystemLogger.
no I started SystemLogger because - it should log objects - it should be the basis for the future logger.
So you should be fair here. Now it is the time to see how we can benefit from each other. I see it as an advantage to have code to compare because a lot of discussions are usual too theoretical to make something of it. I did not have the time to look at svens and dorus code. But I will because I had the impression, too, in the beginning that the dispatching of events would be better done with announcements.
If you have an hammer everything looks like a nail. To me it just kills my fun.
We all should review the other implementations and all of us should be open minded for any reason why the own implementation is probably _not_ the way to go. I wish we can find an agreement about an optimal implementation we like to promote.
Norbert
It is called Beacon, it is based entirely on Announcements, it has ~200 lines of code, it has no tags or levels, and in my opinion it is fully functional.
You can see a detailed description here including some informal comparisons with SystemLogger: http://www.humane-assessment.com/blog/beacon
Please let me know what you think. I would be happy to join forces to reach a mature solution that is both versatile and that can show how Pharo is different. So should we see it as a competitor to SystemLogger? (you will say of course not) but I do not understand.
Cheers, Doru
-- www.tudorgirba.com <http://www.tudorgirba.com/>
"Every thing has its own flow"