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

[Pharo 7.0] Build #61: 22809 Cleanup MethodFinderTest and related sample classes
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #61 was: FAILURE. The Pull Request #2101 was integrated: "22809 Cleanup MethodFinderTest and related sample classes" Pull request url: https://github.com/pharo-project/pharo/pull/2101 Issue Url: https://pharo.fogbugz.com/f/cases/22809 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Catalog Entries
by Sven Van Caekenberghe Dec. 19, 2018

Dec. 19, 2018

Hi, So we have the Catalog with version specific repositories for ConfigurationOfXYZ packages/classes. I am assuming that we will be keeping this system for at least Pharo 7 and possibly 8. Can one define Catalog entries using BaselineOfXYZ ? Is that recommended ? Or should a mostly empty ConfigurationOfXYZ be used that internally refers to the BaselineOfXYZ ? Sven

7 26

[Pharo 7.0] Build #60: 22777 ManifestMonticello and ManifestRingMonticello should be tagged with "Manifest"
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #60 was: SUCCESS. The Pull Request #2076 was integrated: "22777 ManifestMonticello and ManifestRingMonticello should be tagged with "Manifest"" Pull request url: https://github.com/pharo-project/pharo/pull/2076 Issue Url: https://pharo.fogbugz.com/f/cases/22777 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #59: 22806 Small cleanups in EmbeddedFreeTypeFontInstallerTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

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

1 0

Re: [Pharo-dev] Huge Critiques Area in Calypso in Pharo 7
by Denis Kudriashov Dec. 18, 2018

Dec. 18, 2018

Hi Petr. Setting would be nice. I did not know about it in Nautilus Ð²Ñ, 18 Ð´ÐµÐº. 2018 Ð³. Ð² 14:44, Petr Fischer via Pharo-dev < pharo-dev(a)lists.pharo.org>: > I have that feeling too - critiques pane is annoying + occupying too much > place - what about showing critiques inline only (in the line nubers and > breakpoint markers left pane)? > > This choice existed for the old Nautilus browser - but I can't find it for > Calypso. > > pf > > > I am seeing a huge (multiline, ~ 5 to 7 lines) high 'critiques' area at > the bottom of Calypso browsers in Pharo 7 (dl today), see screenshot: > > > > > > Why is that ? I can't resize it to be smaller. > > On a smaller screen this takes up way too much space. > > Can't we have a widget to remove/collapse that area ? Not a setting. > > > > Sven > > > >

1 0

Huge Critiques Area in Calypso in Pharo 7
by Sven Van Caekenberghe Dec. 18, 2018

Dec. 18, 2018

I am seeing a huge (multiline, ~ 5 to 7 lines) high 'critiques' area at the bottom of Calypso browsers in Pharo 7 (dl today), see screenshot: Why is that ? I can't resize it to be smaller. On a smaller screen this takes up way too much space. Can't we have a widget to remove/collapse that area ? Not a setting. Sven

3 5

[Pharo 7.0] Build #58: 22797 deprecated file does not exist should be moved to deprecated70 package
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2018

Dec. 18, 2018

There is a new Pharo build available! The status of the build #58 was: FAILURE. The Pull Request #2092 was integrated: "22797 deprecated file does not exist should be moved to deprecated70 package" Pull request url: https://github.com/pharo-project/pharo/pull/2092 Issue Url: https://pharo.fogbugz.com/f/cases/22797 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

possible QA rule - cascading to class
by Ben Coman Dec. 18, 2018

Dec. 18, 2018

In case someone close to managing the QA rules is interested... on discord it was suggested that this form of cascading might be a trap for newcomers. x := MyClass new; foo I've never seen similar in practice, so it might make a good QA rule. It currently raises "Sends unknown message to global" but I'd guess a more specific message that actually mentions "cascading" could be possible. cheers -ben

2 1

[Pharo 7.0] Build #57: 22780 Fix uncategorized classes in MonticelloGUI
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2018

Dec. 18, 2018

There is a new Pharo build available! The status of the build #57 was: FAILURE. The Pull Request #2078 was integrated: "22780 Fix uncategorized classes in MonticelloGUI" Pull request url: https://github.com/pharo-project/pharo/pull/2078 Issue Url: https://pharo.fogbugz.com/f/cases/22780 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #56: 22760 RBRefactoryClassChange should define #isAbstract with true
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2018

Dec. 18, 2018

There is a new Pharo build available! The status of the build #56 was: FAILURE. The Pull Request #2084 was integrated: "22760 RBRefactoryClassChange should define #isAbstract with true" Pull request url: https://github.com/pharo-project/pharo/pull/2084 Issue Url: https://pharo.fogbugz.com/f/cases/22760 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0