- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1331: 22579 Tag and comment ManifestSystemHashing
by ci-pharo-ci-jenkins2＠inria.fr Oct. 15, 2018

Oct. 15, 2018

There is a new Pharo build available! The status of the build #1331 was: FAILURE. The Pull Request #1911 was integrated: "22579 Tag and comment ManifestSystemHashing" Pull request url: https://github.com/pharo-project/pharo/pull/1911 Issue Url: https://pharo.fogbugz.com/f/cases/22579 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 8 October 2018
by estebanlm＠gmail.com Oct. 15, 2018

Oct. 15, 2018

Hello! This is my weekly ChangeLog, from 8 October 2018 to 14 October 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=8/10/2018&to=14/10/2018 ChangeLog ========= 10 October 2018: ---------------- * I finish an [extension to the GitHub plugin](https://github.com/pharo-vcs/iceberg/issues/1008) to allow users to create branchs from a GitHub issue (same as it works now with pharo fogbugz plugin). This will be used for Pharo 8, but it can also be used by other iceberg users in any project :) cheers! Esteban

1 0

GitHub Topics
by Sven Van Caekenberghe Oct. 13, 2018

Oct. 13, 2018

One of the goals of moving to GitHub.com is to gain visibility. There is https://github.com/topics I think we should standardise how we tag our projects. So at least 'Pharo' (capitalised) should be there. Do we also add 'Smalltalk' by default ? Any other suggestions, ideas ? Sven

8 14

[Pharo 7.0-dev] Build #1330: Added getter and setter methods to Reflectivity class for the argsAsAâ¦
by ci-pharo-ci-jenkins2＠inria.fr Oct. 13, 2018

Oct. 13, 2018

There is a new Pharo build available! The status of the build #1330 was: FAILURE. The Pull Request #1906 was integrated: "Added getter and setter methods to Reflectivity class for the argsAsAâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1906 Issue Url: https://pharo.fogbugz.com/f/cases/Reflectivity Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1329: 22569-add-two-more-inspector-views-for-MetaLink-nodes-and-methods
by ci-pharo-ci-jenkins2＠inria.fr Oct. 13, 2018

Oct. 13, 2018

There is a new Pharo build available! The status of the build #1329 was: FAILURE. The Pull Request #1905 was integrated: "22569-add-two-more-inspector-views-for-MetaLink-nodes-and-methods" Pull request url: https://github.com/pharo-project/pharo/pull/1905 Issue Url: https://pharo.fogbugz.com/f/cases/22569 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Is ZipArchive broken?
by Stephane Ducasse Oct. 12, 2018

Oct. 12, 2018

Hi When I drop a MCZ on a Pharo 70 image I get an instance of Character does not understand bitOr: and I wonder if there is not a regression in ZipArchive. I can rename the file and dezip with an external tools and load the code. It happened to me with multiple mcz files. Stef

2 1

What you think about visibility of trait method in browser?
by Denis Kudriashov Oct. 12, 2018

Oct. 12, 2018

Hello. In next Calypso version the option to enable or disable trait method visibility will not be available anymore (not my choice). All trait methods installed to the class will be just a class methods like it was in Nautilus. No way to hide them. I want to ask you what you think about it. - do you prefer to see trait methods by default? - do you want feature to hide trait methods? Current Calypso support for traits follows simple principle which I found important for me. But I can be the only guy who think this way. Maybe because I meet traits in Self. So: I simply want to see in the browser what class is actually implements. If class uses TEmpty trait (with ifEmpty, isEmpty methods) I don't want to see its methods by default. When I open such class in the browser I want to see only code which class explicitly implements For me this logic is same as for superclass methods. It was my original intention for trait support in Calypso. And I would like to hear if people share it or not. (there are missing trait feature in the current approach but it is not a subject of my question. Think that everything is supported correctly) Best regards, Denis

5 5

MacOS instructions do not work on Mojave
by Jan BlizniÄenko Oct. 12, 2018

Oct. 12, 2018

Hello Before starting, note that I am not MacOS user. Most of experiments I have done on MacOS Mojave in VirualBox and with friend with mac with MacOS Mojave. On https://pharo.org/download there are instructions how to run Pharo on MacOS. These steps are however not needed for Pharo Launcher which is now default download - it runs out of a box, you just have to confirm you really want to start it. On the other hand, these instructions do not work for "Pharo standalone"/"platform"/"all in one" package at all and just with these instructions such package cannot be started. Possibility to use this package without Launcher is important to me. Error is: "Pharo6.1-64 is damaged and cannot be opened. You should move it to Trash." and not option to start anyway. There are two options on download page, but none of these work: 1) Right clicking and picking Open does not make any difference at all - same error message is the result. 2) Going through settings - Security & Privacy does not work either because option Anywhere does not appear after clicking on the lockpad and filling my password - it is just not there. Only way to overcome this is to run "sudo spctl --master-disable" in terminal, which is command that is supposed to completely turn off Gatekeeper. After this command is executed, Pharo opens just fine and even the Anywhere option appears in security settings. It means that the Pharo package is not damaged at all (as error message indicates), it is just not properly signed. <http://forum.world.st/file/t369698/Pharo-MacOS_Mojave.png> <http://forum.world.st/file/t369698/Pharo-MacOS_Mojave-2.png> Jan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

[Call for testers] Pharo Launcher 1.4.5
by Guillermo Polito Oct. 12, 2018

Oct. 12, 2018

Hi all, We have been working these last ~two weeks with Christophe on the stability of the launcher. We have prepared version 1.4.5, and we would like to have some feedback. http://files.pharo.org/pharo-launcher/1.4.5 So, we would really LOVE, if somebody can play with this version and send us feedback. Specially, if your username in your machine has characters that encoded take more than 1 byte, we really would like your feedback. We have tested with japanese characters, and others like Ã®,Ã¼, etc, but the more the better. The main focus was on: - correct management of encodings (in all platforms) - of environment variables - of files and paths - of commands called through OSProcess - better error management in case of edge cases (like when we cannot determine the version of an image) Just FYI: the major limitation of the launcher right now (and it was like that since ever) is that we cannot call external processes with non-ascii characters in windows. This happens because ProcessWrapper uses the ascii version of the windows API to create a process. With what we have learnt this week, we would like to push some of these fixes to Pharo7 too soon: - Correct encoding/decoding of environment variables in linux/osx - Ability to access the encoded version of environment variables in linux/osx to give users control over the encoding they want (or even access binary data) - Correct encoding/decoding of environment variables in windows by using the correct windows API (current primitiveGetenv in windows uses Ascii version too...) In the long term, we also need a solution to enhance or replace ProcessWrapper using the W (wide) version of the windows API. But that is far more work... GC, Guille & Christophe

1 0

Laucher cannot start a fresh 7 image
by phil＠highoctane.be Oct. 12, 2018

Oct. 12, 2018

Used to work. Then does not anymore. Phil

3 3