Re: [Pharo-dev] Launcher Opening Tiny Windows

Hi, I think I have a fix for this. It'll only work if the image has a non-zero screen size to start with. But it arranges that if the effective screen size is zero (as it is for headless images) then the VM writes the savedWindowSize (the windows size the image had in the first place) to

Re: [Pharo-dev] Catalog statistics (Who know this projects?)

Unfortunately making something beginner friendly is A LOT of work, its indeed super important but for most people, which is logical, getting the code to work first is the no 1 priority. Indeed as a beginner you dont see even 0.1% of Pharo capabilities. This is why I started a wiki to expose

Re: [Pharo-dev] Catalog statistics (Who know this projects?)

Thanks for the encouragement. I would love to have a crawler that automatically validates distribution where projects available in the distribution are validated (tests green, ...) but we always find something more important to do. Stef On Tue, Aug 22, 2017 at 9:05 PM, ghoetker

Re: [Pharo-dev] Catalog statistics (Who know this projects?)

Many thanks to Esteban for starting this effort and to everyone who has contributed. As a newish member of the community, the lack of such descriptions creates a huge barrier. Not so much that I need to know what "FlyingMongoose" does, but the presence of so many documented projects in the catalog

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

I started the list of fleaky tests at the end of this document https://docs.google.com/document/d/13Zv-za9V54aurmRwHSgObqGecN9PY8rc-t8U_oI_s-w/edit On Tue, Aug 22, 2017 at 7:12 PM, Stephane Ducasse wrote: > Hi denis > > you can have a look at >

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

Hi denis you can have a look at https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/ I started to crawl this list and log the sporadic failing tests. But I do it when integrating. Stef On Tue, Aug 22, 2017 at 6:41 PM, Denis

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

On Tue, Aug 22, 2017 at 5:51 PM, Guillermo Polito wrote: > Hi Marcus, > > Please, do not relaunch the build if there is a test failure. That > simply does not fix the problem, it just adds noise. There are two > problems: > > 1) we have some sporadic test failures

