September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] OSWindow in Pharo 6.1 stable

by ClÃ©ment Bera

On Fri, Sep 29, 2017 at 10:29 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > IMHO, it will make Pharo much more robust if core libraries as sdl, cairo, > etc will be shipped with each plateform dependent virtual machine and the > image modified accordingly to use these core libraries. > That's how it is now but some of it is not working (Here SDL events and there are 2 SDL2 libs by default). I think we should still have a minimal image starting with a minimal UI without using FFI/SDL/Cairo or whatever lib. Else when we start on a platform where one of this thing is not properly supported yet (See the problem on the raspberry pie with some Pharo alpha version) it is too hard to understand what is going on. > > The delivery of Pharo application to end users is an issue because of > these recuring problem. Honestly I was trying to write a doc on how to deploy Pharo client app with SDL2 and Cairo but I have only a version working in Pharo 4 on Mac and Linux, while in theory I could have it working in Windows/Mac/Linux in the latest Pharo. > Hilaire > > > > Le 28/09/2017 Ã 15:02, ClÃ©ment Bera a Ã©crit : > >> Btw for some reason in the one-click version of Pharo 32 bits on Mac >> there is 2 SDL plugins (libSDL2-2.0.0 and libSDL2), which leads to >> conflicts (the VM use randomly one lib or the other). I randomly chose one >> that I use and deleted the other one, do you have advises on which one I >> should prefer ? Maybe the events are working only with the other one ? >> >> > -- > Dr. Geo > http://drgeo.eu > > > >

Sept. 29, 2017

Re: [Pharo-dev] String Interpolation

by Sven Van Caekenberghe

> On 29 Sep 2017, at 06:40, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Sven, > > Is this one the similar to the #evaluate in > http://www.squeaksource.com/evaluablestrings ? Haha, yes that is exactly the same trick. Lukas & Philippe back in 2005, duh. > Cheers, > > HernÃ¡n > > > 2017-09-28 11:20 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Hi, >> >> I got into a little office discussion about string interpolation as it is done in different programming languages. >> >> In Pharo we have String>>#format: which is pretty nice. It works as follows: >> >> | x y | >> x := 123. >> y := #foo. >> 'x={1} and y={2}' format: { x. y }. >> >> It is also possible to use a dictionary with keys, like this: >> >> | x y | >> x := 123. >> y := #foo. >> 'x={x} and y={y}' format: { #x->x. #y->y } asDictionary. >> >> But this is not true string interpolation as described in [ https://en.wikipedia.org/wiki/String_interpolation ]. The idea is to write the value generating expressions directly inside the strings. >> >> Since in Pharo we add features not by extending the syntax but by adding messages I wondered if it could be done for string interpolation. The goal is to make the following work: >> >> | x y | >> x := 123. >> y := #foo. >> 'It seems x equals {x} and y equals {y} while Pi is still {Float pi}' interpolate. >> >> => 'It seems x equals 123 and y equals foo while Pi is still 3.141592653589793' >> >> Here is the implementation I came up with: >> >> String>>#interpolate >> "Format the receiver by interpolating the evaluation of expressions >> in between curly brackets in the context of the sender as in the following 3 oneline examples. >> 'Today is {Date today}' interpolate. >> | x | x := 123. 'x equals {x} and pi equals {Float pi}' interpolate. >> 'In {#strings} you can escape \{ by prefixing it with \\' interpolate." >> >> | senderContext | >> senderContext := thisContext sender. >> ^ self class new: self size streamContents: [ :out | | stream | >> stream := self readStream. >> [ stream atEnd ] whileFalse: [ | currentChar | >> (currentChar := stream next) == ${ >> ifTrue: [ | expression result | >> expression := stream upTo: $}. >> result := Compiler new >> evaluate: expression in: senderContext to: nil notifying: nil ifFail: [ ^ nil ] logged: false. >> out nextPutAll: result asString ] >> ifFalse: [ >> currentChar == $\ >> ifTrue: [ stream atEnd ifFalse: [ out nextPut: stream next ] ] >> ifFalse: [ out nextPut: currentChar ] ] ] ] >> >> It is a hack that could certainly be improved. And there is of course an obvious security problem. >> >> Thoughts ? >> >> Sven >> >> >

