Hi,
I like very much the new energy people are putting into
creating the SystemLogger engine for Pharo. I think this is a
specifically important area for which we have to have a
solution out of the box. At the same time, I also think that
Pharo provides an infrastructure that makes room for ideas
that are otherwise hard to reach in other languages or
environments.
Why Java does not have announcements?
Stef asked for collaborations around this project, so here
is my literally small contribution: a rather different logging
engine.
I do not see how this contribute to SystemLogger. So at least please
do not say it, respect the amount of time I spent
design it and working with Norbert.
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. 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. 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:
So should we see it as a competitor to SystemLogger?
(you will say of course not) but I do not understand.
Cheers,
Doru
--
"Every thing has its own flow"