May 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Has anyone got some binary search code they like for the Collection class they want to share?

by Sven Van Caekenberghe

It is already in the image: SequenceableCollection>>#findBinary:do:ifNone: & friends ;-) > On 18 May 2017, at 20:22, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > > I didn't see one in the image & I'm happy to implement one but thought I'd ask before I did. > > Thanks > > Paul

May 18, 2017

Re: [Pharo-users] Seaside: WACache had the subclass responsibility to implement #store:

by Paul DeBruicker

Hi Abdelghani, There is a seaside specific list here: http://forum.world.st/Seaside-General-f86180.html You'll have better luck getting prompt answers there. How did you install BootstrapMagritte? WACache is an abstract class in Seaside 3.2 so maybe the install process got something wrong. Paul Pharo Smalltalk Users mailing list wrote > Hi all, > > If run a new Seaside image then instal BootstrapMagrite I can no more > access the list of running apps in the seaside image from a browser > I type in firefox localhost:8080 and I get : > WACache had the subclass responsibility to implement #store: > > Any ideas? > > Thanks in advance > Abdelghani -- View this message in context: http://forum.world.st/Seaside-WACache-had-the-subclass-responsibility-to-im… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 18, 2017

Has anyone got some binary search code they like for the Collection class they want to share?

by PAUL DEBRUICKER

I didn't see one in the image & I'm happy to implement one but thought I'd ask before I did. Thanks Paul

May 18, 2017

Re: [Pharo-users] [Pharo-dev] Need help with Pillar

by Damien Pollet

On 18 May 2017 at 01:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > curl https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh | bash > > I had to copy PharoV50.sources in the folder pharo-vm/ apparently. > Hmm strange I got that this morning as well with ClÃ©ment's book. The script installs a PharoV60.sources so most probably it installs the latest VM; might be a problem if Pillar really relies on Pharo 5â¦ > Getting the archetype book gives me an error: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > /tmp/pillar> ./pillar archetype book > > Which website is it trying to get access to? > That would be Inria CI, they're having problems with CloudStack currently -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 18, 2017

Need help with Pillar

by Alexandre Bergel

