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

[Pharo 8.0] Build #94: 2683-Remove-deprecated-pragma-to-use-deprecated-method
by ci-pharo-ci-jenkins2＠inria.fr Feb. 22, 2019

Feb. 22, 2019

There is a new Pharo build available! The status of the build #94 was: SUCCESS. The Pull Request #2686 was integrated: "2683-Remove-deprecated-pragma-to-use-deprecated-method" Pull request url: https://github.com/pharo-project/pharo/pull/2686 Issue Url: https://pharo.fogbugz.com/f/cases/2683 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Remember to registrar to Pharo days 2019!
by Esteban Lorenzano Feb. 22, 2019

Feb. 22, 2019

Dear all, Pharo days registration is open since two weeks now, and we are starting to work on the schedule and organising the social event :) Register now! Pharo days is a gathering of the Pharo community to exchange, discuss and code with your online colleagues. Join us to share your experiences and help to make a better Pharo! To register, please proceed to the Pharo Days 2019 web page: https://pharo.org/2019PharoDays <https://pharo.org/2019PharoDays>, or go directly to the association event: https://association.pharo.org/event-3255426 <https://association.pharo.org/event-3255426>. (Yes, the schedule is still to be defined, stay tuned). If there are any questions or problems, I am happy to answer them. Esteban

1 0

[Pharo 8.0] Build #93: 2670-Update-the-checkVMVersion-date
by ci-pharo-ci-jenkins2＠inria.fr Feb. 22, 2019

Feb. 22, 2019

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

1 0

[Pharo 8.0] Build #92: 2668-Improve-some-randomly-failing-test-to-give-better-trace
by ci-pharo-ci-jenkins2＠inria.fr Feb. 22, 2019

Feb. 22, 2019

There is a new Pharo build available! The status of the build #92 was: SUCCESS. The Pull Request #2669 was integrated: "2668-Improve-some-randomly-failing-test-to-give-better-trace" Pull request url: https://github.com/pharo-project/pharo/pull/2669 Issue Url: https://pharo.fogbugz.com/f/cases/2668 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Bug in Regex?
by Mariano Martinez Peck Feb. 22, 2019

Feb. 22, 2019

Hi guys, Look at this case: `'25' matchesRegex: '([0-9]|[1-9][0-9])' -> false` `'25' matchesRegex: '([1-9][0-9]|[0-9])' -> true` That is, ( a | b ) is not euqal to ( b | a ) " a or b is not equal to b or a" and should describe a range of 0 to 99. I don't understand why the first sentence answers false. Even Pharo 1.1 answers false (so this is very very old behavior). I checked on other dialects and it answers true. I then checked here [1] and it also find matches. So...do you see some rational explanation or sounds like a bug? [1] https://regex101.com/r/MqVXz8/1 -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

4 10

[ANN] ba-st Web stack updated (RenoirSt, Willow and HighchartsSt)
by Gabriel Cotelli Feb. 21, 2019

Feb. 21, 2019

Now that Pharo 7 is finally released, we took some time to update the whole web stack hosted at ba-st <https://github.com/ba-st>. As a general update all the projects now follow the brand new community guidelines <https://github.com/ba-st/Community> and support Pharo 6.1â32 bits and Pharo 7â32 & 64 bits. The build matrix now includes Pharo 8 as a preview. This includes new versions of RenoirSt, HighchartsSt, Boardwalk, Willow and it's related projects. You can see the detailed announcement here <https://medium.com/ba-st/web-stack-summer-release-1d141b2660ee>. Regards, Gabriel

1 0

[ANN] Pharo Consortium New Academic Member: TecnolÃ³gico de Monterrey in Guadalajara
by Marcus Denker Feb. 21, 2019

Feb. 21, 2019

The Pharo Consortium is very happy to announce that TecnolÃ³gico de Monterrey in Guadalajara has joined the Consortium as an Academic Member. About - TecnolÃ³gico de Monterrey in Guadalajara: http://www.gda.itesm.mx - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

1 0

[ANN] Buoy v5.0.0 released!
by Gabriel Cotelli Feb. 21, 2019

Feb. 21, 2019

Buoy <https://github.com/ba-st/Buoy>, the project aiming to complement Pharo <https://www.pharo.org> adding useful extensions reached itâs 5.0.0 version. The supported Pharo versions are 6.1 â 32 bits and 7.0 â 32 & 64 bits. The breaking changes are just in the package organization, so you may have to adapt your baseline dependencies but the rest of the code is backwards compatible with version 4. You can see the detailed release notes here. <https://medium.com/ba-st/buoy-v5-0-0-released-9a26da396ceb> Regards, Gabriel

1 0

Host window icon
by Cyril Ferlicot Feb. 21, 2019

Feb. 21, 2019

Hi, Currently, the CI of Pharo has two non random test failures. windows-32 / Tests-windows-32 / testHostWindowIcon â Windows32.Graphics.Tests.Primitives.DisplayScreenTest windows-32 / Tests-windows-32 / testHostWindowIconWrongTypeOfArgument â Windows32.Graphics.Tests.Primitives.DisplayScreenTest I know this was a part of the system was improved during Pharo 7 to be able to display a custom icon at the top of the window. Does someone knows why it is failing? Or should we investigate? -- Cyril Ferlicot https://ferlicot.fr

1 0

Question on KmGlobalDispatcher
by David Richards Feb. 20, 2019

Feb. 20, 2019

Why does the class name KmGlobalDispatcher have a small 'm'? Should it be more consistently named KMGlobalDispatcher, as all other classes in package: 'Keymapping-Core'? Object subclass: #KmGlobalDispatcher instanceVariableNames: 'dispatcher' classVariableNames: '' package: 'Keymapping-Core' Just curious why this name seems inconsistent. I don't recall seeing an inconsistency with class name prefixes in any other package group. Is this just a mistake, or rather an opportunity to learn something interesting about how classes should be named in Pharo? As a beginner, I'm not sure which. Thanks David

3 3