- Pharo-dev - lists.pharo.org

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

ZnUrl and mailto
by Sean P. DeNigris June 16, 2018

June 16, 2018

I have a ZnUrl subclass MailtoUrl. It was working for simple cases, but then I realized that ZnUrl assumes a single username. At first, I figured maybe mailto was such a specialized case that it wouldn't be worth reexamining, but then I noticed that ZnUrl implemented #mailToAddress so I figured it was at least worth asking about. The reason it seems important to specify the users this way is that, although the rfc [1] allows users to be specified in the query, it also says that "[that] form is NOT RECOMMENDED becauseâ¦ some existing clients ignore "to" <hfvalue>s." 1. https://tools.ietf.org/html/rfc6068 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 3

@pharoproject: > 2000 followers
by Marcus Denker June 16, 2018

June 16, 2018

@pharoproject on twitter now has >2000 followers: https://twitter.com/pharoproject

2 1

Beacon for Pharo 7
by Denis Kudriashov June 15, 2018

June 15, 2018

Hi. I was looking at Beacon again to prepare integration. Some changes was needed in baseline for better granularity. So I send pull request because I have no permissions. But now I remember that we had idea to integrate only core part of Beacon which requires MemoryLogger and TranscriptLogger. And we wanted to manage logger backends using separate baselines. So we need separate repos to have separate versioning. What you think to create new org "pharo-logging" for this purpose? It looks like current approach to manage common projects (pharo-vcs, pharo-ide). Another question is what we want: copy of BeaconCore into Pharo or load it separately like Iceberg and Calypso? We can start with loading then we will decide. Best regards, Denis

9 33

[Pharo 7.0-dev] Build #1064: 22152 Categorize in Tool-Workspace
by ci-pharo-ci-jenkins2＠inria.fr June 15, 2018

June 15, 2018

There is a new Pharo build available! The status of the build #1064 was: FAILURE. The Pull Request #1552 was integrated: "22152 Categorize in Tool-Workspace" Pull request url: https://github.com/pharo-project/pharo/pull/1552 Issue Url: https://pharo.fogbugz.com/f/cases/22152 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1063: 22150 Improve Spec-Layout
by ci-pharo-ci-jenkins2＠inria.fr June 15, 2018

June 15, 2018

There is a new Pharo build available! The status of the build #1063 was: FAILURE. The Pull Request #1550 was integrated: "22150 Improve Spec-Layout" Pull request url: https://github.com/pharo-project/pharo/pull/1550 Issue Url: https://pharo.fogbugz.com/f/cases/22150 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0