December 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] can I get Pharo7 release candidate images in PharoLauncher

by Ben Coman

On Mon, 3 Dec 2018 at 22:06, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi Ben, > > Le 3 dÃ©c. 2018 Ã 12:41, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > I updated PharoLauncher by... > loading ConfigurationOfPharoLauncher-ChristopheDemarey.92 > running ```ConfigurationOfPharoLauncher load``` > then in settings clicked "Hard reset persistent state" > > But I'm not seeing any of the release candidate images. > Should I be? > > cheers -ben > > > I wanted to publish a new release of PL today but we have issues with the > windows certificate. > To know more about the problem: > https://github.com/pharo-project/pharo-launcher/issues/281 > To solve the problem quickly (waiting for the new PL release): > in your Pharo Launcher app, hit cmd+p to open monticello browser and load > PharoLauncher-Core-TorstenBergmann.209 > > The new PL release solves this problem and externalize the definition of > template sources. > Thanks Christophe. That worked. I needed to do "Hard reset persistent state" after loading the mcz. cheers -ben

Dec. 3, 2018

Migrate PetitParser (1) on GitHub under moosetechnology organisation?

by Julien

Hello, Iâd like to migrate PetitParser (1) on GitHub under moosetechnology organisation. I have a project depending on it and there are some stuff Iâd like to fix on PetitParser 1 ConfigurationOf (which will become a baseline on GitHub). Is it ok to migrate it? Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

Dec. 3, 2018

Re: [Pharo-dev] can I get Pharo7 release candidate images in PharoLauncher

by Christophe Demarey

Hi Ben, > Le 3 dÃ©c. 2018 Ã 12:41, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > I updated PharoLauncher by... > loading ConfigurationOfPharoLauncher-ChristopheDemarey.92 > running ```ConfigurationOfPharoLauncher load``` > then in settings clicked "Hard reset persistent state" > > But I'm not seeing any of the release candidate images. > Should I be? > > cheers -ben I wanted to publish a new release of PL today but we have issues with the windows certificate. To know more about the problem: https://github.com/pharo-project/pharo-launcher/issues/281 <https://github.com/pharo-project/pharo-launcher/issues/281> To solve the problem quickly (waiting for the new PL release): in your Pharo Launcher app, hit cmd+p to open monticello browser and load PharoLauncher-Core-TorstenBergmann.209 The new PL release solves this problem and externalize the definition of template sources. Cheers, Christophe

Dec. 3, 2018

[Pharo 7.0-dev] Build #1433: 22720-add-more-tests

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

There is a new Pharo build available! The status of the build #1433 was: FAILURE. The Pull Request #2030 was integrated: "22720-add-more-tests" Pull request url: https://github.com/pharo-project/pharo/pull/2030 Issue Url: https://pharo.fogbugz.com/f/cases/22720 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 3, 2018

can I get Pharo7 release candidate images in PharoLauncher

by Ben Coman

I updated PharoLauncher by... loading ConfigurationOfPharoLauncher-ChristopheDemarey.92 running ```ConfigurationOfPharoLauncher load``` then in settings clicked "Hard reset persistent state" But I'm not seeing any of the release candidate images. Should I be? cheers -ben

Dec. 3, 2018

[Pharo 7.0-dev] Build #1432: 22718-argumentNames-should-not-use-propertyValueAt

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

There is a new Pharo build available! The status of the build #1432 was: SUCCESS. The Pull Request #2029 was integrated: "22718-argumentNames-should-not-use-propertyValueAt" Pull request url: https://github.com/pharo-project/pharo/pull/2029 Issue Url: https://pharo.fogbugz.com/f/cases/22718 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 3, 2018

[Pharo 7.0-dev] Build #1431: 22716-testDefaultWorkingDirectory-does-a-wrong-assertion

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

There is a new Pharo build available! The status of the build #1431 was: SUCCESS. The Pull Request #2027 was integrated: "22716-testDefaultWorkingDirectory-does-a-wrong-assertion" Pull request url: https://github.com/pharo-project/pharo/pull/2027 Issue Url: https://pharo.fogbugz.com/f/cases/22716 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 3, 2018

[Pharo 7.0-dev] Build #1430: Revert "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding"

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

There is a new Pharo build available! The status of the build #1430 was: FAILURE. The Pull Request #2035 was integrated: "Revert "22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding"" Pull request url: https://github.com/pharo-project/pharo/pull/2035 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 3, 2018

Re: [Pharo-dev] [Ann] Fog 1.0.0-beta

by Santiago Bragagnolo

It was late yesterday hahaha, I made many mistakes, thanks Marcus. Anyway, the address is this one: https://github.com/smartanvil/Fog <https://github.com/sbragagnolo/Fog> El lun., 3 de dic. de 2018 09:12, Marcus Denker <marcus.denker(a)inria.fr> escribiÃ³: > Link to GitHub: > > https://github.com/smartanvil/Fog <https://github.com/sbragagnolo/Fog> > > On 3 Dec 2018, at 01:20, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> > wrote: > > Hi All! > > I have being working on releasing versions (i should do it more often). > I am happy to announce Fog v1.0.0-beta. I think I found a API that i like > enough. So, i took the courage to pass to 1. > > Thew new version changes many things: Redefines the roll of the session, > it minimize the roll of the connection, it cleans up the code, it defines a > more verbose but less magic API. It generates proxies for the contracts. > > It supports now all the types including: maps and arrays. > > Goodnight :) > > > Santiago > > > Fog > > Pharo Ethereum Driver > > Fog is a library that allows the user to connect to an ethereum based > blockchain data base. > > Is based on the Javascript canonical implementation done by Ethereum > community Ethereum Javascript API > <https://github.com/ethereum/wiki/wiki/JavaScript-API>. > <https://github.com/smartanvil/Fog#dependencies> > Download code <https://github.com/smartanvil/Fog#iceberg--baseline>Iceberg > / Baseline > > Metacello > new > baseline: 'Fog'; > repository: 'github://sbragagnolo/Fog/src'; > load. > > >

Dec. 3, 2018

Re: [Pharo-dev] [Ann] Fog 1.0.0-beta

by Marcus Denker

Link to GitHub: https://github.com/sbragagnolo/Fog <https://github.com/sbragagnolo/Fog> > On 3 Dec 2018, at 01:20, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > > Hi All! > > I have being working on releasing versions (i should do it more often). > I am happy to announce Fog v1.0.0-beta. I think I found a API that i like enough. So, i took the courage to pass to 1. > > Thew new version changes many things: Redefines the roll of the session, it minimize the roll of the connection, it cleans up the code, it defines a more verbose but less magic API. It generates proxies for the contracts. > > It supports now all the types including: maps and arrays. > > Goodnight :) > > > Santiago > > > Fog > > Pharo Ethereum Driver > > Fog is a library that allows the user to connect to an ethereum based blockchain data base. > > Is based on the Javascript canonical implementation done by Ethereum community Ethereum Javascript API <https://github.com/ethereum/wiki/wiki/JavaScript-API>. > > <https://github.com/smartanvil/Fog#dependencies> > Download code > > <https://github.com/smartanvil/Fog#iceberg--baseline>Iceberg / Baseline > > Metacello > new > baseline: 'Fog'; > repository: 'github://sbragagnolo/Fog/src'; > load.

Dec. 3, 2018