Sept. 29, 2017

CI does not finish (PR 309)

by Torsten Bergmann

For whatever reason the CI jobs for PR's to Pharo 7 runs endless and never finishes. It run well a few days ago ... https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… Any ideas?

Sept. 29, 2017

Re: [Pharo-dev] Non-deterministic ombu errors

by Jan BlizniÄenko

I'm glad it has known reason then, thank you for looking into it, all I was able to find out was that it relates to non-ascii characters and that build on our production server fails because of that :) Jan tinchodias wrote > On Sun, Sep 24, 2017 at 5:49 AM, Sven Van Caekenberghe < > sven@ > > wrote: > >> >> > On 23 Sep 2017, at 22:42, Jan BlizniÄenko < > bliznjan@.cvut > > wrote: >> > >> > Hello >> > >> > I am having very similar errors from time to time when manually loading >> code >> > into Pharo from filetree (gitfiletree), but only in one of my projects >> which >> > contains non-ASCII characters like ÄÅ¡ÄÅÅ¾Ã½Ã¡ÃÃ©Å¯ÃºÅ¥Ä. For the very same >> reason >> > (not able to find why sometimes the error is there and sometimes is >> not), I >> > did not report it yet, but it is quite annoying. Retrying loading the >> > package helps every time. >> >> I think was reported before. I believe Ombu somewhere takes an arbitrary >> chunk of bytes out of an UTF-8 encoded file (like the last 100 of >> something >> like that) and then starts reading that. With UTF-8, a variable length >> encoding, that can be dangerous because you could end up in the middle of >> a >> character, not between encoded character boundaries. This would also >> explain the randomness, as it is highly dependent on the contents. >> >> ZnUTF8Encoder>>#backOnStream: can be used to make sure you are really at >> the start of an encoded character. >> > > > Hello > > This issue was reported as: > > https://pharo.fogbugz.com/f/cases/20112/Epicea-can-fail-while-reading-non-a… > > My apologies for the bug... I introduced that code as an i/o optimization > but wasn't properly tested. > > Thnks Sven, but I finally used stream's #basicNext (as Henrik suggested in > fogbugz) which skips forward. > > > Martin -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 29, 2017

Should we always put application file paths into FileLocator?

by Denis Kudriashov

Hi. Many times I was trying to find "global" files of some packages in system. For example do you know how to find epicea session logs? There is class side method for this at EpMonitor: EpMonitor logsDirectory Is it easy to find when you never look at it? No. Do you know how to find sources file? There is message in Smalltalk global: Smalltalk sourcesFile Is it easy to find? No. And there are many other examples. But if you read about FileSystem library. You know the common place where to find well known files. It is FileLocator. For example changes file is here: FileLocator changes. So my idea is to introduce kind of pattern, the good style, how to access global application files: they should be in FileLocator as extensions. Then it would be super easy to find files of any applications. What do you think? If it is good idea then we should fix current places in system to follow this pattern. Best regards, Denis

Sept. 29, 2017

Re: [Pharo-dev] OSWindow in Pharo 6.1 stable

by Hilaire

Hi, IMHO, it will make Pharo much more robust if core libraries as sdl, cairo, etc will be shipped with each plateform dependent virtual machine and the image modified accordingly to use these core libraries. The delivery of Pharo application to end users is an issue because of these recuring problem. Hilaire Le 28/09/2017 Ã 15:02, ClÃ©ment Bera a Ã©critÂ : > Btw for some reason in the one-click version of Pharo 32 bits on Mac > there is 2 SDL plugins (libSDL2-2.0.0 andÂ libSDL2), which leads to > conflicts (the VM use randomly one lib or the other). I randomly chose > one that I use and deleted the other one, do you have advises on which > one I should prefer ? Maybe the events are working only with the other > one ? > -- Dr. Geo http://drgeo.eu

