August 2020 - Pharo-dev - lists.pharo.org

strange bug , close a morph window => close the image
by ClÃ©ment Dutriez Aug. 4, 2020

Aug. 4, 2020

Hello, When I want to close a morph window it's close the image. Sometimes this bug appears on Pharo 8 and pharo 7 , I'm working on Linux , I don't succeed to reproduce it. Do some of you already meet this bug? -- Dutriez ClÃ©ment

1 1

Halos Broken - P9 Headless
by Sean P. DeNigris Aug. 4, 2020

Aug. 4, 2020

Morphic halos don't seem to be working with the Pharo 9 headless VM. They seem fine with headful. Where do I report this? Pharo or VM repo (or elsewhere)? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 2

Robust Functionality vs. Minimalism (was "Microdown ?")
by Sean P. DeNigris Aug. 3, 2020

Aug. 3, 2020

I wonder whether/how-best to apply our principle of minimalism when it applies to areas of the system that, while critical, seem inherently non-minimalist e.g. test harnesses, documentation, etc. I thought a lot about this when trying to document and refactor SDL. The lack of a mock library in core was a big barrier to understanding the interactions between SDL objects. Maybe I'm being naive, but I feel like if someone wants a minimal image, they're not going to want to load SUnit or rich text documentation *at all*, so I don't see the risk-benefit of crippling these features. This also applies to Pillar/Microdown. While *any* rich text comments are an exciting development, I'd like to understand the benefit of Microdown vs. full Pillar syntax. Presumably the primary benefit is the size of the codebase. Any other reasons? A few other questions about the "rich text doc" roadmap: 1. Could/will this be extended to method comments? That would be really cool :) 2. How close are we for someone to use full Pillar syntax in class comments in their own library? Any plans to make this possible? NB. I originally posted a version of this on an older thread about Pillar but and I'm assuming it may have gotten lost in that limited context. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 2

[Pharo 9.0] Build #572: Playground-Color-defined-Variables
by ci-pharo-ci-jenkins2＠inria.fr Aug. 1, 2020

Aug. 1, 2020

There is a new Pharo build available! The status of the build #572 was: FAILURE. The Pull Request #7021 was integrated: "Playground-Color-defined-Variables" Pull request url: https://github.com/pharo-project/pharo/pull/7021 Issue Url: https://github.com/pharo-project/pharo/issues/Playground Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #571: Compiler-donot-hardcode-ReservedVariables
by ci-pharo-ci-jenkins2＠inria.fr Aug. 1, 2020

Aug. 1, 2020

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

1 0