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

[Pharo 7.0-dev] Build #1069: Revert "22161-Add-more-log-to-bootstrap"
by ci-pharo-ci-jenkins2＠inria.fr June 18, 2018

June 18, 2018

There is a new Pharo build available! The status of the build #1069 was: SUCCESS. The Pull Request #1569 was integrated: "Revert "22161-Add-more-log-to-bootstrap"" Pull request url: https://github.com/pharo-project/pharo/pull/1569 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1068: 22161-Add-more-log-to-bootstrap
by ci-pharo-ci-jenkins2＠inria.fr June 18, 2018

June 18, 2018

There is a new Pharo build available! The status of the build #1068 was: FAILURE. The Pull Request #1559 was integrated: "22161-Add-more-log-to-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1559 Issue Url: https://pharo.fogbugz.com/f/cases/22161 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Call for TechTalks
by Marcus Denker June 18, 2018

June 18, 2018

Hi, As you might now, we organised âtech talksâ in the past: https://pharo.org/TechTalk <https://pharo.org/TechTalk> We would like to continue the next half of 2018 with this series. The form itself is quite open: it can be a lecture, a demo, or just some âguidedâ discussion on Discord. If you have ideas â> send me a mail. Marcus

3 3

[Pharo 7.0-dev] Build #1067: 22145-Extract-menu-registration-to-its-own-project
by ci-pharo-ci-jenkins2＠inria.fr June 18, 2018

June 18, 2018

There is a new Pharo build available! The status of the build #1067 was: SUCCESS. The Pull Request #1545 was integrated: "22145-Extract-menu-registration-to-its-own-project" Pull request url: https://github.com/pharo-project/pharo/pull/1545 Issue Url: https://pharo.fogbugz.com/f/cases/22145 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 11 June 2018
by estebanlm＠gmail.com June 18, 2018

June 18, 2018

Hello! This is my weekly ChangeLog, from 11 June 2018 to 17 June 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=11/6/2018&to=17/6/2018 ChangeLog ========= 15 June 2018: ------------- * I fixed a recurring error on pharo site that was preventing [http://pharo.org/news](http://pharo.org/news) to be seen. 14 June 2018: ------------- * Finally I got green on my metacello work. Before it vanishes, I made a [PR to update Pharo7](https://github.com/pharo-project/pharo/pull/1546) :) It was a lot of work, to make all parts passes tests, sometimes working "bliindly"... but well, now is there. I really hope at least we can go to metadataless format someday soon. 13 June 2018: ------------- * So, yet another SDL2 integration problem, yet another PR: [https://github.com/pharo-project/pharo/pull/1531](https://github.com/pharo-… This time, problem was that SDL2 assumes you are going to do a game, by default, hence it disables the screensaver of your computer (the one that turns off your monitor or allow a screensaver to run when you are afk some time). To fix this, I needed to add capability to set HINTS when starting SDL2, and set a HINT to prevent this disabling. 12 June 2018: ------------- * I'm still preparing a new metacello version to be integrated on Pharo 7. To allow it I pushed back changes from P7 into the metacello stream (mostly clean up made by @torsten) [Here is the PR](https://github.com/Metacello/metacello/pull/492) (still on works) 11 June 2018: ------------- * I released [tonel 1.0.7](https://github.com/pharo-vcs/tonel/releases/tag/v1.0.7) which adds support for stateful traits. cheers! Esteban

1 0

1500 pull requests closed
by Marcus Denker June 17, 2018

June 17, 2018

Hi, As of today, we closed 1500 pull requests: https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls> These of course range from trivialities to merging sub-systems with hundreds of commitsâ¦ Marcus

2 1

[Pharo 7.0-dev] Build #1066: 22162-remove-some-dead-code-in-TextEditor
by ci-pharo-ci-jenkins2＠inria.fr June 17, 2018

June 17, 2018

There is a new Pharo build available! The status of the build #1066 was: SUCCESS. The Pull Request #1561 was integrated: "22162-remove-some-dead-code-in-TextEditor" Pull request url: https://github.com/pharo-project/pharo/pull/1561 Issue Url: https://pharo.fogbugz.com/f/cases/22162 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1065: 22164-GlamourGLMUpdateMorphicTest-is-failing-randomly
by ci-pharo-ci-jenkins2＠inria.fr June 17, 2018

June 17, 2018

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

1 0

Pharo 6.1 for FreeBSD - is available somewhere?
by Petr Fischer June 17, 2018

June 17, 2018

Hello, is a compiled Pharo VM 64bit for FreeBSD somewhere? I am sticked with Linux version of Pharo 5 32bit (running it on the FreeBSD by linux compatibility layer), because actual Linux Spur 64bit VM is segfaulting randomly on FreeBSD. Maybe some FreeBSD enthusiast's already did it? I need to start a new project and I want to do it on the current Pharo (Pharo 5 32b is getting out of date). On what Linux is default 64bit VM compiled? Ubuntu? CentOS 7? I am asking because linux compatibility layer on FreeBSD is based on CentOS 7 libraries. Thanks! pf

2 1

Debugger Button Positioning
by Eliot Miranda June 16, 2018

June 16, 2018

Hi All, I've been using Pharo intensively for the first time, Pharo 7. Forgive me for starting with a complaint, but I don't have time to state all the things that are great about it; you already now ;-) One thing I find painful is the positioning of the debugger into/over/through buttons. Because these are above the context list, and you read the code like I do, one has to mouse further to reach them. I find my focus is on the highlighted method, and my cursor is typically within it (I'm dong implementors, or senders, or just looking at the code). Further, there's lots of space between the Source tab and the "Where Is?" and "Browse" buttons. Doesn't it make more sense to put the into/over/through buttons between the Source tab and the "Where Is?" button? If not, doesn't it make sense to put a copy of the buttons there where they're in much easier reach? _,,,^..^,,,_ best, Eliot

7 10