Sept. 29, 2017

Re: [Pharo-dev] OSWindow in Pharo 6.1 stable

by ClÃ©ment Bera

Hi Ronie... I need help again. In fact I am still not able to work with SDL2 events in Mac with Pharo 6 nor 7. In Pharo 6 and Pharo 7, 32 and 64 bits I need to run this code: 'FFIExternalStructure allSubclassesDo: #rebuildFieldAccessors'. In all cases I can open the window and draw on it with Cairo, but the problems lie with the events. In all cases when I start with libSDL2 and libSDL2-2.0.0 I have warnings in the command line (2 libs detected, a random one will be used each time), so I usually use only libSDL2 which seems to work better. In 32 bits (both Pharo 6 and 7) if I delete the libSDL2-2.0.0 lib and use libSDL2 only, I have mouse and window events but only **some** keyboard events. I have around 2/3 of the keyboard events, which makes the app very hard to use (Each time you press a key, you need to check if it worked or press it again if not). I don't know for sure if I have all the other events or only 2/3 of them too as there are so many. In 64 bits, (both Pharo 6 and 7), whatever combination of lib I attempt I don't have *any* event (keyboard, mouse or window). I have a working version in Pharo 4 where I have all the events. It's the same 32 bits lib so it has to come from something else (VM changes or image changes). Any idea on what I have to fix to move from 2/3 of the events to all the events ? What is the right way to get a working SDL2 window with Pharo 6/7 ? Thanks On Thu, Sep 28, 2017 at 4:25 PM, ClÃ©ment BÃ©ra <bera.clement(a)gmail.com> wrote: > Ok I used the other lib (libSDL2 instead of libSDL2-2.0.0) and it worked. > > 2017-09-28 16:07 GMT+02:00 ClÃ©ment BÃ©ra <bera.clement(a)gmail.com>: > >> >> >> 2017-09-28 15:33 GMT+02:00 Ronie Salgado <roniesalg(a)gmail.com>: >> >>> Hi Clement, >>> >>> The last time I checked, the 64 bits Mac VM version is eating the >>> keyboard events, but not the mouse and other events. I guess that for the >>> minheadless this is not required. The 32 bits version of Mac works by >>> running the folowing script: >>> >>> FFIExternalStructure allSubclassesDo: #rebuildFieldAccessors >>> >>> I think that Pavel fixed this for Pharo 7. >>> >> >> Ok. >> >> I had done that. >> >> But... >> >> I don't have any keyboard events. I have mouse and window events. I am >> using Mac 32 bits. >> >> Ok... >> >> It seems that the keyboard events arrive as touch events... >> >> I will try to make that work. We'll see. >> >> Thanks >> >> >> >>> >>> >>> Btw for some reason in the one-click version of Pharo 32 bits on Mac >>>> there is 2 SDL plugins (libSDL2-2.0.0 and libSDL2), which leads to >>>> conflicts (the VM use randomly one lib or the other). I randomly chose one >>>> that I use and deleted the other one, do you have advises on which one I >>>> should prefer ? Maybe the events are working only with the other one ? >>>> >>> They should be a symlink. The correct one is the libSDL2-2.0. >>> >>> Best regards, >>> Ronie >>> >>> 2017-09-28 15:02 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>> >>>> Hi Ronie, Hi all, >>>> >>>> I am trying to use OSWindow/SDL2 in Pharo 6,1 stable, I successfully >>>> opened the window and I can draw on it with Athens (with minor changes >>>> compared to Pharo 4). However, the user events (keyboard, mouse, etc.) are >>>> not working. It seems some constants are not initialized but I am not sure >>>> what is the right way to initialize them. >>>> >>>> If I am correct Ronie you said you had a script to run to make OSWindow >>>> work in the latest Pharo version. Can you give it to me so I can use it ? I >>>> just need keyboard events for my use case. >>>> >>>> Btw for some reason in the one-click version of Pharo 32 bits on Mac >>>> there is 2 SDL plugins (libSDL2-2.0.0 and libSDL2), which leads to >>>> conflicts (the VM use randomly one lib or the other). I randomly chose one >>>> that I use and deleted the other one, do you have advises on which one I >>>> should prefer ? Maybe the events are working only with the other one ? >>>> >>>> Thanks >>>> >>> >>> >> >

