April 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Logging API discussion

by Denis Kudriashov

2016-04-28 14:51 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > It is not the most elegant solution, but it is very malleable and good > enough for debugging purposes. If we would have instance-based filtering > for announcements, we could filter based on that without any extra effort. > Also, if we would have a composition mechanism in place, we could build > these objects with a more elegant API. > > Regarding your statement of logging domain objects, you will have to store > these objects with the additional information somewhere, and that will be a > wrapper class. I do not see the difference with the Signal. > Difference with Beacon is that users will not depends on objects from logging library. Nobody needs to subclass core components like Signal. Instead domain objects will be added to logs inside general LogEntry instances which will be hidden from user and only available inside logs. And LogEntry will allow include additional information to itself by appropriate logging API. Question is: does it better? And this is what problem I see around Beacon: Beacon proposes to design log entries as events, as subclasses of BeaconSignal. If nothing else exists it is good. We will see in logs collection of such events. But what to do with existing domain events which has no relation to logs? How to log them if we decide to do it? They can be added to log inside WrapperSignal. But then we will see in logs mix of normal events which created specially for logs and WrapperSignal's containing original application events. But both type of events belong to same application. We definitely want to see them and to work with them in same way everywhere (especially inside logs) Tudor what do you think about this problem? Maybe I misunderstood Beacon.

April 28, 2016

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

by Andrei Chis

I can help a bit if you need non French speakers. On Thu, Apr 28, 2016 at 3:15 PM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > Me too. > > Vincent > > > -----Message d'origine----- > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Serge > > Stinckwich > > EnvoyÃ© : jeudi 28 avril 2016 14:45 > > Ã : Pharo Development List > > Objet : Re: [Pharo-dev] Looking for moderators and helpers for the Pharo > Mooc > > > > I can help. > > > > > > On Thu, Apr 28, 2016 at 8:43 PM, stepharo <stepharo(a)free.fr> wrote: > > > Hi guys > > > > > > We are looking for moderators and people to help in the forum on the > mooc. > > > > > > Let me know if you want to help. > > > > > > Stef > > > > > > > > > > > > > > -- > > Serge Stinckwich > > UCBN & UMI UMMISCO 209 (IRD/UPMC) > > Every DSL ends up being Smalltalk > > http://www.doesnotunderstand.org/ > > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted.!!!" >

April 28, 2016

zeroconf will not support anymore get.pharo.org/vm

by Esteban Lorenzano

this is a legacy script they will not work anymore, since vms are not compatibleâ¦ is announced since last year we will remove itâ¦ this is the moment :) Esteban

April 28, 2016

zeroconf for release pharo50 will remove "travis" scripts...

by Esteban Lorenzano

â¦ because nobody uses them, and they are not needed :)

April 28, 2016

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

by Blondeau Vincent

Me too. Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Serge > Stinckwich > EnvoyÃ© : jeudi 28 avril 2016 14:45 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc > > I can help. > > > On Thu, Apr 28, 2016 at 8:43 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > > > We are looking for moderators and people to help in the forum on the mooc. > > > > Let me know if you want to help. > > > > Stef > > > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

April 28, 2016

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

by phil＠highoctane.be

Went through the course, I can help. Phil On Thu, Apr 28, 2016 at 2:43 PM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > We are looking for moderators and people to help in the forum on the mooc. > > Let me know if you want to help. > > Stef > > >

April 28, 2016

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

by Cyril Ferlicot Delbecque

On 28/04/2016 14:43, stepharo wrote: > Hi guys > > We are looking for moderators and people to help in the forum on the mooc. > Hi, I can help a little if needed. > Let me know if you want to help. > > Stef > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

April 28, 2016

Re: [Pharo-dev] Logging API discussion

by Denis Kudriashov

2016-04-28 14:51 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > And if I really wanted to add extra information, I rudimentary did: > > {âsome textâ . object } asBeaconSignal log. > > Or even: > > {âsome textâ . #someSymbol . 42 . object } asBeaconSignal log. > And for such cases we definitely need simple #log message without #asBeaconSignal. It can be hidden inside. Or it can be: Log add: {âsome textâ . #someSymbol . 42 . object }

April 28, 2016

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

by Valentin Ryckewaert

If needed I can help at my little level ! 2016-04-28 14:45 GMT+02:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > I can help. > > > On Thu, Apr 28, 2016 at 8:43 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > > > We are looking for moderators and people to help in the forum on the > mooc. > > > > Let me know if you want to help. > > > > Stef > > > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

April 28, 2016

Re: [Pharo-dev] Logging API discussion

by Denis Kudriashov

2016-04-28 14:42 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > > Domain objects can supply own timestamp to log entries. > > I do not understand this point. Could you clarify? I think you mention something different than I had in mind. My case was when anObject already has internal timestamp it can pass it to log entry (signal)

April 28, 2016