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

[pharo-project/pharo-core]
by GitHub May 16, 2017

May 16, 2017

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

1 0

[pharo-project/pharo-core] 844ba7: 60487
by GitHub May 16, 2017

May 16, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 844ba73bea8ec6051bbe808cfed8551104283104 https://github.com/pharo-project/pharo-core/commit/844ba73bea8ec6051bbe808c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-05-16 (Tue, 16 May 2017) Changed paths: M Glamour-Tests-Core.package/GLMLoggerTest.class/instance/tests/testDefault.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60486.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60487.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60486.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60487.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M TravisIntegrationHelp.package/TravisIntegrationHelp.class/class/pages/step05.st Log Message: ----------- 60487 20056 [Easy to review] Odd formatting in the TravisIntegrationHelp https://pharo.fogbugz.com/f/cases/20056 19809 Failing test: WeakAnnouncerTest>>#testNoDeadWeakSubscriptions https://pharo.fogbugz.com/f/cases/19809 20060 GLMLoggerTest>>testDefault fails if abstract class is abstract in a hierarchy https://pharo.fogbugz.com/f/cases/20060 http://files.pharo.org/image/60/60487.zip

1 0

Does OSSubprocess works on ARM vm?
by Denis Kudriashov May 16, 2017

May 16, 2017

Hi. I decided to ask before I will try it. Best regards, Denis

8 23

PharoLauncher prepared for Pharo 7
by Torsten Bergmann May 15, 2017

May 15, 2017

Pharo Launcher was updated for Pharo 7 already: ----------------------------------------------------------- Name: PharoLauncher-Core-TorstenBergmann.105 Author: TorstenBergmann Time: 15 May 2017, 9:12:21.430226 am UUID: 9b8faeb3-da25-49e9-bdf4-0c2b130ed357 Ancestors: PharoLauncher-Core-CyrilFerlicot.104 Adopt to Pharo 70 already after loading ensure to run PhLTemplateGroupRepository resetGroups. the new directory http://files.pharo.org/image/70/ is still empty until the middle of the week. Have fun T.

2 1

Use of minimal image
by K K Subbu May 15, 2017

May 15, 2017

Hi, I am tempted ;-) by the following message on Pharo's download page: --- The minimal image is a reduced version of Pharo 7.0 (alpha): You have the most basic environment and you can interact with it via command line. WARNING: For hackers only! --- What kind of hacking has been done with this image in the past ? Can this image be used as a swiss-army knife for st (ala busybox in GNU)? The image is small enough to ship as part of regular VM binary and plugins. If pharo (binary) is run without any image, this image can be used as a fallback to run st scripts. At launch time, we know underlying platform OS and architecture, so we could move a lot of platform-specific vm code into such st scripts. Or, we could use it within Makefiles to build plugins outside of src tree. Regards .. Subbu

2 1

Extending the debugger inspector with a new presentation
by tdupriez＠ens-paris-saclay.fr May 15, 2017

May 15, 2017

Hello, I would like to extend the debugger with some context-dependent information. I am playing with metalinks and I would like to show, in the debugger, some information if my metalinks are in the selected method. This means that: - I need to add a new presentation in the debugger next to the "variable" and "evaluator" ones. - I need to filter that presentation to show it depending on which method is selected. I tried to extend ProtoObject with a method like: gtDebuggerExpressionMachinViewIn: composite <gtDebuggerPresentationOrder: 21> composite text title: 'My machin'; display: [ :browser :debugger | debugger asString] However, this did not add a presentation in the debugger. It only show up when selecting an object in the debugger inspector (see screenshot). How can I extend the debugger as I want? Thanks Thomas and Guille

4 5

Esteban's ChangeLog week of 8 May 2017
by estebanlm＠gmail.com May 15, 2017

May 15, 2017

Hello! This is my weekly ChangeLog, from 8 May 2017 to 14 May 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=8/5/2017&to=14/5/2017 ChangeLog ========= 10 May 2017: ------------ * I removed some remaining overrides on [iceberg](http://github.com/pharo-vcs/iceberg). NOW is ready for integration. I will submit an issue :) 9 May 2017: ----------- * Working for release: I spent some time working on the future [Pharo 7.0 download page](http://pharo.org/STAGE.download). It's still not finished (I need to see how to fix the linux distros), but is almost there. * I prepared [zeroconf](http://get.pharo.org) to serve also Pharo 7.0 images (and prepared it to declare a new stable/latest). This is ready but on hold for the momnent of release. * I fixed [iceberg](http://github.com/pharo-vcs/iceberg) remaining problems, merged +dev-0.4+ to +master+ and verify everything works more or less "as expected". With this, I think iceberg is ready to integration (in Pharo6, not enabled by default, but available anyway). cheers! Esteban

1 0

Idea of searcheability of Pharo project on git
by Stephane Ducasse May 14, 2017

May 14, 2017

Hi guys right now many people publish their software on SmalltalkHUB, SS3 and Squeaksource and this is handy to find something. I hope that we will release soon the package repository that christophe was developing but now I'm wondering if we as a community should follow a pattern to help? git freaks do you have suggestions Stef

7 15

New booklet available
by Stephane Ducasse May 14, 2017

May 14, 2017

A new booklet is joining the collection and it is on Voyage the object to document mapper developed by E. Lorenzano. Available in beta http://files.pharo.org/books/ and open to contributors at https://github.com/SquareBracketAssociates/Booklet-Voyage Enjoy Stef

1 0

10/05/17 - Advancing in Pharo Code Quality Support - Myroslava Romaniuk
by Myroslava Romaniuk May 14, 2017

May 14, 2017

A. Work done: - converted a new rule and updated my git repository - read chapters 5 and 6 of the 'Pharo by Example' book - started collaborating with my mentors using a Trello board B. Next steps: - continue reading 'Pharo by Example' - update and convert more rules - watch more tutorials relating to my project (e.g. matchtool tutorial, etc) C. Help required: - I'm seeing other Pharo members also struggling with the same error in iceberg (LGit_GIT_ERROR: error authenticating: failed connecting agent), Ben Coman suggested notifying the pharo-dev community. I know you're all really busy with the upcoming Pharo 6 release but since this bug is kind of pertinent to the new release I thought maybe I should report it on fogbugz? If yes, what priority, whom should I notify? P.S. for me it's the same error when downloading both the stable and the latest versions of the Pharo 6 VM. For now I'm still making do with the 60450 version but would really like to upgrade to a newer one and can't find the one that wouldn't cause any errors. I'm on Win 7 (64 bit). Would appreciate some advice or help with this - also if there's any advice regarding what I should read or look at that's connected to the work I'm doing on my GSoC project, that would be great

3 3