- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #323: Remove unused FFITestCallback
by ci-pharo-ci-jenkins2＠inria.fr June 10, 2019

June 10, 2019

There is a new Pharo build available! The status of the build #323 was: SUCCESS. The Pull Request #3474 was integrated: "Remove unused FFITestCallback" Pull request url: https://github.com/pharo-project/pharo/pull/3474 Issue Url: https://github.com/pharo-project/pharo/issues/3460 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #322: Revert "2568-copyUpTo-and-copyUpThrough-are-identical-in-SequencableCollection"
by ci-pharo-ci-jenkins2＠inria.fr June 10, 2019

June 10, 2019

There is a new Pharo build available! The status of the build #322 was: SUCCESS. The Pull Request #3473 was integrated: "Revert "2568-copyUpTo-and-copyUpThrough-are-identical-in-SequencableCollection"" Pull request url: https://github.com/pharo-project/pharo/pull/3473 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ZLibWriteStream compression level
by Christopher Fuhrman June 10, 2019

June 10, 2019

For my PlantUML project ( https://github.com/fuhrmanator/PlantUMLPharoGizmo ), I started to run into trouble when I have PlantUML source files that are bigger than around 900 bytes. I think I tracked it down in that ZLibWriteStream, which I used to try to achieve the deflate approach used in PlantUML. It uses an flevel=1 of compression, which is "fast", rather than flevel=2, which is "default". This results in longer URLs because the text is less compressed. I couldn't see any way to influence the kind of compression. Does anyone know of a way? I think the bug I am hitting is with the PlantUML.com's web server, since the URLs render fine on a PlantUML server running on localhost. But for compatibility, I would like to see if I can avoid the bug by changing how Pharo is doing the compression.

2 2

ESUG call for talks and registration
by StÃ©phane Ducasse June 9, 2019

June 9, 2019

Please distribute the following call The ESUG board is pleased to announce that the 27th ESUG conference/summer-school will be held in Cologne, Germany 26-30 August 2019; with Camp Smalltalk 24-25 August 2019. The conference is co-organized by ZWEIDENKER. More information at: https://esug.github.io/2019-Conference/call2019.html <https://esug.github.io/2019-Conference/call2019.html> The registration is available at: https://registration.esug.org The submissions for talks at: Submissions deadline is 15 of July 2019 (Pay attention early registration will end up 22 of July 2019) Notification of acceptance will be on done on the fly. Prospective presenters should submit a PR https://github.com/ESUG/esug.github.io/tree/source/2019-Conference/talks <https://github.com/ESUG/esug.github.io/tree/source/2019-Conference/talks> If you do not succeed to do a PR you can send an email to stephane.ducasse(a)inria.fr with [ESUG2019] in the title Title: Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

Smalltalk to Smalltalk interface
by askoh June 8, 2019

June 8, 2019

Hi: While working on VisualWorks-Python interface, it occurred to me why not have VisualWorks-Pharo interface too. Has something like that been attempted? One Smalltalk dialect to Another Smalltalk dialect interface? What would be a good way to interface them? Master-Slave? Peer to Peer? Thanks, Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

4 6

[Pharo 8.0] Build #321: Add class comment to FreeTypeFontHelp
by ci-pharo-ci-jenkins2＠inria.fr June 7, 2019

June 7, 2019

There is a new Pharo build available! The status of the build #321 was: SUCCESS. The Pull Request #3476 was integrated: "Add class comment to FreeTypeFontHelp" Pull request url: https://github.com/pharo-project/pharo/pull/3476 Issue Url: https://github.com/pharo-project/pharo/issues/3475 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #320: 3468-Slots-use-variable-name-instead-of-Object-new-as-temp
by ci-pharo-ci-jenkins2＠inria.fr June 6, 2019

June 6, 2019

There is a new Pharo build available! The status of the build #320 was: FAILURE. The Pull Request #3469 was integrated: "3468-Slots-use-variable-name-instead-of-Object-new-as-temp" Pull request url: https://github.com/pharo-project/pharo/pull/3469 Issue Url: https://github.com/pharo-project/pharo/issues/3468 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #319: 3463-StringencodeDoublingQuoteOn-does-not-do-work-anymore
by ci-pharo-ci-jenkins2＠inria.fr June 6, 2019

June 6, 2019

There is a new Pharo build available! The status of the build #319 was: SUCCESS. The Pull Request #3464 was integrated: "3463-StringencodeDoublingQuoteOn-does-not-do-work-anymore" Pull request url: https://github.com/pharo-project/pharo/pull/3464 Issue Url: https://github.com/pharo-project/pharo/issues/3463 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #318: Revert "Pharo8.0-ffi"
by ci-pharo-ci-jenkins2＠inria.fr June 6, 2019

June 6, 2019

There is a new Pharo build available! The status of the build #318 was: FAILURE. The Pull Request #3462 was integrated: "Revert "Pharo8.0-ffi"" Pull request url: https://github.com/pharo-project/pharo/pull/3462 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #314: Pharo8.0-ffi
by ci-pharo-ci-jenkins2＠inria.fr June 6, 2019

June 6, 2019

There is a new Pharo build available! The status of the build #314 was: SUCCESS. The Pull Request #3136 was integrated: "Pharo8.0-ffi" Pull request url: https://github.com/pharo-project/pharo/pull/3136 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

3 2