Hi! I have installed Pillar on MacOSX using: curl https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh | bash I had to copy PharoV50.sources in the folder pharo-vm/ apparently. Getting the archetype book gives me an error: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /tmp/pillar> ./pillar archetype book ConnectionTimedOut: Data receive timed out. [ ConnectionTimedOut signal: 'Data receive timed out.' ] in Socket>>waitForDataFor: in Block: [ ConnectionTimedOut signal: 'Data receive timed o...etc... Socket>>waitForDataFor:ifClosed:ifTimedOut: Socket>>waitForDataFor: ZdcSecureSocketStream(ZdcAbstractSocketStream)>>socketWaitForData [ self socketWaitForData ] in ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer in Block: [ self socketWaitForData ] BlockClosure>>on:do: ZdcSecureSocketStream(ZdcSimpleSocketStream)>>fillReadBuffer ZdcSecureSocketStream(ZdcAbstractSocketStream)>>next ZnLineReader>>processNext ZnLineReader>>nextLine ZnStatusLine>>readFrom: ZnStatusLine class>>readFrom: ZnResponse>>readHeaderFrom: ZnResponse(ZnMessage)>>readStreamingFrom: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Which website is it trying to get access to? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 17, 2017

Re: [Pharo-users] Problems loading XML System ( was [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding)

by monty

For example, this: ((StAXHTMLParser onURL: aURLString) nextElementNamed: 'head') ifNotNil: [:headElement | ...] parses the document upto the next "head" element and returns it and any descendants as a DOM subtree. If there's no next "head" element, it exhausts the event stream looking for one. If you don't want that, test it first: (parser peek isStartTagNamed: 'head') ifTrue: [| headElement | headElement := parser nextNode. ...]. because you now know what kind of DOM subtree the next events represent, #nextNode is used, which builds any DOM subtree out of the next events, including an element with descendants, a string or comment node, or even an entire document (if sent before reading the start-of-document event). So this: (StAXHTMLParser onURL: aURLString) nextNode is equivalent to this: XMLHTMLParser parseURL: aURLString. StAX is more useful with XML than HTML, because XML documents can be huge. > Sent: Tuesday, May 16, 2017 at 6:39 PM > From: PBKResearch <peter(a)pbkresearch.co.uk> > To: "'Any question about pharo is welcome'" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Problems loading XML System ( was [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding) > > Monty > > Many thanks for your help. I have followed your advice to start again in a clean Moose 6.1 image, and so far everything is working fine. Apologies for getting you to sort out the results of my stupidity. In Pharo I am really an experienced beginner. > > Thanks again > > Peter Kenny > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of monty > Sent: 16 May 2017 03:37 > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] Problems loading XML System ( was [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding) > > Something went wrong during your upgrade with class initialization. > > Installing the latest versions of these projects into a clean image would work, and so would installing the latest XMLParserHTML and XMLParserStAX into the newest Moose-6.1 image (which has the latest XMLParser and XPath). > > But if you insist on upgrading your old image, try the latest ConfigurationOfXMLParser (.303.mcz) and ConfigurationOfXPath (.149.mcz) from their PharoExtras repos and install their latest project versions, and do the same with XMLParserHTML and XMLParserStAX (the older versions aren't compatible with newer XMLParser versions). Then open the test runner and run all "XML|XPath" tests. If you get any failures, evaluate this: > > #('XML-Parser' 'XPath-Core') do: [:package | > (SystemNavigation default allClassesInPackageNamed: package) do: [:class | > class initialize]] > > and try running the tests again. > > > Sent: Monday, May 15, 2017 at 6:50 PM > > From: PBKResearch <peter(a)pbkresearch.co.uk> > > To: "'Any question about pharo is welcome'" <pharo-users(a)lists.pharo.org> > > Subject: [Pharo-users] Problems loading XML System ( was Re: [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding) > > > > Monty > > > > As an update, I have rebuilt from the Moose 6.0 download. The version of XML-Parser in that was dated 18 July 2016 (configuration monty.233), so I installed versions of XML-Parser-HTML and XML-Parser-StAX contemporary with that. (The respective configurations are monty.48 and monty.39). With these versions all my previous XMLHTMLParser operations work as before, and I have been able to use the StAX parser in a simple way. So I can start exploring as I intended. > > > > I have made repeated attempts to update this rebuilt image to more recent versions of the HTML and StAX parsers, and every time I run into the same error reported below. I started from the latest version and worked backwards, but gave up quickly; it takes about 6 minutes on my machine to load and compile a version, and it soon gets tedious. If I feel more enthusiastic tomorrow, I might start working forwards from my current versions. > > > > Anyway, I now have a working system with the StaX and HTML parsers, so I can continue to explore. > > > > Best wishes > > > > Peter Kenny > > > > -----Original Message----- > > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of PBKResearch > > Sent: 15 May 2017 20:44 > > To: 'Any question about pharo is welcome' <pharo-users(a)lists.pharo.org> > > Subject: Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding > > > > Monty > > > > I have just started trying to use the StAX parsers, and I have found that the update has introduced a problem, which means that XMLHTMLParser no longer works on examples I have used before. I updated to ConfigurationOfXMLParser(monty.302), which is the latest version on the smalltalkhub repository, and then used the load version in the class comment, which loads the stable default. Similarly, I loaded ConfigurationOfXMLParserHTML(monty.62) and ConfigurationOfXMLParserStAX(monty.51), again using stable and default. When I try to run the XMLHTMLParser example I quoted below, I get an error message 'MessageNotunderstood: receiver of "critical:" is nil'. The same message comes up with anything else I try with XMLHTMLParser or with StAXHTMLParser. > > > > I am not really up to using the debugger on someone else's code, but the one thing I can see is that the problem lies in XMLKeyValueCache>>critical:, which has the code: > > ^ self mutex critical: aBlock > > The problem being that mutex is nil. > > > > In my enthusiasm, I saved the updated image with the same name as the old image, which is now therefore overwritten. If I cannot solve this problem, my only way out is to rebuild my image from the Moose 6.0 download. Any suggestions gratefully received. > > > > Thanks in advance > > > > Peter Kenny > > > > -----Original Message----- > > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of PBKResearch > > Sent: 15 May 2017 19:16 > > To: 'Any question about pharo is welcome' <pharo-users(a)lists.pharo.org> > > Subject: Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding > > > > Monty > > > > Many thanks for this. My original purpose was just to answer Paul deBruicker's query, namely to parse an html file and stop reading at the end of the <head> section. I solved this by trial and error using the code shown below ( which actually stops at the opening tag of the body). This was not my problem at all, but Paul's; I just tackled it for fun. > > > > However, you note has prompted me to update my version of the whole XML system - I was using the version I downloaded with Moose 6.0, which was dated August 2016. I am looking at the StAX parsers as a possible way of simplifying what I currently do, which involves downloading an entire web page as a DOM and then manipulating it with XPath to extract the bits I am interested in. I may be able to use StAX to do some of the selection and manipulation as I am reading. > > > > It's all a new topic to me, so I foresee a lot of experimentation. It all helps to keep the grey matter active. > > > > Thanks again > > > > Peter Kenny > > > > -----Original Message----- > > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of monty > > Sent: 15 May 2017 12:15 > > To: pharo-users(a)lists.pharo.org > > Subject: Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding > > > > For that kind of incremental parsing, you could also use XMLParserStAX, a pull-parser that parses a document as a stream of event objects you control with #next, #peek, and #atEnd. It also supports pull-DOM parsing with messages like #nextNode, #nextElement, and #nextElementNamed:, which return the next event object(s) as DOM subtrees (searchable with XPath). See the StAXParser class comment for an example. (The StAXHTMLParser class requires XMLParserHTML be installed to work.) > > > > > > > > > > > > >

May 17, 2017

Seaside: WACache had the subclass responsibility to implement #store:

by Alidra Abdelghani

Hi all, If run a new Seaside image then instal BootstrapMagrite I can no more access the list of running apps in the seaside image from a browser I type in firefox localhost:8080 and I get : WACache had the subclass responsibility to implement #store: Any ideas? Thanks in advance Abdelghani

May 17, 2017

Re: [Pharo-users] Loading Glorp+PostgreSQL

by Sven Van Caekenberghe

> On 17 May 2017, at 19:35, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > 2017-05-17 11:04 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> >>> On 17 May 2017, at 16:01, Pierce Ng <pierce(a)samadhiweb.com> wrote: >>> >>> On Tue, May 16, 2017 at 11:58:50AM +0200, Sven Van Caekenberghe wrote: >>>> I am bringing my Reddit example back up to date (https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53…) for an upcoming Pharo Booklet. > >>> I've adapted your Reddit application to work with Glorp-SQLite. It was pretty >>> much simply subclassing RedditDatabaseResource and wiring up #newGlorpSession. >>> It's a nice demo of Glorp's pluggability. >> >> That is cool. We should definitively keep a reference to that. Thanks. > > And it's better to get a non devops savvy user to get started, because > it avoids installing a PgSQL server. Yes and no. On macOS, http://postgresapp.com is dead simple for any user. > Regards! > > Esteban A. Maringolo >

May 17, 2017

Re: [Pharo-users] Loading Glorp+PostgreSQL

by Stephane Ducasse

Ahhhh this can be good for the reddit booklet :) But sven has the last word on it. On Wed, May 17, 2017 at 7:35 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2017-05-17 11:04 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > >> On 17 May 2017, at 16:01, Pierce Ng <pierce(a)samadhiweb.com> wrote: > >> > >> On Tue, May 16, 2017 at 11:58:50AM +0200, Sven Van Caekenberghe wrote: > >>> I am bringing my Reddit example back up to date (https://medium.com/ > concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b5327ca0740) for an > upcoming Pharo Booklet. > > >> I've adapted your Reddit application to work with Glorp-SQLite. It was > pretty > >> much simply subclassing RedditDatabaseResource and wiring up > #newGlorpSession. > >> It's a nice demo of Glorp's pluggability. > > > > That is cool. We should definitively keep a reference to that. Thanks. > > And it's better to get a non devops savvy user to get started, because > it avoids installing a PgSQL server. > > Regards! > > Esteban A. Maringolo > >

May 17, 2017

Re: [Pharo-users] Fwd: Re: 11/05/17 - Tabular Data Structures for Data Analysis - Oleksandr Zaytsev

by Stephane Ducasse

write some tests and ask for a good implementations. Crazy implementors like henrik can probably beat us all :) On Wed, May 17, 2017 at 7:55 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > I'm interested to help for such new "containers". > May be we should proceed that way: > > > On Tue, May 16, 2017 at 7:44 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> We may also use Discord and do something "somewhat live" >> >> Phil >> >> On Tue, May 16, 2017 at 7:23 PM, <serge.stinckwich(a)gmail.com> wrote: >> >>> I was asking Philippe but hope to see you also at ESUG ! >>> >>> EnvoyÃ© de mon iPhone >>> >>> Le 16 mai 2017 Ã 19:02, Oleksandr Zaytsev <olk.zaytsev(a)gmail.com> a >>> Ã©crit : >>> >>> I would love to, but to go to Lille from my country I would need a visa. >>> Which is not that easy to acquire. >>> So maybe I will come to PharoDays 2018. >>> And I will definitely try to come to ESUG Conference in September. >>> >>> Oleks >>> >>> On Tue, May 16, 2017 at 7:26 PM, <serge.stinckwich(a)gmail.com> wrote: >>> >>>> >>>> >>>> EnvoyÃ© de mon iPhone >>>> >>>> Le 11 mai 2017 Ã 11:43, "phil(a)highoctane.be" <phil(a)highoctane.be> a >>>> Ã©crit : >>>> >>>> ---------- Message transfÃ©rÃ© ---------- >>>> De : "phil(a)highoctane.be" <phil(a)highoctane.be> >>>> Date : 11 mai 2017 10:54 >>>> Objet : Re: 11/05/17 - Tabular Data Structures for Data Analysis - >>>> Oleksandr Zaytsev >>>> Ã : "Nick Papoylias" <npapoylias(a)gmail.com> >>>> Cc : >>>> >>>> >>>> >>>> On Thu, May 11, 2017 at 10:20 AM, Nick Papoylias <npapoylias(a)gmail.com> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Thu, May 11, 2017 at 5:24 AM, Oleksandr Zaytsev < >>>>> olk.zaytsev(a)gmail.com> wrote: >>>>> >>>>>> >>>>>> *A. Work done* >>>>>> >>>>>> - Downloaded the threaded VM as suggested by Esteban Lorenzano to >>>>>> make Iceberg work. And it does! I have successfully pushed my NeuralNetwork >>>>>> code to GitHub: https://github.com/olekscode/MLNeuralNetwork >>>>>> - Joined the PolyMath organization on GitHub >>>>>> - Created a repository for the TabularDataset project >>>>>> https://github.com/PolyMathOrg/TabularDataset >>>>>> <https://github.com/PolyMathOrg/TabularDataset> as a part of >>>>>> PolyMath organization on GitHub >>>>>> - Fixed a PolyMath issue #25 and made a PR >>>>>> - Read an article from Wolfram Mathematica documentation >>>>>> regarding Dataset. It was one of the reading suggestions sent to me by Nick >>>>>> Papoylias >>>>>> >>>>>> >>>>>> *B. Next steps* >>>>>> >>>>>> - Fix more issues of PolyMath, using Iceberg. I have to get used >>>>>> to it by the time the coding phase starts >>>>>> - Read the rest of Nick Papoylias's suggestions >>>>>> >>>>>> >>>>>> *C. Help needed* >>>>>> >>>>>> - The Dataset in Wolfram, as well as Pandas in Python, has a very >>>>>> advanced indexing system. Smalltalk has its own special conventions for >>>>>> indexing, so I think that it would be great if I got familiar with them. >>>>>> Could you suggest me some reading on this topic (what are the indexing >>>>>> conventions in Smalltalk?). >>>>>> For example, in Wolfram, I can write *dataset[[-1]]* to extract >>>>>> the last row. But in Pharo indexes can not be negative. In Pharo I would >>>>>> say *dataset last*. But how about *dataset[[-5]]*? >>>>>> >>>>>> This would be a good exercise for you ;) In Pharo you can easily add >>>>> negative indexing yourself. >>>>> >>>>> *Hint:* You know the index of the last element, since this is the >>>>> size of the collection, so... ;) >>>>> >>>>> No need for changes, this exists already. >>>> >>>> Use atWrap: index put: value and atWrap: with negative indexes. >>>> 'hello' atWrap: -2 >>>> >>>> There is a specific version for Array using a primitive. >>>> #[ 10 20 30 40 ] atWrap: -1 >>>> >>>> atWrap:0 gives you the last item. >>>> atWrap: -1 gives 30 >>>> >>>> This is different from 0 based index languages. >>>> >>>> The interesing thing about atWrap: is that it uses modulo interally so >>>> you do not need to care about that. >>>> >>>> ($/ split: 'abc/def/ghi/jkl') atWrap: -1 >>>> --> 'ghi' >>>> >>>> The Matrix class has a bunch of things API wise but the class is highly >>>> inefficient, doing copies all the time etc. It would be nice to have some >>>> kind of futures/copy on write style things in there. >>>> >>>> I miss cbind and rbind. These are useful. I have some half baked super >>>> inefficient implementations of these things for Matrix. >>>> >>>> https://stat.ethz.ch/R-manual/R-devel/library/base/html/cbind.html >>>> >>>> The ability to name columns is also nice to have. >>>> >>>> In R one does: >>>> >>>> df <- dataframe() >>>> cbind(df, c(1,2,3)) >>>> cbind(df, c(4,5,6)) >>>> names(df)<-("C1", "C2", "C3") >>>> names can be found back with: >>>> >>>> names(df) >>>> >>>> A Smalltalkish style would be welcome. >>>> >>>> >>>> >>>> >>>> Interesting ! Are you coming to PharoDays ? We can talk about that if >>>> we found time. >>>> >>>> Maybe looking at the Voyage queries can be helpful. >>>> >>>> Phil >>>> >>>> >>>> >>>>> Try adding an extention method to Ordrered or SequenceableCollection. >>>>> >>>>> If the Pharo by example chapter is not enough or the MOOC, read the >>>>> source >>>>> itself in the core, to see how basic methods are implemented (it is >>>>> less scary, >>>>> than it sounds). >>>>> >>>>> You can also try Chapters 9, 10, 11 of the blue book (some API changes >>>>> may apply): >>>>> >>>>> <http://goog_1902892863> >>>>> http://sdmeta.gforge.inria.fr/FreeBooks/BlueBook/Bluebook.pdf >>>>> >>>>> >>>>>> - Or what is the best way of implementing this index: >>>>>> *dataset[["name"]]* (extracts a named row), *dataset[[1]*] >>>>>> (extracts the first row)? Should I create two separate messages: *dataset >>>>>> rowNamed: 'name'* and *dataset rowAt: 1*? >>>>>> >>>>>> rowNamed: >>>> rowAt: >>>> >>>> yes, look like it. >>>> >>>> But if we want to model things like R dataframes for example, this has >>>> to be seen as a vectorized operation, so you can to use row slices, column >>>> slices, and logical indexes. >>>> >>>> Check this out: >>>> >>>> http://www.r-tutor.com/r-introduction/data-frame/data-frame-row-slice >>>> https://www.r-bloggers.com/working-with-data-frames/ >>>> >>>> >>>> >>>>> The internal representation of your data-structure can be anything at >>>>> the moment, *as long as you encapsulate it.* >>>>> >>>>> (ie it can be nested OrderedCollections with meta-data for >>>>> column-names to indexes, or dictionary of collections etc). >>>>> >>>>> *If you don't expose it to the user* (ie return it from the public >>>>> api, or expect knowledge of it in argument passing), >>>>> we can easily change it later. So *first make it work, and we >>>>> optimize later ;)* >>>>> >>>>> For your case it will be a little bit trickier because *you also have >>>>> the notions of a) rows and b) columns*, which >>>>> are exposed to the user. So *you would need to create abstractions* >>>>> for these too. >>>>> >>>>> Cheers, >>>>> >>>>> Nick >>>>> >>>>>> >>>>>> - >>>>>> >>>>>> >>>>>> If someone else is having problems with Iceberg on Linux, try >>>>>> downloading the threaded VM: >>>>>> >>>>>> wget -O- get.pharo.org/vmT60 | bash >>>>>> >>>>>> And use SSH (not HTTPS) remote URL. >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Pharo Google Summer of Code" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to pharo-gsoc+unsubscribe(a)googlegroups.com. >>>>>> To post to this group, send email to pharo-gsoc(a)googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/pharo-gsoc/CAEp0Uzu-8fw3dA >>>>>> 6ezVoj-QptvLcB8cWPHvZ1tfLg1Ce8qkTqfQ%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/pharo-gsoc/CAEp0Uzu-8fw3dA6ezVoj-QptvLcB8…> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Pharo Google Summer of Code" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to pharo-gsoc+unsubscribe(a)googlegroups.com. >>>>> To post to this group, send email to pharo-gsoc(a)googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/pharo-gsoc/CACEStOgLC6HbYJ >>>>> 8HBLHWfs5%2BwqN3ib_kdVGuVizx7Gh1c0sM%3DA%40mail.gmail.com >>>>> <https://groups.google.com/d/msgid/pharo-gsoc/CACEStOgLC6HbYJ8HBLHWfs5%2BwqN…> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>> >> >

May 17, 2017