September 2017 - Pharo-dev - lists.pharo.org

Pharo-Launcher Windows 10 requires admin privilg
by Alex Laurie Sept. 20, 2017

Sept. 20, 2017

Latest version of Pharo launcher requires Admin privileges to launch properly. If it doesn't have Admin permission it throws a "stdout does not exist." error. Not sure if this is the right mailing list for the launcher, if not let me know. Cheers, Alex

3 2

Iceberg
by Aliaksei Syrel Sept. 20, 2017

Sept. 20, 2017

Hi, It is amazing to see how fast Pharo progresses and moves closer to release. Therefore it may happen that after a week of absence there is so much new stuff that I just loose track of changes and sometimes old behaviour does not correspond new reality and "nothing works" :) Probably it is my case now. I would like to work on a project hosted on github. I tried iceberg:dev-0.4, iceberg:dev-0.5, iceberg-master but didn't succeed.. Here is what I get when try to clone repository both from Playground or by using "+" clone button in Iceberg both dev-04 and dev-05 [image: Inline images 1] If I try to load Iceberg master in the Image I get this: [image: Inline images 2] I am sure I do something wrong, so I recorded three videos - one for every Iceberg version. â Iceberg-0.4.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTLTZvejdYTkNfaWM/view?usp=drive…> ââ Iceberg-0.5.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTbDJNZnJMeUJEYk0/view?usp=drive…> ââ Iceberg-master.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTVzhGQmJOVzN3akU/view?usp=drive…> â VM: pharo-mac-i386-201705051953-b8db6de Image: 60482 OS: macOS Sierra 10.12.4 P.S. Still getting black screen when open an Image until I click... Cheers, Alex

8 11

[Pharo 7.0-dev] Build #138: 20443-SDL-Event-not-initialized
by ci-pharo-ci-jenkins2＠inria.fr Sept. 20, 2017

Sept. 20, 2017

There is a new Pharo build available! The status of the build #138 was: SUCCESS. The Pull Request #300 was integrated: "20443-SDL-Event-not-initialized" Pull request url: https://github.com/pharo-project/pharo/pull/300 Issue Url: https://pharo.fogbugz.com/f/cases/20443 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #137: 20435-The-CI-process-should-fail-if-the-conversion-fails
by ci-pharo-ci-jenkins2＠inria.fr Sept. 20, 2017

Sept. 20, 2017

There is a new Pharo build available! The status of the build #137 was: SUCCESS. The Pull Request #292 was integrated: "20435-The-CI-process-should-fail-if-the-conversion-fails" Pull request url: https://github.com/pharo-project/pharo/pull/292 Issue Url: https://pharo.fogbugz.com/f/cases/20435 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #136: 20415-Restore-the-extra-morphic-worlds-properly-on-startup
by ci-pharo-ci-jenkins2＠inria.fr Sept. 20, 2017

Sept. 20, 2017

There is a new Pharo build available! The status of the build #136 was: SUCCESS. The Pull Request #298 was integrated: "20415-Restore-the-extra-morphic-worlds-properly-on-startup" Pull request url: https://github.com/pharo-project/pharo/pull/298 Issue Url: https://pharo.fogbugz.com/f/cases/20415 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #134: 20431-Move-initialization-of-Color-InstructionStream-and-SmallInteger
by ci-pharo-ci-jenkins2＠inria.fr Sept. 20, 2017

Sept. 20, 2017

There is a new Pharo build available! The status of the build #134 was: SUCCESS. The Pull Request #290 was integrated: "20431-Move-initialization-of-Color-InstructionStream-and-SmallInteger" Pull request url: https://github.com/pharo-project/pharo/pull/290 Issue Url: https://pharo.fogbugz.com/f/cases/20431 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #133: 20437 recategorized methods
by ci-pharo-ci-jenkins2＠inria.fr Sept. 20, 2017

Sept. 20, 2017

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

1 0

TechTalk today, 17h UTC "Free talk Pharo 7"
by Esteban Lorenzano Sept. 19, 2017

Sept. 19, 2017

Hi, Today we have the montly TechTalk at 17hs UTC. x So far, I think this is something I would like to talk: - new development process status - tonel 1.0/iceberg 0.6 status butâ¦ subject is âfree talkâ so prepare your questions/opinions :) Esteban

5 6

[Calypso] Toolbar and Statusbar Look - voting time
by Torsten Bergmann Sept. 19, 2017

Sept. 19, 2017

Hi all, as you know Denis Kudriashov does a fantastic job in implementing the new Calypso system browser. The plan is that at some point in time will be a replacement for Nautilus in the standard image. Even if not yet integrated one can already use it (either by loading from catalog or github [1]) For me the more I use it (and get used to it) the more I like Calypso and I guess others enjoy it too already. But unfortunately there is a single but very prominently visible UI thing that I dislike on the current look: For the "Pharo3Theme" (light theme) the current implementation of Calypso has a white toolbar in the middle and a white status bar at the bottom. Technically Dennis sets the colors of these morphs to transparent to have this effect (see LEFT example of the attached screenshot) To me this lookes strange and unusual because - usually (on Windows, GTK, Java Swing, Linux window managers) such areas like a status bar follow the window color and are displayed in gray when that is the default window theme color (see [2], [3], [4]) - these white bars would better fit for the "Glamorous Whitespace" theme (as this theme is already more white areas) Also the current white bars do not make a pleasant contrast to the other panes of Calypso: - there is not really a visual distinction to the package/class/protocol-tag/method panes and filters for the middle part (toolbar) - there is not really a visual distinction from the code pane for the bottom part (statusbar) - the divider line in the code pane just stops in a white area without borders To me this looks rather ugly and I would like Pharo to look more professional and clean ;) So I proposed a simple PR [5] today to change this and technically using the window color of the theme - the result can be seen on the right side of the attached screenshot and discussed with Denis on Discord. Denis on the other hand still likes the white approach on the left more while I prefer the right one. He wrote that he wants other people comment on this issue first to which I agree and therefore I write this mail to discuss it here on the dev-list and find out about what the majority in the community prefers. So it would be good if others could - comment about their personal preference - or just vote with "LEFT" (white/transparent) or "RIGHT" (window color) in reply to this mail - or make another proposal (which is only accepted with screenshot and PR ;) Also please do not mix other UI discussions into this thread. Thanks in advance! Bye T. [1] https://github.com/dionisiydk/Calypso [2] http://cdn.osxdaily.com/wp-content/uploads/2011/08/show-status-bar-and-disk… [3] http://i.stack.imgur.com/pgt5n.png [4] http://python.zirael.org/gtk-statusbar1-1.png [5] https://github.com/dionisiydk/Calypso/pull/91

9 14

[Pharo 7.0-dev] Build #132: 20436-Pull-request-URL-in-build-information-e-mail-is-wrong
by ci-pharo-ci-jenkins2＠inria.fr Sept. 19, 2017

Sept. 19, 2017

There is a new Pharo build available! The status of the build #132 was: SUCCESS. The Pull Request #293 was integrated: "20436-Pull-request-URL-in-build-information-e-mail-is-wrong" Pull request url: https://github.com/pharo-project/pharo/pull/293 Issue Url: https://pharo.fogbugz.com/f/cases/20436 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0