Sept. 29, 2017

Re: [Pharo-dev] [Ann] Class meta annotations

by Denis Kudriashov

2017-09-28 21:12 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > I would not use meta because you would not write annotationAnnotations :) > and annotations is meta by its name. > > classAnnotation is much better than metaAnnotation > Done. > > Stef > > > On Thu, Sep 28, 2017 at 5:40 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> So I renamed it to ClassAnnotation with all related names. >> >> But I keep meta prefix in #metaAnnotations Class extension to avoid >> general name: >> >> MyClass metaAnnotations >> >> You can check updated readme for details https://github.com/dio >> nisiydk/ClassAnnotation >> >> 2017-09-26 17:31 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >>> ;) >>> >>> On Tue, Sep 26, 2017 at 1:28 PM, Ben Coman <btc(a)openinworld.com> wrote: >>> >>>> Shhh... The first rule of meta-club is we don't talk about meta-club. >>>> >>>> >>>> cheers -ben >>>> >>>> >>>> On Mon, Sep 25, 2017 at 11:09 PM, Guillermo Polito < >>>> guillermopolito(a)gmail.com> wrote: >>>> >>>>> Why calling them meta-annotation and not just annotation? Annotations >>>>> are in general already meta :) >>>>> >>>>> On Mon, Sep 25, 2017 at 5:01 PM, Denis Kudriashov < >>>>> dionisiydk(a)gmail.com> wrote: >>>>> >>>>>> Hi. >>>>>> >>>>>> I glad to present one class package which introduces reusable >>>>>> mechanism for first class annotations. >>>>>> >>>>>> The project can be found on github https://github.com/dion >>>>>> isiydk/ClassMetaAnnotation. >>>>>> And I tried to describe why it is needed in my blog >>>>>> http://dionisiydk.blogspot.fr/2017/09/class-meta-annotations.html. >>>>>> >>>>>> And here is overview: >>>>>> >>>>>> Every annotation should be subclass of ClassMetaAnnotation. To attach >>>>>> it to class you create new class side method which will return an instance >>>>>> of the annotation. Method should be marked with pragma #classMetaAnnotation: >>>>>> >>>>>> >>>>>> MyClass class>>specialAnnotation >>>>>> >>>>>> <classMetaAnnotation> >>>>>> >>>>>> ^MySpecialAnnotation new >>>>>> >>>>>> >>>>>> To query annotations from system there are two methods: >>>>>> >>>>>> 1) You can ask concrete annotation class for all declared instances: >>>>>> >>>>>> MySpecialAnnotation declaredInstances >>>>>> >>>>>> 2) You can ask given class for all attached annotations: >>>>>> >>>>>> MyClass metaAnnotations >>>>>> >>>>>> Every annotation includes information about annotated class and the >>>>>> selector of declaring method. >>>>>> All annotations are cached. So it is cheap to query them. There are >>>>>> extra messages to enumerate annotations using block. >>>>>> >>>>>> Now let's discuss it. I think it can be good addition for the Pharo >>>>>> 7. Especially that it is very small code. >>>>>> >>>>>> Also I would like to thank Marcus who helps me realize this concept >>>>>> in Commander and Calypso which I start simplify with this library. >>>>>> >>>>>> Best regards, >>>>>> Denis >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> Guille Polito >>>>> >>>>> Research Engineer >>>>> >>>>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>>>> >>>>> CRIStAL - UMR 9189 >>>>> >>>>> French National Center for Scientific Research - *http://www.cnrs.fr >>>>> <http://www.cnrs.fr>* >>>>> >>>>> >>>>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>>>> >>>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>>>> >>>> >>>> >>> >> >

