- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Where is the latest linux vm?

by stephan

On 01-12-17 11:16, stephan wrote: > Is the latest really from august? Ping

Dec. 1, 2017

Re: [Pharo-dev] Moving from mc to tonel?

by Martin Dias

Julien, I dodn't know it but anyway my issue was just in the step smalltalkhub -> filtree using the migration tool. Peter, yes it's public. This is the code I used: ---------------------------------------- migration := GitMigration on: 'MartinDias/Epicea'. migration cacheAllVersions. migration authors: { 'md' -> #('Martin Dias' '<tinchodias(a)gmail.com>'). 'MD' -> #('Martin Dias' '<tinchodias(a)gmail.com>'). 'MartinDias' -> #('Martin Dias' '<tinchodias(a)gmail.com>'). 'PabloTesone' -> #('Pablo Tesone' '<tesonep(a)gmail.com>'). 'PavelKrivanek' -> #('Pavel Krivanek' '<pavel.krivanek(a)gmail.com>'). 'DamienCassou' -> #('Damien Cassou' '<DamienCassou(a)gmail.com>'). 'DenisKudryashov' -> #('Denis Kudryashov' '<dionisiydk(a)gmail.com>'). 'GustavoSantos' -> #('Gustavo Santos' '<gugajansen(a)gmail.com>'). 'ThomasHeniart' -> #('Thomas Heniart' '<heniart.thomas(a)gmail.com>'). 'LucasGodoy' -> #('Lucas Godoy' '<godoy.lucas(a)gmail.com>'). 'StephaneDucasse' -> #('Stephane Ducasse' '<stephane.ducasse(a)inria.fr>'). 'VincentBlondeau' -> #('Vincent Blondeau' '<vincent.blondeau(a)inria.fr>'). 'AlbertoBacchelli' -> #('Alberto Bacchelli' '<sbackg(a)gmail.com>'). 'SkipLentz' -> #('Skip Lentz' '<skippetie(a)gmail.com>'). 'TheIntegrator' -> #('The Integrator' '<integrator(a)fake.com>'). }.l migration fastImportCodeToDirectory: 'src' initialCommit: '18a30d8d' to: './epicea-fast-import.txt' ---------------------- MartÃn On Thu, Nov 30, 2017 at 2:14 PM, Julien <julien.delplanque(a)inria.fr> wrote: > If you use Traits and want to have Epicea loadable from GitHub on Pharo > 6.1, it will not work. > > There is an issue when you try to load a Trait in Tonel format in the > image. > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille 1 > http://juliendelplanque.be/phd.html > Equipe Rmod, Inria > BÃ¢timent B 40, avenue Halley 59650 > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve%C2%A0d'Ascq&entry=gmail&source=g> > Villeneuve > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve%C2%A0d'Ascq&entry=gmail&source=g> > d'Ascq > <https://maps.google.com/?q=40,+avenue+Halley+59650%C2%A0Villeneuve%C2%A0d'Ascq&entry=gmail&source=g> > NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > > Le 6 nov. 2017 Ã 01:42, Martin Dias <tinchodias(a)gmail.com> a Ã©crit : > > Hi all, I'm considering to move Epicea (+Ombu+Hiedra) to github. I read > that tonel is the new format and there is Peter's git-migration, which > could be the tool to do it. > > Is it good idea to move now? > Is it the right tool? > > Bests, > MartÃn > > >

Dec. 1, 2017

[Pharo 7.0-dev] Build #355: 20800-do-not-open-welcome-window-for-now

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #355 was: FAILURE. The Pull Request #568 was integrated: "20800-do-not-open-welcome-window-for-now" Pull request url: https://github.com/pharo-project/pharo/pull/568 Issue Url: https://pharo.fogbugz.com/f/cases/20800 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 1, 2017

[ANN] New Academic Partner: USI Software Institute

by Marcus Denker

The Pharo Consortium is very happy to announce that the Software Institute of the UniversitÃ della Svizzera italiana has joined as a Academic Partner. About - USI Software Institute: https://www.si.usi.ch <https://www.si.usi.ch/> - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org <http://association.pharo.org/>

Dec. 1, 2017

Re: [Pharo-dev] Polymorphism between Strings and FileReference

by Cyril Ferlicot

On Fri, Dec 1, 2017 at 12:17 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Cyril, > > > Sorry, I misunderstood. > No problem :) > This looks like a good addition. Although is there any reason it > shouldn't be added to SequenceableCollection, where #readStream and > #writeStream are defined? > I agree. I talked about string because it is my use case but it's true it should be with #readStream/#writeStream. > Cheers, > Alistair > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 1, 2017

