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.
ok. Here the combination of sentences is unfortunate. I�m sorry! I know the reasons why you did it. And you know that I chimed in (not developing my own solution) because I liked the idea from the beginning (because I have thought about that often before). I just wanted to say that there are good reasons to start your own implementation (like you did). That�s all!
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.
Right. In my case it is just a gut feeling I had all the time. Might be it turns out that announcements are not the way to go. But I want to look at it.
To me it just kills my fun.
I understand and I�m sorry if the mail I wrote supported that. To be really honest I had the same feeling when I talked with Sven and Doru. It appeared to me that everyone wanted to place his own solution. But I like to take the chance that we get something out where a lot of people are happy with. On the other hand SystemLogger is not final. It can be improved and we should improve it. Now it is the time to collaborate and tame our egos. Otherwise there will be three half baked approaches, one in zinc, one in GT* tools and one in pharo. That would be the worst outcome. In order to prevent that I wanted to talk. Just that!
My plan is to:
- look at beacon to see what Doru has in his mind. Maybe I get a good idea from it
- then I would look at Sven�s new code to see the difference to Doru�s and to actual see if that works for more than a framework
- finally I would like to look at the SystemLogger design again and improve it where it might be improved.
- then there will be a new version of SystemLogger. That�s it.
I personally don�t plan to skip SystemLogger in favour of beacon or zinc log. beacon is a proof of concept but there are AFAIK no formatters, outputs and so on. So it is not even a replacement for SystemLogger. Zinc log is a log system for a single framework called zinc. I�m not sure it can be useful for anything else and I don�t think Sven is hitting in that direction.
I want a basic logging support that either has a central access for pain free logging or it has multiple announcers (maybe one per module/framework) that can be composed to a log source that can be attached to some kind of dispatcher. I don�t know. That I need to figure out
Norbert
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"