February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] SystemLogger unrevealed :)

by HernÃ¡n Morales Durand

2014-02-22 15:50 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: > Hernan > > do you know how we could produce an extension that can plug into Log4J and > Log4s :) > I don't know, sorry. > BTW the last time I check I could not really load Log4s :) > That's weird because I'm using in production since weeks ago from daily fresh built 3.0 images :) I've checked now from Configuration Browser and all +200 tests passes. I cannot say for 2.0, I decided to stop maintaining packages for older versions. I will check your Logger and see how it goes. HernÃ¡n

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

Hernan do you know how we could produce an extension that can plug into Log4J and Log4s :) BTW the last time I check I could not really load Log4s :) Stef On 22 Feb 2014, at 19:07, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > What's the advantage over Log4s? > > HernÃ¡n > > > 2014-02-22 9:24 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: >

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

Goran do you know the JSON format I meand not format but schema to be compatible with fluentd because this could be a nice extension. Stef > So actually, I would make sure that SimpleLogger could also easily log in JSON, let me quote from fluentd: > > "Fluentd treats logs as JSON, a popular machine-readable format. It is written primarily in C with a thin-Ruby wrapper that gives users flexibility. > > Fluentdâs performance has been proven in the field: its largest user currently collects logs from 5000+ servers, 5 TB of daily data, handling 50,000 msgs/sec at peak time."

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

On 22 Feb 2014, at 18:49, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Excellent, Stef! > > I reviewed a bit the code: > - The name log denotes the recording of multiple events. However, the Log class models only one event, not many. Thus, a more suitable name would be LogEvent. Or maybe LogEntry (like in StarTrek :)) in the class comment :) !! Design notes. I'm named Log and not SLLogObject or whatever because I'm the main entry point for a client point of view. > - Similarly, SystemLogger>>logs should be something like logEvents/logEvents. I changed it to logEntries. Iâm interested in extensions to stress the design and extension points of SystemLogger :) On 22 Feb 2014, at 18:49, Tudor Girba <tudor(a)tudorgirba.com> wrote:

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

On 22 Feb 2014, at 19:07, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > What's the advantage over Log4s? I was thinking to reply simplicity and no string bullshit but this could be impolite :) Frankly I want an extensible object logger that can be domain specific if needed. All the rest is âextensionsâ to me. I will start to integrate simpleLog as extensions Stef > > HernÃ¡n > > > 2014-02-22 9:24 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: >

Feb. 22, 2014

Re: [Pharo-dev] Morphic UI designer

by Erwan Douaille

Hi, I add Lorenzo as a contributor of UIPainter. If you need help, i'm on vacation this week so i can help :) 2014-02-22 17:18 GMT+01:00 Pharo4Stef <pharo4Stef(a)free.fr>: > > On 22 Feb 2014, at 15:24, jannik laval <jannik.laval(a)gmail.com> wrote: > > Does it make sense to add energy on it ? > Probably, we should investigate UIPainter. > > > may be the first thing to do would be to convert some of the widgets to > work in Pharo with announcements. > I did not have the time to verify but I did the following experience > I built a simple naive browser using self changed:/updates > then I wanted to rewrite it using Announcement only and it did not work > probably because some of our widgets > are not done to be used with announcements (probably they expect changed....) > > so it may be the same with his widgets. > > Stef > > > Jannik > > > 2014-02-21 22:02 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > >> At the moment I'm moving, so I have very little time to do something >> about it. >> Current state is described in a thread from end of last year: >> >> >> http://forum.world.st/have-a-question-for-morphic-Designer-in-pharo-td47313… >> >> Stephan >> > > > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://car.mines-douai.fr/ > > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

