- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1434: 22687-Update-Tonel
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

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

1 0

Migrate PetitParser (1) on GitHub under moosetechnology organisation?
by Julien Dec. 3, 2018

Dec. 3, 2018

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

2 3

can I get Pharo7 release candidate images in PharoLauncher
by Ben Coman Dec. 3, 2018

Dec. 3, 2018

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

2 2

[Pharo 7.0-dev] Build #1433: 22720-add-more-tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

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…

1 0

[Pharo 7.0-dev] Build #1432: 22718-argumentNames-should-not-use-propertyValueAt
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

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…

1 0

[Pharo 7.0-dev] Build #1431: 22716-testDefaultWorkingDirectory-does-a-wrong-assertion
by ci-pharo-ci-jenkins2＠inria.fr Dec. 3, 2018

Dec. 3, 2018

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…

1 0

[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 Dec. 3, 2018

Dec. 3, 2018

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…

1 0

[Ann] Fog 1.0.0-beta
by Santiago Bragagnolo Dec. 3, 2018

Dec. 3, 2018

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.

2 3

Version control of Playground scripts
by Christopher Fuhrman Dec. 2, 2018

Dec. 2, 2018

Hello, In Pharo 6.1 I have got Iceberg working and love the interface to GitHub. Thanks to the Rmod folks for all the patient answers to my newbie questions. However, most of my development remains in playground scripts, and as far I understand, it's not possible to put them under version control with Iceberg. My scripts *could* be turned into classes eventually (some already have been and are under Iceberg). But it feels frustrating to rush it, just to get the versioning. I know how to save Playground files to the web, which is useful, but of course not version control per se. Knowing Playground files are saved on local disk, I got to thinking... What would be the risk(s) of using git outside Pharo, on the Playground files' directory? Has anyone tried that before? Cheers, Christopher

5 6

[Pharo 7.0-dev] Build #1429: 22679-Metacello-attributes-should-be-based-on-SystemVersion-instead-of-hardcoding
by ci-pharo-ci-jenkins2＠inria.fr Nov. 30, 2018

Nov. 30, 2018

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

1 0