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

Re: [Pharo-dev] SystemLogger unrevealed :)

by GÃ¶ran Krampe

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 :) - 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. 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. 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." > 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. The SLLogWatchDog is a trivial "send an email if a certain level is reached" with some bundling etc. SLLogFile has log file rotation. SLLogMorph is the simple search and filter UI. regards, GÃ¶ran

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

I updated the doc and Iâm studying SimpleLog. For the level of errors if this is easy I will follow sysLog order/default because it is not worth to be different. tx for the pointer Stef PS: now the cool remark would also be to say: "Pharo is cool not only cool frameworks are developed but they come with a nice documentationâ On 22 Feb 2014, at 15:51, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hey! > > You didn't know about SimpleLog or? > > http://map.squeak.org/packagebyname/simplelog > > Not that it matters much, we can all use more logging tools ;) but... one "mistake" I think is that you don't match the standard syslog levels as described on the URL above. > > SimpleLog even has a Morphic tool with it. Anyway, feel free to take whatever you like from it. > > regards, GÃ¶ran >

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

On 22 Feb 2014, at 15:00, btc(a)openinworld.com wrote: > That looks very nice. I wonder whether yes I will fix it. > Log warm: 'the system is still running but you should have look at it'. > should be > Log warn: 'the system is still running but you should have look at it'. > > > I liked the example ... > withExtra: [ :log | log extensionAt: #thisContext put: thisContext] > > I recently have had some good debugging success using the following... > Transcript crShow: > thisContext printString , ' ' , > thisContext sender printString , ' ' , > thisContext sender sender printString , ' ' , > thisContext sender sender sender printString. > ...to understand some dynamic behaviour with Announcements where putting a #halt would lock the system and a #haltOnce didn't provide a broad enough picture. > > It would be cool to be able to do something like... > Log message: 'Here' withExtra: [ :log | log contextDepth: 4 ] send some doc and update the doc :) > > cheers -ben >

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by Pharo4Stef

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 :). 100 timesRepeat: [Goran repeatAfter: me what: âString sucks, string are dead objectsâ] Iâm coding in Smalltalk and not in perl! 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. So we should have look at letting string habits outside of our nice house. Stef On 22 Feb 2014, at 15:51, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hey! > > You didn't know about SimpleLog or? > > http://map.squeak.org/packagebyname/simplelog > > Not that it matters much, we can all use more logging tools ;) but... one "mistake" I think is that you don't match the standard syslog levels as described on the URL above. > > SimpleLog even has a Morphic tool with it. Anyway, feel free to take whatever you like from it. > > regards, GÃ¶ran >

Feb. 22, 2014

Re: [Pharo-dev] Multiple-selection drag-and-drop

by Martin Dias

On Sat, Feb 22, 2014 at 5:04 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > On Sat, Feb 22, 2014 at 4:53 PM, Benjamin > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> On 22 Feb 2014, at 16:40, Martin Dias <tinchodias(a)gmail.com> wrote: >>> >>> Mmmmmmm, now that I test it with a mouse instead of a trackpad, I see >>> it's almost impossible to do not loose the multiple selection before >>> starting the drag in a TreeModel. >> >> Why? >> Here it works fine (at least as expected) >> I >> -click on the first element, >> -shift click on the last one, >> -click and drag >> >> and it works >> > > Ohhh! I found how to reproduce it: if you start to drag in the bottom > item, then it works; but if you start in another one, then > multi-selection is lost. Another find: When multi-selecting using control key (I'm on mac), then drag has to start in the last selected item, otherwise it's list.

Feb. 22, 2014

Re: [Pharo-dev] Morphic UI designer

by Pharo4Stef

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/ >

Feb. 22, 2014

Re: [Pharo-dev] SystemLogger unrevealed :)

by GÃ¶ran Krampe

On 02/22/2014 04:30 PM, btc(a)openinworld.com wrote: > GÃ¶ran Krampe wrote: >> Hey! >> >> You didn't know about SimpleLog or? >> >> http://map.squeak.org/packagebyname/simplelog >> >> Not that it matters much, we can all use more logging tools ;) but... >> one "mistake" I think is that you don't match the standard syslog >> levels as described on the URL above. >> >> SimpleLog even has a Morphic tool with it. Anyway, feel free to take >> whatever you like from it. >> >> regards, GÃ¶ran >> >> > SimpleLog gets a mention in the PDF. > cheers -ben Nope, that's SimpleLogger. regards, GÃ¶ran

Feb. 22, 2014

Re: [Pharo-dev] Multiple-selection drag-and-drop

by Martin Dias

On Sat, Feb 22, 2014 at 4:53 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > On 22 Feb 2014, at 16:40, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> Mmmmmmm, now that I test it with a mouse instead of a trackpad, I see >> it's almost impossible to do not loose the multiple selection before >> starting the drag in a TreeModel. > > Why? > Here it works fine (at least as expected) > I > -click on the first element, > -shift click on the last one, > -click and drag > > and it works > Ohhh! I found how to reproduce it: if you start to drag in the bottom item, then it works; but if you start in another one, then multi-selection is lost.

Feb. 22, 2014

Re: [Pharo-dev] Multiple-selection drag-and-drop

by Benjamin

On 22 Feb 2014, at 16:40, Martin Dias <tinchodias(a)gmail.com> wrote: > > Mmmmmmm, now that I test it with a mouse instead of a trackpad, I see > it's almost impossible to do not loose the multiple selection before > starting the drag in a TreeModel. Why? Here it works fine (at least as expected) I -click on the first element, -shift click on the last one, -click and drag and it works > > As I remembered that in another thread I somebody told that NewLists > work better with drag-and-drop of multiple selection, I tried with > NewListModel, but I discovered that here drag-and-drop is not working > even with single selection. I just reported it in: > > https://pharo.fogbugz.com/f/cases/12969/Drag-and-drop-never-starts-in-a-New… Fixed already :P Ben

Feb. 22, 2014

Re: [Pharo-dev] Multiple-selection drag-and-drop

by Martin Dias

On Fri, Feb 21, 2014 at 6:26 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > On Fri, Feb 21, 2014 at 2:14 PM, Benjamin > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> This works: >> >> m := TreeModel new. >> m roots: #(1 2 3 4 5). >> m dragEnabled: true. >> m dropEnabled: true. >> >> m transferBlock: [ :p :s | >> TransferMorph >> withPassenger: s model >> selectedItems from: s ]. >> >> m multiSelection: true. >> >> m openWithSpec. >> >> I guess the same applies for the other model, aka, redefining the >> TransferMorph. >> I am currently working on a TransferModel to hide the morphic part of it, >> but it will not be in Pharo 3.0. > > Great, it worked. Thanks Mmmmmmm, now that I test it with a mouse instead of a trackpad, I see it's almost impossible to do not loose the multiple selection before starting the drag in a TreeModel. As I remembered that in another thread I somebody told that NewLists work better with drag-and-drop of multiple selection, I tried with NewListModel, but I discovered that here drag-and-drop is not working even with single selection. I just reported it in: https://pharo.fogbugz.com/f/cases/12969/Drag-and-drop-never-starts-in-a-New… Thanks for all your support. MartÃn

Feb. 22, 2014