[Pharo-dev] [Wanted] Content for Newsletter

Hi, We are sending a monthly newsletter, see http://newsletter.pharo.org It has a collection of links gathers during the month, but in addition 2-3 larger “mini articles” If someone has ideas for small articles like this —> send me a mail. Marcus

Re: [Pharo-dev] Change Pharo window icon

Hi, The fact that he mentioned an ability to change window's title from inside of the running image suggested me that he actually wants to change an icon at runtime too. Indeed, that is what I would like to do. Cheers, Vincent From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On

[Pharo-dev] OSVM pre-release 201802061430 ready to be tested

Dear all, We were able to fix all build problems today, so here is the OpenSmalltalkVM pre-release 201802061430 [1]. The Pharo VMs for macOS are now correctly signed. More importantly, they come with a fix for "Crashes while typing on macOS Sierra" [2]. Please give the VMs a try if you have some

Re: [Pharo-dev] [OpenSmalltalk/opensmalltalk-vm] Crashes while typing on macOS Sierra (#141)

Hi Tobias, > On Feb 6, 2018, at 4:43 AM, Tobias Pape wrote: > > Closed #141 via ecd41af. > thank you very much for this fix! Lots of people have been hurting from this. > — > You are receiving this because you are subscribed to this thread. > Reply to this email

Re: [Pharo-dev] VMs build process restored

Le 06/02/2018 à 17:58, Esteban Lorenzano a écrit : > (it was broken since december) > > Which means latest vm versions are latest builds from OSVM: > > 64bit > > • http://files.pharo.org/get-files/70/pharo64-mac-latest.zip > •

[Pharo-dev] Which was the way to tag methods so that Spotter think they are examples?

I remember that Spotter was able to detect that some methods were examples and display them differently. Do I remember correctly? I guess some pragma? Anyway, appreciated any hint. Cheers, -- Mariano http://marianopeck.wordpress.com

Re: [Pharo-dev] VMs build process restored

Thank you very much Esteban, Thanks Fabio. On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano wrote: > (it was broken since december) > > Which means latest vm versions are latest builds from OSVM: > > 64bit > > •

[Pharo-dev] VMs build process restored

(it was broken since december) Which means latest vm versions are latest builds from OSVM: 64bit • http://files.pharo.org/get-files/70/pharo64-mac-latest.zip • http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip •

[Pharo-dev] [Pharo 7.0-dev] Build #506: 21124 ffi should work without the sources

There is a new Pharo build available! The status of the build #506 was: FAILURE. The Pull Request #750 was integrated: "21124 ffi should work without the sources" Pull request url: https://github.com/pharo-project/pharo/pull/750 Issue Url: https://pharo.fogbugz.com/f/cases/21124 Build

[Pharo-dev] [Pharo 7.0-dev] Build #505: 21242-improve-includesMethod

There is a new Pharo build available! The status of the build #505 was: SUCCESS. The Pull Request #802 was integrated: "21242-improve-includesMethod" Pull request url: https://github.com/pharo-project/pharo/pull/802 Issue Url: https://pharo.fogbugz.com/f/cases/21242 Build Url:

Re: [Pharo-dev] Reviewing Changes ?

another thing I was thinking about is to just do to do “live” youtube sessions… e.g. if I do a tiny fix, to just stream the whole thing, from start to finish. (but then, I guess the tech talk will be just that) > On 6 Feb 2018, at 13:42, Tim Mackinnon wrote: > > As an idea -

[Pharo-dev] [Pharo 7.0-dev] Build #504: 21243-add-testReifyMethodArgsByNameBefore

There is a new Pharo build available! The status of the build #504 was: SUCCESS. The Pull Request #803 was integrated: "21243-add-testReifyMethodArgsByNameBefore" Pull request url: https://github.com/pharo-project/pharo/pull/803 Issue Url: https://pharo.fogbugz.com/f/cases/21243 Build

[Pharo-dev] How to force a BaselineOf to load ?

Hi, I have a Pharo 4 (#40627) image that already contains P3. Now I want to update P3, without completely rebuilding this image from scratch. It seems as if an expression like Metacello new baseline: 'P3'; repository: 'github://svenvc/P3'; load. executed like $ ../bin/pharo

[Pharo-dev] [Pharo 7.0-dev] Build #503: 21241-remove-comment-Extremely-Slow-from-methodSourceContainingIt

There is a new Pharo build available! The status of the build #503 was: FAILURE. The Pull Request #801 was integrated: "21241-remove-comment-Extremely-Slow-from-methodSourceContainingIt" Pull request url: https://github.com/pharo-project/pharo/pull/801 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #502: 19702-glmSubscriptions-not-needed-in-SubscriptionRegistry

There is a new Pharo build available! The status of the build #502 was: SUCCESS. The Pull Request #777 was integrated: "19702-glmSubscriptions-not-needed-in-SubscriptionRegistry" Pull request url: https://github.com/pharo-project/pharo/pull/777 Issue Url:

Re: [Pharo-dev] Reviewing Changes ?

there will be a techtalk next thursday :) Esteban ps: btw, in general is no “pain”, is people adapting and solving problems. I would like to have also a way to measure when people is happy, but thing is… lists works so people with problems can post them :) > On 6 Feb 2018, at 13:42, Tim

