January 2016 - Pharo-users - lists.pharo.org

Pharo-contribution down
by Damien Cassou Jan. 5, 2016

Jan. 5, 2016

The Jenkins for pharo-contribution seems to be down: builds never finish. https://ci.inria.fr/pharo-contribution -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

3 3

Re: [Pharo-users] Using Playgrounds as a notepad
by Andy Burnett Jan. 5, 2016

Jan. 5, 2016

@Dimitris Thanks for the Workspace idea. That is pretty much what I am looking for. However, I am struggling to get it to behave the way I want. When I type into the Workspace, and then inspect ws contents I just get an empty string. Is there a simple way to get the ws to update its contents so that I can access it? @Sven, @Doru. Thanks. The Clipboard approach is very slick. I will use that for the time being. Out of curiosity, is it possible to access any other data on the clipboard. For instance, if I copy a pictured from my desktop, is that accessible via the Clipboard object? I only saw text oriented methods. Thanks Andy

3 2

OSX el capitan - SIP
by recursive68＠gmail.com Jan. 4, 2016

Jan. 4, 2016

Hi, OSX el capitan implements System Integrity Protection: https://en.wikipedia.org/wiki/System_Integrity_Protection One of the effects of this is you can no longer modify DYLD_LIBRARY_PATH for an OSX application. I use a FFI wrapper to load and use an Oracle library in Pharo but this requires modification of the DYLD_LIBRARY_PATH to work. Up until now I could do this by adding a plist config file to /Library/LaunchAgents for the Pharo application which modified DYLD_LIBRARY_PATH. This no longer works because of SIP. Launching Pharo from a terminal having modified DYLD_LIBRARY_PATH via .bash_profile works as required but this is less than ideal. Anyone know of any other way of doing this so I can launch Pharo directly as an OSX application ? Thanks

2 1

Versionner and package dependencies
by Ferlicot D. Cyril Jan. 4, 2016

Jan. 4, 2016

Hi, I wanted to use versionner to manage some existing configurations but in one of these configuration there is some dependencies on packages that have no project. For example in the baseline there is: spec package: 'Glamour-EyeSee-Presentations' with: [ spec requires: #('EyeSee'). spec repository: 'http://smalltalkhub.com/mc/Moose/Glamour/main' ]. But in versionner I can only add a project as dependency. Is there a way to do such a thing or is it a future feature of versionner? -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

2 3

Adding description doc for Catalog browser projects
by Dimitris Chloupis Jan. 4, 2016

Jan. 4, 2016

It has just occured me to that since meta repo is public and anyone can commit to it, is it ok if I add descriptions to projects that have none ? Because I am tried of seeing a project on Catalog Browser with no idea what it does. But i thought to ask permission to edit other people's configurations, though I wont be touching the configurations themselves only add descriptions to projects I find interesting yet they have not description. Is that ok with you ?

3 3

[IMPORTANT] Starting migration to Spur VM
by Esteban Lorenzano Jan. 3, 2016

Jan. 3, 2016

We will start migration to Spur today. To complete it, we will require some time, specially to adapt the CI and check everything is ok. Spur will allow us to do a big step forward in Pharo development, in the concrete you will see it immediately for this: - We have noticed a speed increment of 100% in tiny benchmarks (and according to Eliot, it will be at least 35% in general on the system). - No more GC stops (noticeable when running large systems) - We will be able to scale our systems up to 2G memory consumption without loosing performance. But, this will have some drawbacks in the first times: 1) VM will not be compatible between versions anymore: Pharo 5.0 will have a Pharo Spur VM associated (and they are not compatible). - There WILL NOT be a "non-spur" version of Pharo 5.0. Once completed the transitions, this will be the only one. 2) NativeBoost-FFI implementation has been replaced with a new implementation who relies in ThreadedFFIPlugin and IA32Plugin. While we worked a lot to do this transition as painless as possible and we achieve a good level of backward compatibility (most uses of #nbCall: should work out of the box), there are some problems we cannot solve: - there are some stuff not possible to compatibilise, notably: - Structures now need to inherit from FFIExternalStructure - Arrays now are now shadowed - in general is a bit slower (impossible to compete with ASM) but in general is not perceptible. - THERE WILL BE BUGS AND NON-IMPLEMENTED FEATURES: Current implementation is validated with Athens and even Roassal was working, but of course that does not covers all cases. 2.1) ASMJIT will be removed from system and put in a separated packages. NOTE: There will be a blog post explaining FFI-NB architecture during the week. 3) There are more or less 70 new failing tests, some of them important than we need to fix as soon as possible. Please, please, please, help us with them :) 4) In general we foresee the system will became unstable some weeks, before it gets back to normal. Please be patient. 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to take care about new VM). Some programs will stop work at all (for example, I think Pharo-launcher will need to be adapted).

14 30

Happy new year 2016
by stepharo Jan. 2, 2016

Jan. 2, 2016

Hi Pharoers I want to thank all of you for making Pharo what it is becoming: a Really Cool system and community. I wish you good health and a lot of business or fun in Pharo :). 2016 will see many changes that are planned to name a few - Pharo 5.0 with Spur - Pharo 5.0 with 64 bits - Bootstrap Pharo in production - SDL full integration - Git and Package validation - A full Mooc on Pharo - A couple of cool tutorials And I'm sure many unexpected project and libraries... The consortium should continue to grow so if you are hesitating to join please do. Stef

6 7

Happy new year 2016
by abdelghani ALIDRA Jan. 2, 2016

Jan. 2, 2016

Happy new year everybody. Best wish for 2016. Looks like the Pharo journey is getting more and more exciting :) Abdelghani. Message: 1 Date: Fri, 1 Jan 2016 16:57:27 +0100 From: stepharo <stepharo(a)free.fr> To: Pharo Development List <pharo-dev(a)lists.pharo.org>,Â Â Any question Â Â about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Happy new year 2016 Message-ID: <5686A1E7.10109(a)free.fr> Content-Type: text/plain; charset=utf-8; format=flowed Hi Pharoers I want to thank all of you for making Pharo what it is becoming: a Really Cool system and community. I wish you good health and a lot of business or fun in Pharo :). 2016 will see many changes that are planned to name a few Â Â - Pharo 5.0 with Spur Â Â - Pharo 5.0 with 64 bits Â Â - Bootstrap Pharo in production Â Â - SDL full integration Â Â - Git and Package validation Â Â - A full Mooc on Pharo Â Â - A couple of cool tutorials And I'm sure many unexpected project and libraries... The consortium should continue to grow so if you are hesitating to join please do. Stef

1 0

2016
by Thibault ARLOING Jan. 1, 2016

Jan. 1, 2016

Self assert: (Year new:2016) should: (be Happy) Sorry i couldn't stop myself from doing this Pharo joke. Happy new year 2016 everybody !! -Thibault

3 2