June 2019 - Pharo-dev - lists.pharo.org

Iceberg: No Project Founds
by Shaping June 2, 2019

June 2, 2019

>From a 64-bit Pharo 7.0.3 I cloned UpdatedPharoByExample and immediately saw in red âNo Project Foundâ. Why is this and what must I do to fix it? GitKraken shows that the repo is healthy. I tried pointing Iceberg in a virgin Pharo to the same folder, got the same result. Shaping

2 2

Environments
by Shaping June 2, 2019

June 2, 2019

Does anyone have experience with Squeak Environments? This came up in the Cuis list. Environments are Squeakâs attempt at a module or namespace system. Does this exist for Pharo? Has anyone worked with it, and found it to be usable? Shaping

5 10

[Pharo 8.0] Build #307: 3064-Each-assert-like-method-in-TestRunner-should-have-the-dual-deny-method
by ci-pharo-ci-jenkins2＠inria.fr June 2, 2019

June 2, 2019

There is a new Pharo build available! The status of the build #307 was: SUCCESS. The Pull Request #3403 was integrated: "3064-Each-assert-like-method-in-TestRunner-should-have-the-dual-deny-method" Pull request url: https://github.com/pharo-project/pharo/pull/3403 Issue Url: https://github.com/pharo-project/pharo/issues/3064 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #306: Update CODE_OF_CONDUCT.md
by ci-pharo-ci-jenkins2＠inria.fr June 2, 2019

June 2, 2019

There is a new Pharo build available! The status of the build #306 was: FAILURE. The Pull Request #3441 was integrated: "Update CODE_OF_CONDUCT.md" Pull request url: https://github.com/pharo-project/pharo/pull/3441 Issue Url: https://github.com/pharo-project/pharo/issues/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

automatic field-size adjustment to font-change not working on window open
by Shaping June 2, 2019

June 2, 2019

Sorry, I spoke to soon. There are still reformatting problems when reopening the windows after a font change, say, the Settings window. If you choose, for example Fira Code 11 and Force All across all categories of use, you'll see the following in one stretch of Settings, which shows truncated labels under QualityAssistant. The rest of Settings has similar problems. Can this truncated-label problem be corrected now without waiting for Spec? I would think that the problem is caused by not having the internal reformatting ability already there in all GUIs or by not making a system-wide announcement to all GUIs when a font is changed, so that the resize/reformat can be triggered. Note that field-resizings are not happening even on reopen. Can someone fill me in on the problem and the anticipated fix and ETA? Shaping From: Shaping [mailto:shaping@uurda.org] Sent: Sunday, June 2, 2019 02:44 To: 'Pharo Development List' <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] automatic field-size adjustment to font-change Shaping1 wrote > that Pharo labels are truncated if you switch to a monospace font Did you try doing this before opening any windows? There is a problem that sometimes already-open tools are not properly updated when the font is changed... Yes, that's the problem. All windows open before the font-change must be re-opened. The font does visibly change before the reopening, but the field-size adjustment needed to see all the text does not happen until after reopening. Will Spec fix this? Thanks. Shaping

1 0

automatic field-size adjustment to font-change
by Shaping June 2, 2019

June 2, 2019

Shaping1 wrote > that Pharo labels are truncated if you switch to a monospace font Did you try doing this before opening any windows? There is a problem that sometimes already-open tools are not properly updated when the font is changed... Yes, that's the problem. All windows open before the font-change must be re-opened. The font does visibly change before the reopening, but the field-size adjustment needed to see all the text does not happen until after reopening. Will Spec fix this? Thanks. Shaping

1 0