On 22 Feb 2014, at 18:12, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hi! > > On 02/22/2014 05:26 PM, Pharo4Stef wrote: >> Hi goran >> >> There are only two questions: >> 'Why when I load code do I have to open the transcript before to see the shadow and undeclared. >> and why I cannot click on an object and jump to the broken code?" >> >> Now with SimpleLogger I imagine that I cannot log compiler shadow, donât you :). > > I am not quite sure what you are saying... Ah, you mean logging objects instead of strings? Sure, I didn't say SimpleLog was BETTER, I just said you didn't look at it and thus may be missing out on nice stuff that you can steal :) Iâm currently :) In fact I read all the other frameworks except his ones. > - Using syslog levels, it is very standard and logging these days of clouds do NOT stay on the local machine. > - Stealing the syslog emitter, it is just 20 lines of code. > - Stealing log file rotation perhaps? I think its in there. > - Stealing whatever else seems good. Yes I was reading the code and I will package that in extensions. Now I do not know UDP and others. > Having log objects in the image is great. > >> 100 timesRepeat: [Goran repeatAfter: me what: âString sucks, string are dead objectsâ] > > Well, do remember that logs in a "system world" end up getting routed through syslog (and tons of variations on that theme) and eventually end up in event collecting systems etc - just look at fluentd.org to understand what I mean. Indeed this is orthogonal to me. And I want to kill Transcript show > So actually, I would make sure that SimpleLogger could also easily log in JSON, let me quote from fluentd: It is just a simple formater. Norbert is using that (if Iâm correct) to collect data from his servers with SystemLogger. > > "Fluentd treats logs as JSON, a popular machine-readable format. It is written primarily in C with a thin-Ruby wrapper that gives users flexibility. > > Fluentdâs performance has been proven in the field: its largest user currently collects logs from 5000+ servers, 5 TB of daily data, handling 50,000 msgs/sec at peak time." > >> Iâm coding in Smalltalk and not in perl! > > In fact, now that I am looking at SimpleLog I realize we could have had an emitter that collected objects and just let "message" be whatever - and send asString or asJSON to it when it reaches the emitter instead. :) > Now if you want to have syslog output this is probably one method definition in a new formatter in our nice frameworks. >> Do you have an output that shows what is needed for sysLog? because I can add a package for sysLog outputter. > > Its very short code. Just steal it. I attached all the code as an .st fileout so that you can get it trivially. Its the SLSyslogSender class. Yes I will. If you want I can give you access to the repo. After I want to avoid to have dependencies to morph because the tiny core should be in the core of Pharo and all the rest pluggable. I want to use SystemLogger for Opal too. > The SLLogWatchDog is a trivial "send an email if a certain level is reached" with some bundling etc. Yes I saw :) Nice extension. > SLLogFile has log file rotation. Yes I saw I will rewrite it to use FS. > SLLogMorph is the simple search and filter UI. Yes I will probably steal it too. > > regards, GÃ¶ran > > > <SimpleLog.st>

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by HernÃ¡n Morales Durand

What's the advantage over Log4s? HernÃ¡n 2014-02-22 9:24 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: >

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Tudor Girba

Excellent, Stef! I reviewed a bit the code: - The name log denotes the recording of multiple events. However, the Log class models only one event, not many. Thus, a more suitable name would be LogEvent. Or maybe LogEntry (like in StarTrek :)) - Similarly, SystemLogger>>logs should be something like logEvents/logEvents. I like it a log that LogEvents are full objects because we can subclass them with specific semantics. This is particularly important if we want to build tools for custom applications. The first application I have in mind is Zinc. Zinc already comes with a logging mechanism that treats LogEvents as objects, but they are all of the same type, so in the end, if you want to track the events for request/response you have to reverse engineer the text. These semantics could be preserved. >From what I see, the main difference between the Zinc log system and the SystemLogger is that the latter has a dispatcher that can dispatch to multiple loggers. Is there anything else that is different? I think it would be cool to merge the two. Doru 2014-02-22 13:24 GMT+01:00 Pharo4Stef <pharo4Stef(a)free.fr>: > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Sven Van Caekenberghe

Reading it now. There is also the Zinc logging framework, Zinc-HTTP-Logging, already in the image, based on Announcements. On 22 Feb 2014, at 13:24, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > <Logger.pier.pdf>

Feb. 22, 2014