Re: [Pharo-dev] Reviewing Changes ?

As an idea - might someone do a tech talk on this and take us through some scenarios? Every time I think about how to help - I read the pain here and shy away from it (yes the mental barrier is mine, and also alack of time to really get to grips with it) - but I was thinking that it someone

[Pharo-dev] [Pharo 7.0-dev] Build #501: 21240-update-iceberg-to-067

There is a new Pharo build available! The status of the build #501 was: SUCCESS. The Pull Request #800 was integrated: "21240-update-iceberg-to-067" Pull request url: https://github.com/pharo-project/pharo/pull/800 Issue Url: https://pharo.fogbugz.com/f/cases/21240 Build Url:

Re: [Pharo-dev] another file reference question

Hi Stef, Assuming I understand what you're trying to do: This is broken out to hopefully make it clear what the steps are: | src srcPrefix dstPrefix dst | src := 'a/b/c/d.pi' asFileReference. srcPrefix := 'a' asFileReference. dstPrefix := 'result' asFileReference. dst := dstPrefix resolve:

[Pharo-dev] [Pharo 7.0-dev] Build #500: 21236-Sometimes-the-debugger-opens-with-the-context-one-off

There is a new Pharo build available! The status of the build #500 was: SUCCESS. The Pull Request #797 was integrated: "21236-Sometimes-the-debugger-opens-with-the-context-one-off" Pull request url: https://github.com/pharo-project/pharo/pull/797 Issue Url:

Re: [Pharo-dev] Weird ZnClient benchmarking result

Tx this is cool! On Sat, Feb 3, 2018 at 12:17 AM, Sven Van Caekenberghe wrote: > https://pharo.fogbugz.com/f/cases/21232/BenchmarkResult-printFrequencyOn-can-be-confusing > > https://github.com/pharo-project/pharo/pull/794 > >> On 12 Dec 2017, at 07:22, Stephane Ducasse

Re: [Pharo-dev] another file reference question

Thanks alistair What I want to know is a different of paths between two paths so that after I can reproduce the structure under another folder. Example a/b/c/d.pi I should ''copy'' it into result folder and I should get result/b/c/d.pi now I compute the path What is the path of a/b/c/d.pi in

Re: [Pharo-dev] another file reference question

HI I have the following scenario: '/PharoBooks/Booklet-AMiniSchemeInPharo/_result' asFileReference / 'book.pillar' >>> "File @ /PharoBooks/Booklet-AMiniSchemeInPharo/_result/book.pillar" ok it works. I want to update the contents of a target folder only if a file is missing or too old

[Pharo-dev] ESUG 2018 Call for Participation

Call-for-Presentations 26rd International Smalltalk Joint Conference The ESUG board is pleased to announce that the 26th ESUG conference/summer-school will be held in Cagliari, Italy 10-14 September 2018; with Camp Smalltalk 8-9 September 2018. The conference is co-organized by University of

Re: [Pharo-dev] Feedback about "Contribute a Fix to Pharo" (For windows users)

HI nicolai about left and right I totally agree and we should change it. Now we should get a new UI for iceberg too. I started to migrate my project for real using Iceberg and it is working (there are still some glitches). We are concerned about usability. So thanks a lot for your feedback. Stef

[Pharo-dev] [Pharo 7.0-dev] Build #499: 21237-Remove-UndefinedObjectsuspend

There is a new Pharo build available! The status of the build #499 was: SUCCESS. The Pull Request #798 was integrated: "21237-Remove-UndefinedObjectsuspend" Pull request url: https://github.com/pharo-project/pharo/pull/798 Issue Url: https://pharo.fogbugz.com/f/cases/21237 Build Url: