- Pharo-dev - lists.pharo.org

Zinc redirect bug?
by Aliaksei Syrel July 15, 2017

July 15, 2017

Hello, I am trying to download a file from *bintray* with the help of ZnClient. I'm doing the following: ZnClient new systemPolicy; url: ' https://dl.bintray.com/syrel/Moz2D/osx/development/i386/libMoz2D.dylib'; get; yourself which results in Error 403. At the same time wget works as expected: wget https://dl.bintray.com/syrel/Moz2D/osx/development/i386/libMoz2D.dylib Trying to open this url in a browser works too. I tried to find out what may cause the error and it looks like it is something related to redirects because request and response headers look good... Thanks, Alex

3 3

macOS Sierra support
by Sven Van Caekenberghe July 15, 2017

July 15, 2017

Hi, Can someone who really knows/understand please describe where to find the necessary Pharo VM's to run on the newly released macOS Sierra (10.12) ? In particular it seems old VM's just stop working and recent VM's that do work either have issues or cannot run older (3.0, 4.0) images. Thanks, Sven PS: I have not yet upgraded, but one of my colleagues did and he got stuck: even after we found a VM that worked, it could only run 5.0 images, not his production 4.0 images. Needless to say, this is not good. PS2: Another really annoying problem is the following: he saved all his (really important) scripts using Script Manager as a FUEL. Moving between 4.0 and 5.0 FUEL stops working (version incompatibility) - this is really not cool, why would a newer FUEL not be able to read older FUEL. He ended up copying string data by opening the binary FUEL file in a text editor.

12 27

Pharo Launcher
by Stephane Ducasse July 14, 2017

July 14, 2017

Hi where can I find the pharo launcher for the latest version of Pharo? Stef

5 5

Loading GitHub repositories in Pharo 4
by Sven Van Caekenberghe July 13, 2017

July 13, 2017

Hi, Like others I seem to have trouble loading GitHub repositories, in Pharo 4 in my case. Basically, the following fails: Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load. But it also fails as dependency when specified like this: baseline: 'P3' with: [ spec repository: 'github://svenvc/P3' ]; The problem seems to be related to the version info and meta data. (This project was created with Iceberg). MCFileTreeStCypressReader>>#loadVersionInfo self hasMonticelloMetadata ifTrue: [ ^ info := self extractInfoFrom: (self parseMember: 'version') ]. ... The test #hasMonticelloMetadata succeeds, but 'version' is not found in /Users/sven/Tmp/pharo4/github-cache/svenvc/P3/master/svenvc-P3-6897866/BaselineOfP3.package/monticello.meta/version In the above method, there seems to be code to handle missing meta data, but it is not reached. Is this supposed to work ? Is there a way around this ? Thx, Sven

2 3

[pharo-project/pharo-core]
by GitHub July 12, 2017

July 12, 2017

Branch: refs/tags/60508 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] a80076: 60508
by GitHub July 12, 2017

July 12, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a800763b1b40483a518db73a2bf2ec75d8b502dd https://github.com/pharo-project/pharo-core/commit/a800763b1b40483a518db73a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-07-12 (Wed, 12 Jul 2017) Changed paths: A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/README.md A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/definition.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/initialization/initialize.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/stepping and presenter/currentIcon.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/stepping and presenter/step.st A Morphic-Widgets-Tabs.package/TabBuildingIconMorph.class/instance/stepping and presenter/stepTime.st R Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/createAnimationProcess.st M Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/retrieveMorph_.st M Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/softRetrieveMorph.st M Polymorph-Widgets.package/MorphicUIManager.class/instance/debug/lowSpaceWatcherDefaultAction_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60507.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60508.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60507.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60508.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60508 20226 TabMorph should use stepping mechanism for animating background building https://pharo.fogbugz.com/f/cases/20226 20238 Run out of memory the image hangs without out of memory warning https://pharo.fogbugz.com/f/cases/20238 http://files.pharo.org/image/60/60508.zip

1 0

integrating FileDialog into Pharo 7
by Peter Uhnak July 12, 2017

July 12, 2017

Hi, some people expressed interest in integrating File Dialog https://github.com/peteruhnak/file-dialog into Pharo as the default file dialog. Is it something people are interested in, or is the current solution sufficient for them? Peter

4 5

No Metadata in 7.0
by Henrik Nergaard July 11, 2017

July 11, 2017

Hi, I had a look at the Pharo 7.0 today and see metadata for methods (Author and timestamp) has been removed*, what is the reason for this? Having the ability to find methods created around the same time and/or by author is quite useful when fixing bugs in the core libraries. There is also quite a lot of history that is lost as well with this change (I am always impressed when I stumble upon methods over 15-20 years old!). Could this be reverted, please? [*] all methods have a stamp, but it is the same for all with only a timestamp from the bootstrap(?). Best regards, Henrik

6 8

latest 70 and vm
by Stephane Ducasse July 10, 2017

July 10, 2017

Hi I realized that I forgot where I could find the latest 70 and vm. So I could not update the web site Stef

2 6

The new implementation of current working directory
by Rajula Vineet July 10, 2017

July 10, 2017

Hi all, As I have already been posting about my GSoC work and updates on my blog <https://vineetreddy.wordpress.com> and on the mailing list <http://forum.world.st/template/NamlServlet.jtp?macro=search_page&node=12947…> . In this post, I would like to go in depth of my work on 'the working directory' so that I can get valuable feedback and suggestions from everyone. This discussion was started on an github PR <https://github.com/pharo-project/pharo/pull/96> which was conflicting my PR. Firstly, I would like to go through the current implementation of the working directory. With this implementation, when you use the defaultWorkingDirectory method, the directory in which the running image is present in, is returned. This is not a completely good working because when you run the image from a different directory like './pharo ../Pharo.image' the working directory is the one in which your image resides. But that isn`t your actual working directory. Due to this, 1. Pharo cannot be installed as a normal application in a read-only environment. 2. Pharo wrongly reads and writes files relative to the 'working directory'. 3. It also makes scripting difficult. In the FogBugz issue here <https://pharo.fogbugz.com/f/cases/5723/Default-Working-Directory> , there is an example which explains the problem. Let say the Pharo VM and Image are in the directory "~/Pharo", and I wrote a script in "~/Documents/Pharo-scripts" called "perfect-numbers.st" I have 2 possibilities: cd ~/Pharo && pharo Pharo.image st ~/Documents/Pharo-scripts/perfect-numbers.st // works or cd ~/Documents/Pharo-scripts && pharo ~/Pharo/Pharo.image st perfect-numbers.st // doesn't work... It doesn't work because when pharo wants to load the file, it tries to locate it with: FileSystem disk workingDirectory !!! which is NOT the current working directory." I hope you get the problem. So for the new implementation <https://github.com/rajula96reddy/pharo-cli> with the help of Guille I researched about $PWD and getcwd() for a while and wrote a new implementation. This is how it goes 1. I have written new methods in OSPlatorm 'getPwdFromFFI' and 'getPwdFromFFIwithsize:'. These call the getcwd() function using the UFFI 2. And a new method currentWorkingDirectoryPath and currentWorkingDirectoryPathWithBufferSize: in OSPlatform which uses the above method and gets the working directory. 3. To integrate this, I have patched the DiskStore method 'defaultWorkingDirectory' to use the new methods in OSPlatform. I have checked all the sendors of the 'defaultWorkingDirectory' for any issue. And I also wrote some unit tests. So, the new implementation is working fine. With this, now I am able to get the right working directory. The example mentioned above works perfectly. But, there may be a few cases where it can break interoperability between Pharo and other Smalltalk dialects like squeak etc. And the 'pharo-local' directory and its methods should also be patched subsequently. In fact, these problems can be tackled by running image from its own directory itself (which is obvious ;) ) or by using the method imageDirectory in FileLocator class explicitly when necessary. But overall a good thing is this is will ensure the system will behave as in other languages. I have completed this implementation and submitted a PR <https://github.com/pharo-project/pharo/pull/92> to github. But because of some dependency issue, it has not yet been merged. With the help of my mentor, I am working on the problem. Thanks for reading all this. Please give your feedback and comments on this new implementation. Your suggestions help me in learning more about the project and also about the organization. Thanks, Rajula -- View this message in context: http://forum.world.st/The-new-implementation-of-current-working-directory-t… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

7 15