Re: [Pharo-dev] Polymorphism between Strings and FileReference

by Alistair Grant

Hi Cyril, On 1 December 2017 at 12:04, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > On Fri, Dec 1, 2017 at 11:55 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Cyril, >> >> The normal way to handle this is #asFileReference, so you can just have: >> >> aStringOrReference asFileReference readStreamDo: ... >> > > In that case, if it is a String like 'test', we will get a readStream > on the file './test' and not on the string 'test'. This is not what I > want. > > What I want is this for example: > > > > MyClass>>addComaAtTheEndOf: aStringOrFileReference > "If the argument is a String, add a coma at the end. If the > parameter is a file, add a coma at the end of its contents" > > aStringOrFileReference writeStreamDo: [ :s | s atEnd; nextPut: $, ] > > > > If I use your code, it will not add a coma at the end of the string > parameter, but at the end of the file represented by the string if it > exists. Sorry, I misunderstood. This looks like a good addition. Although is there any reason it shouldn't be added to SequenceableCollection, where #readStream and #writeStream are defined? Cheers, Alistair

Dec. 1, 2017

Re: [Pharo-dev] Polymorphism between Strings and FileReference

by Cyril Ferlicot

On Fri, Dec 1, 2017 at 11:55 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Cyril, > > The normal way to handle this is #asFileReference, so you can just have: > > aStringOrReference asFileReference readStreamDo: ... > In that case, if it is a String like 'test', we will get a readStream on the file './test' and not on the string 'test'. This is not what I want. What I want is this for example: MyClass>>addComaAtTheEndOf: aStringOrFileReference "If the argument is a String, add a coma at the end. If the parameter is a file, add a coma at the end of its contents" aStringOrFileReference writeStreamDo: [ :s | s atEnd; nextPut: $, ] If I use your code, it will not add a coma at the end of the string parameter, but at the end of the file represented by the string if it exists. > Cheers, > Alistair > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 1, 2017

[TechTalk] Topics Wanted for 2018!

by Marcus Denker

Hi, As you know, we are trying to have one Pharo tech-talk per month. The idea is to use this for -> mini âLecturesâ -> Demos of interesting Projects -> Just some interesting topic to discuss with audio chat on Discord You can see the past topics here: http://pharo.org/TechTalk <http://pharo.org/TechTalk> We will soon define the dates for the first half of 2018. If you want to do a techtalk yourself (give a presentation / Demo or moderate a discussion), feel free to contact me! You are able to pick a date that works best for you. Marcus

Dec. 1, 2017

Re: [Pharo-dev] Polymorphism between Strings and FileReference

by Alistair Grant

Hi Cyril, On 1 December 2017 at 11:50, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > Hi, > > I am often in the case where I have a method taking a file or a string > as parameter and I often want to use #readStreamDo:/#writeStreamDo: in > the method because with I do not have to care if I need to close the > file stream or not with those. But since String do not understand > #readStreamDo:/#writeStreamDo: I cannot do that. > > Maybe it's worth to implement them on String? > > https://pharo.fogbugz.com/f/cases/20796/String-should-understand-readStream… > > Since it add methods to String I prefer talk about it on the mailing > list to have everyone's advice. The normal way to handle this is #asFileReference, so you can just have: aStringOrReference asFileReference readStreamDo: ... Cheers, Alistair

Dec. 1, 2017

Polymorphism between Strings and FileReference

by Cyril Ferlicot

Hi, I am often in the case where I have a method taking a file or a string as parameter and I often want to use #readStreamDo:/#writeStreamDo: in the method because with I do not have to care if I need to close the file stream or not with those. But since String do not understand #readStreamDo:/#writeStreamDo: I cannot do that. Maybe it's worth to implement them on String? https://pharo.fogbugz.com/f/cases/20796/String-should-understand-readStream… Since it add methods to String I prefer talk about it on the mailing list to have everyone's advice. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 1, 2017