Hi Norbert,
On Tue, Jun 17, 2014 at 5:09 PM, Norbert Hartl <[email protected]> wrote: ... > 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. > Thanks. > 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! > Indeed. I think nobody wants that. But the very fact that we are talking about ideas and that we all want to compare with one another will exactly lead us to one strong solution :) 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 > I think they are the same conceptually. On the one hand, Sven's code is more specific to Zinc, but the cool thing about it is that we get real use cases for typed events. > - 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. > Nor should you :). We should build one whatever the name is. Let's just take the time to compare the concepts and we see afterwards. beacon is a proof of concept but there are AFAIK no formatters, outputs and > so on. > I think Beacon is actually a full implementation of a logger. There are as many outputs as there are in the core of SystemLogger. As for formatters, I explicitly did not want them in the core because I think we should not favor text too prominently. I think that scrolling through a text file is not a good direction and that we should instead build logging analysis tools as I tried to explain in the blog post. The video of Sven shows how this can look in practice. 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 > Great. Doru > > 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: > 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 > > "Every thing has its own flow" > > > > > > -- www.tudorgirba.com "Every thing has its own flow"