Re: [Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail

Ok I checked and the Session manager is not the toolRegistry. I do not like the design of the latter: a global variable used from anywhere. Now the alternative is that each tool access other tools via a context object but the question is how to update such context when we have a new tool loaded.

Re: [Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail

My impression is that this code is old and we should rewrite it. Now I wonder why the session manager register itself to the tools. The idea of the tool registration was that we can swap them to get different suite of tools. This was never really used and I would replace that by a tool context

Re: [Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail

Le mar. 22 août 2017 à 18:33, Alistair Grant a écrit : > Hi Guille, > > On Tue, Aug 22, 2017 at 05:55:22PM +0200, Guillermo Polito wrote: > > I don't think so... Build number only works from the CI. This means > > that if you build your image in your machine you'll have no

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

Hi. > 1) we have some sporadic test failures (sometimes network, sometimes > some mutex or delay issues). They do not happen all the time and > that's why sometimes there is one or two failing tests. We should > detect these tests and fix them to be more robust I thing I am responsible for

Re: [Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail

Hi Guille, On Tue, Aug 22, 2017 at 05:55:22PM +0200, Guillermo Polito wrote: > I don't think so... Build number only works from the CI. This means > that if you build your image in your machine you'll have no build > number and then this piece of code will not work neither. Thus maybe > we need

Re: [Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail

On Tue, Aug 22, 2017 at 05:55:22PM +0200, Guillermo Polito wrote: > I don't think so... Build number only works from the CI. This means > that if you build your image in your machine you'll have no build > number and then this piece of code will not work neither. Thus maybe > we need to find a

Re: [Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail

I don't think so... Build number only works from the CI. This means that if you build your image in your machine you'll have no build number and then this piece of code will not work neither. Thus maybe we need to find a separate solution for it? On 8/22/17, Alistair Grant

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

Hi Marcus, Please, do not relaunch the build if there is a test failure. That simply does not fix the problem, it just adds noise. There are two problems: 1) we have some sporadic test failures (sometimes network, sometimes some mutex or delay issues). They do not happen all the time and that's

[Pharo-dev] SystemVersion>>highestUpdate causes FFISharedPool class>>initialize to fail

Hi Everyone, I'm attempting to update to the latest Pharo7 image (918efe2, 32 bit), but am getting an error while loading OSsubprocess. The error occurs in FFISharedPool class>>initialize: initialize self flag: #removeIt. "This IF will be eliminated soon...only here temporary"

[Pharo-dev] [ Pharo 70 ] Build 52 to 54

[ Pharo 70 ] Build 52 PR 205 index-inst-var-should-move-from-Slot-to-IndexedSlot https://github.com/pharo-project/pharo/pull/205 https://pharo.fogbugz.com/f/cases/20191 Build 53: failed, redone as 54 [ Pharo 70 ] Build 54 PR 193 Integrate WebBrowser-Core package to be able to

Re: [Pharo-dev] TechTalk Dates for the rest of 2017

> On 22 Aug 2017, at 13:02, Alexandre Bergel wrote: > >>> I'm not sure Pharo tech talk is the good place but would love to see such a >>> presentation. >>> >> Why not? I am sure Alex will have some code in there.. " programming, from >> scratch, a small artificial

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

> On 18 Aug 2017, at 09:56, Marcus Denker wrote: > >> >> What I think would have been good is to list all the updates that where done >> between >> releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they >> were already >> in the image that you got

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

Thanks Alistair. On Thu, Aug 17, 2017 at 5:50 PM, Alistair Grant wrote: > Hi Stef, > > On Thu, Aug 17, 2017 at 05:08:40PM +0200, Stephane Ducasse wrote: >> I do not know but I imagine that I added basenameWithoutExtension because >> I found the name much much clearer. I

Re: [Pharo-dev] Launcher Opening Tiny Windows

Yes I experienced this problem too. I have the impression that during the build the size of the window are messed up. Stef On Sun, Aug 20, 2017 at 2:44 AM, Tim Mackinnon wrote: > It's a known problem for any image that was saved in headless mode (not just > launcher) - we

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

Tx norbert I updated the blog post on pharoweekly. On Mon, Aug 21, 2017 at 11:18 AM, Norbert Hartl wrote: > For the .deb based distributions the adding of the repo is missing. This > would be for > > Ubuntu 16.04 > > echo "deb >

Re: [Pharo-dev] TechTalk Dates for the rest of 2017

>> I'm not sure Pharo tech talk is the good place but would love to see such a >> presentation. >> > Why not? I am sure Alex will have some code in there.. " programming, from > scratch, a small artificial intelligence” > if done with Pharo would be a very nice thing todo for the tech talk.

[Pharo-dev] [ Pharo 70 ] Build 52 PR 195 Make-SUnit-loadable-by-Hermes

[ Pharo 70 ] Build 52 PR 195 Make-SUnit-loadable-by-Hermes https://pharo.fogbugz.com/f/cases/20306/Make-SUnit-loadable-by-Hermes https://github.com/pharo-project/pharo/pull/195

[Pharo-dev] [Wanted] Newsletter topics and "takeovers"

Hi, As you for sure know, we have now a good monthly rhythm with the newsletter. http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77=048680a940 And the number of subscribers is growing!

[Pharo-dev] Spotter references?

Hi I tried Command Shift n to get the class references in Spotter I got #References Point but I got an empty list while if I do Point Cmd shift n I get a list Stef

Re: [Pharo-dev] TechTalk Dates for the rest of 2017

> On 21 Aug 2017, at 19:08, serge.stinckw...@gmail.com wrote: > > I'm not sure Pharo tech talk is the good place but would love to see such a > presentation. > Why not? I am sure Alex will have some code in there.. " programming, from scratch, a small artificial intelligence” if done with