Sept. 29, 2017

Re: [Pharo-dev] String Interpolation

by Pavel Krivanek

This solution will not work for environments without sources too where names like t1, t2 are used for temporary variables. Anyway, nice idea. -- Pavel Dne Ätvrtek 28. zÃ¡ÅÃ 2017 Sven Van Caekenberghe <sven(a)stfx.eu> napsal(a): > Hi, > > I got into a little office discussion about string interpolation as it is > done in different programming languages. > > In Pharo we have String>>#format: which is pretty nice. It works as > follows: > > | x y | > x := 123. > y := #foo. > 'x={1} and y={2}' format: { x. y }. > > It is also possible to use a dictionary with keys, like this: > > | x y | > x := 123. > y := #foo. > 'x={x} and y={y}' format: { #x->x. #y->y } asDictionary. > > But this is not true string interpolation as described in [ > https://en.wikipedia.org/wiki/String_interpolation ]. The idea is to > write the value generating expressions directly inside the strings. > > Since in Pharo we add features not by extending the syntax but by adding > messages I wondered if it could be done for string interpolation. The goal > is to make the following work: > > | x y | > x := 123. > y := #foo. > 'It seems x equals {x} and y equals {y} while Pi is still {Float pi}' > interpolate. > > => 'It seems x equals 123 and y equals foo while Pi is still > 3.141592653589793' > > Here is the implementation I came up with: > > String>>#interpolate > "Format the receiver by interpolating the evaluation of expressions > in between curly brackets in the context of the sender as in the > following 3 oneline examples. > 'Today is {Date today}' interpolate. > | x | x := 123. 'x equals {x} and pi equals {Float pi}' interpolate. > 'In {#strings} you can escape \{ by prefixing it with \\' interpolate." > > | senderContext | > senderContext := thisContext sender. > ^ self class new: self size streamContents: [ :out | | stream | > stream := self readStream. > [ stream atEnd ] whileFalse: [ | currentChar | > (currentChar := stream next) == ${ > ifTrue: [ | expression result | > expression := stream upTo: $}. > result := Compiler new > evaluate: expression in: senderContext to: nil notifying: > nil ifFail: [ ^ nil ] logged: false. > out nextPutAll: result asString ] > ifFalse: [ > currentChar == $\ > ifTrue: [ stream atEnd ifFalse: [ out nextPut: stream next ] > ] > ifFalse: [ out nextPut: currentChar ] ] ] ] > > It is a hack that could certainly be improved. And there is of course an > obvious security problem. > > Thoughts ? > > Sven > > >

Sept. 29, 2017

Re: [Pharo-dev] Call for little tasks for GCI

by Stephane Ducasse

I will turn the mooc challenges into tasks. On Fri, Sep 29, 2017 at 8:29 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hernan > > What we should see is that students will barely know how to program. > So any solution is good. > I think that we should ask really simple task. > > Stef > > On Fri, Sep 29, 2017 at 7:19 AM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> Hi Jigyasa, >> >> Thank you for the invitation. I read the letter, it looks interesting >> for me to participate. >> >> However I have a question about how the students can solve the exercises. >> Are they allowed to use any library or just limited to the packages >> distributed in the standard Pharo image? >> >> Cheers, >> >> HernÃ¡n >> >> >> >> >> 2017-09-28 14:41 GMT-03:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >>> Hello hernanmd, >>> >>> Please check out the link to the repository >>> (github.com/jigyasa-grover/GCI-2017-with-Pharo) it should work for you, I >>> added you as a collaborator. >>> >>> For more details on the contest and type of tasks to be created, please >>> refer: >>> 1. Resources in the repository >>> 2. Invitation Letter >>> (http://forum.world.st/Let-s-prepare-for-Google-Code-In-2017-with-Pharo-Cons…) >>> >>> Looking forward to significant contributions from your side ! >>> >>> Best Regrads >>> Jigyasa Grover >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >>> >>

Sept. 29, 2017