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

2016-04-21 15:45 GMT+02:00 Tudor Girba : > > I think we not need special LoggerUI app. We can just inspect > SystemLogger instance to look at all recorded objects. And in perspective > of my suggestions it will mean that we just explore particular ObjectLog. > And we can

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

2016-04-21 14:57 GMT+02:00 stepharo : > >- name SystemLogger for collection based log. > > SystemLogger makes me think that it is singleton which is used by system > and I should not use it for my own application. > I would call it like ObjectLog or NativeLog (following my

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

Hi, > On Apr 20, 2016, at 10:53 AM, Norbert Hartl wrote: > > Denis, > > >> Am 18.04.2016 um 18:28 schrieb Denis Kudriashov : >> >> Hello. >> >> Year ago Beacon and SystemLogger were announced. There was big discussion >> about them. And there were

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

> On Apr 20, 2016, at 9:05 PM, Ben Coman wrote: > > Sorry for not having a better reviewed understanding of both > frameworks, but I have some thoughts from perspective of one user... > > On Thu, Apr 21, 2016 at 12:05 AM, Denis Kudriashov > wrote:

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

Hi, > On Apr 20, 2016, at 6:05 PM, Denis Kudriashov wrote: > > Hi. > > Thank's for answers. > > 2016-04-20 10:53 GMT+02:00 Norbert Hartl : > Agreed. As I said above. If you take to point of view from legacy logging > tool Beacon is not a big help.

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

2016-04-21 15:04 GMT+02:00 stepharo : > Denis > > you see, we (norbert and me) did not take this names randonmly we really > thought about them. > Yes, I know. I just try to make fresh look on it :)

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

Denis you see, we (norbert and me) did not take this names randonmly we really thought about them. Stef

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

You are considering Log as a noun, but it can also be used as a verb. defn "13. to enter in a log; keep a record of; e.g. to log a day's events." [1] Stef said: "Remember that you want to have them short especially for the main one. This is why in SystemLogger we have Log instead of what it is

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

Le 20/4/16 18:05, Denis Kudriashov a écrit : Hi. Thank's for answers. 2016-04-20 10:53 GMT+02:00 Norbert Hartl >: Agreed. As I said above. If you take to point of view from legacy logging tool Beacon is not a big help. But the ideas

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

Hi Ben. 2016-04-20 21:05 GMT+02:00 Ben Coman : > Sorry for not having a better reviewed understanding of both > frameworks, but I have some thoughts from perspective of one user... > So if you look at code you will see that what you mention below is not truth for current

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

Sorry for not having a better reviewed understanding of both frameworks, but I have some thoughts from perspective of one user... On Thu, Apr 21, 2016 at 12:05 AM, Denis Kudriashov wrote: > Hi. > > Thank's for answers. > > 2016-04-20 10:53 GMT+02:00 Norbert Hartl

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

Hi. Thank's for answers. 2016-04-20 10:53 GMT+02:00 Norbert Hartl : > Agreed. As I said above. If you take to point of view from legacy logging > tool Beacon is not a big help. But the ideas in it are good and should be > integrated somewhere. If you are talking about legacy

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

Denis, > Am 18.04.2016 um 18:28 schrieb Denis Kudriashov : > > Hello. > > Year ago Beacon and SystemLogger were announced. There was big discussion > about them. And there were plans to provide single solution. What was done > around that? > we had some talks but

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

> On 20 Apr 2016, at 9:54 , Tudor Girba wrote: > > Hi, > >> On Apr 20, 2016, at 9:37 AM, Henrik Johansen >> wrote: >> >> >>> On 19 Apr 2016, at 3:34 , Tudor Girba wrote: >>> >>> In the process I also added the

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

Hi, > On Apr 20, 2016, at 9:37 AM, Henrik Johansen > wrote: > > >> On 19 Apr 2016, at 3:34 , Tudor Girba wrote: >> >> In the process I also added the possibility to remove Announcements from an >> AnnouncementSet and I would like to push

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

> On 19 Apr 2016, at 3:34 , Tudor Girba 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

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

What I would like and that I wanted to SystemLogger was that the compiler for example could issue a log event and that we could build a tools to browse only such events and that I can click on it and jump right in the method with shadowing variables for example. So to get something more than

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

Hi, I even reviewed this post :). Of course, you can just use plain Announcements, but I still need to nuance your too strong statement. A framework is worthwhile when there is a recurrent need that it can serve. And when it comes to logging there are several such needs. For example: -

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

You might want to read https://medium.com/concerning-pharo/lampsort-revisited-visualised-6652055ef858 that discusses object logging and what you can do with it. My take on this is that if you write your code to produce log events (as Announcements), you can do whatever you want in the end.

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

Hi, Beacon is being used systematically. We even said we will integrate it in the image for Pharo 5 at the end of last year, but after the agitated start of the year, I did not push it anymore to not increase the level of agitation. The only class name that encountered some opposition was

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

Le 18/4/16 18:28, Denis Kudriashov a écrit : Hello. Year ago Beacon and SystemLogger were announced. There was big discussion about them. And there were plans to provide single solution. What was done around that? Nothing. We should have done it at Cambridge and we just discussed. I did

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

Hello. Year ago Beacon and SystemLogger were announced. There was big discussion about them. And there were plans to provide single solution. What was done around that? What exactly should be merged between this libraries? Was Beacon or SystemLogger planned to be end solution? We definitely