Re: [Pharo-dev] FastTableModel switched from default single-select to multi

On 16/02/17 20:37, Martin Dias wrote: I set the case to "Milestone Later"... I reproduced the bug in Pharo 5 It is somewhat more complex. I have the problem with doubleClick, but not if only adding a doubleClick handler. In SpecGenerator I set some more properties. Stephan

[Pharo-dev] debugger evaluator tab for temporary variables

A minor irritation with the debugger is that the [Evaluator] tab is only for the object of the selected instance variable. IIUC, to write a snippet of code using a local variable you must edit the code of the method, which dirties it. I've lived with this, but thinking of newcomer first

Re: [Pharo-dev] Pharo Papers

But you will not get the papers not stored on HAL. And I suspect there are more papers about Pharo outside the HAL world. Alexandre > On Feb 16, 2017, at 11:13 AM, denker wrote: > > One idea on my TODO that I got from colleagues here working on another >

Re: [Pharo-dev] Pharo Papers

Yes definitively will be nice to have a list of research about Pharo or based on Pharo. Thank you Marcus. On Thu, Feb 16, 2017 at 3:13 PM, denker wrote: > One idea on my TODO that I got from colleagues here working on another > OpenSource/Research > system (Sofa3D): to

Re: [Pharo-dev] Pharo Papers

> On 16 Feb 2017, at 23:58, Alexandre Bergel wrote: > > But you will not get the papers not stored on HAL. And I suspect there are > more papers about Pharo outside the HAL world. > Hal is a public archive. So the idea would be that if you want you paper listed, add

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

On Thu, Feb 16, 2017 at 6:10 PM, Sven Van Caekenberghe wrote: > Thanks, Clément, for this update, really exciting news. Is the new GC > faster too ? > The full GC is indeed much faster as the previous compaction algorithm was very slow. But unless you were executing memory

Re: [Pharo-dev] 2 seconds default time limit for tests

I vote for not introducing during code-freeze. We can discuss it for Pharo 7, I'm not against actually. But I have some concerns: - How does it work when we are debugging? I mean, imagine I'm running a test, a debugger is open, and I start working on it. How do these timeout currently work in

Re: [Pharo-dev] 2 seconds default time limit for tests

But we could integrate the patch (his work marking slow tests) and the code, and then disable the enforcing mechanism. That will allow us to re-able it quickly later on. > On 16 Feb 2017, at 14:23, Esteban Lorenzano wrote: > > >> On 16 Feb 2017, at 13:49, Guillermo

Re: [Pharo-dev] 2 seconds default time limit for tests

2017-02-16 14:35 GMT+01:00 Sven Van Caekenberghe : > But did you not mark more tests with custom timeouts ? Yes, couple test cases. And actually all slow tests (from previous fixes too) are marked with 10 seconds. Current default 1 minute is to not affect possible external

Re: [Pharo-dev] 2 seconds default time limit for tests

On Thu, Feb 16, 2017 at 9:32 PM, Denis Kudriashov wrote: > > 2017-02-16 14:26 GMT+01:00 Sven Van Caekenberghe : >> >> But we could integrate the patch (his work marking slow tests) and the >> code, and then disable the enforcing mechanism. That will allow us to

Re: [Pharo-dev] 2 seconds default time limit for tests

2017-02-16 14:59 GMT+01:00 Ben Coman : > But this could conceivably cause more erroneous failures by the CI > monkey, which slows down progress up to the Release. > I would not wrote this mail without Monkey :). With "2 seconds" Monkey was happy. > > +1 for doing it

[Pharo-dev] 2 seconds default time limit for tests

Hi. In Pharo 6 we introduced time limit for tests. Currently it is set to 1 minute by default. And concrete test cases or single tests can redefine it with suitable value. There is also setting to change default limit globally which should help to not adopt external projects immediately if

[Pharo-dev] blog post about Calypso navigation model

Hello. I wrote blog post about Calypso navigation model http://dionisiydk.blogspot.fr/2017/02/calypso-navigation-model.html. Questions and feedback are welcome. Best regards, Denis

[Pharo-dev] Pharo Papers

And now for your regularly scheduled random trivia show... I was mildly curious about how many papers touched on Pharo. 1,110 on google scholar for... "pharo" "programming" http://tiny.cc/pharo-scholar 1,630 on normal google for... "pharo" "programming" "abstract" "introduction" "conclusion"

Re: [Pharo-dev] Pharo Papers

One idea on my TODO that I got from colleagues here working on another OpenSource/Research system (Sofa3D): to add all publication to the website automatically using HAL (the national french paper database). It looks like this on the website:

Re: [Pharo-dev] 2 seconds default time limit for tests

2017-02-16 14:26 GMT+01:00 Sven Van Caekenberghe : > But we could integrate the patch (his work marking slow tests) and the > code, and then disable the enforcing mechanism. That will allow us to > re-able it quickly later on. It is already in image. My patch only enable small

Re: [Pharo-dev] 2 seconds default time limit for tests

2017-02-16 13:49 GMT+01:00 Guillermo Polito : > I vote for not introducing during code-freeze. > I understand it but these behaviour was introduced in Pharo 6. And It is already used quite long time. So it could be considered as small improvements to already integrated

Re: [Pharo-dev] 2 seconds default time limit for tests

2017-02-16 14:46 GMT+01:00 Guillermo Polito : > >> It solved very easily. "Watchdog process" just checks that test process >> isSuspended or not. If it is not suspended timeout is signalled. Test >> process is suspended only when debugged. >> > > Ok. Is something like

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Association: Join or Renew now!

> On 16 Feb 2017, at 14:06, denker wrote: > > >> On 16 Feb 2017, at 10:43, denker wrote: >> >> Hi, >> >> Yes, we are planning to extend the profiles to have space for >> -> website > > I have added a field for the website. > I have

Re: [Pharo-dev] 2 seconds default time limit for tests

On Thu, Feb 16, 2017 at 2:31 PM, Denis Kudriashov wrote: > > 2017-02-16 13:49 GMT+01:00 Guillermo Polito : > >> I vote for not introducing during code-freeze. >> > > I understand it but these behaviour was introduced in Pharo 6. And It is >

[Pharo-dev] [VM] Windows VM SurfacePlugin.dll LoadLibrary failure

Hi, recently (couple of days ago) sometimes when I start Pharo there's a box at the bottom "Debug console" with the following info ~~ # Debug console # To close: F2 -> 'debug options' -> 'show output console' # To disable: F2 -> 'debug options' -> 'show

[Pharo-dev] [pharo-project/pharo-core] 03cd61: 60396

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 03cd61e0aae1f586d4890c320a7bd01e00fc78dc https://github.com/pharo-project/pharo-core/commit/03cd61e0aae1f586d4890c320a7bd01e00fc78dc Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

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

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Association: Join or Renew now!

> On 16 Feb 2017, at 10:43, denker wrote: > > Hi, > > Yes, we are planning to extend the profiles to have space for > -> website I have added a field for the website. Marcus

Re: [Pharo-dev] 2 seconds default time limit for tests

> On 16 Feb 2017, at 13:49, Guillermo Polito wrote: > > I vote for not introducing during code-freeze. +1: not in code freeze. > > We can discuss it for Pharo 7, I'm not against actually. But I have some > concerns: > > - How does it work when we are debugging? >

Re: [Pharo-dev] 2 seconds default time limit for tests

> On 16 Feb 2017, at 14:32, Denis Kudriashov wrote: > > > 2017-02-16 14:26 GMT+01:00 Sven Van Caekenberghe : > But we could integrate the patch (his work marking slow tests) and the code, > and then disable the enforcing mechanism. That will allow us to

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Association: Join or Renew now!

Hi, Yes, we are planning to extend the profiles to have space for -> website -> short bio -> list of interests -> interested in listed as public pharo consultant? *and* we will then automatically generate http://consultants.pharo.org

[Pharo-dev] CI down this morning for maintance

Hi, The ci (pharo and pharo-contrib) has some maintenance this morning and can be down for some hours. Marcus

Re: [Pharo-dev] Code Completion in Pharo

Hi Lukas, This is cool and an interesting topic. Something that I would like is to see wether we can merge the auto-completion with the AST-based suggestion mechanism (right click on a piece of code -> suggestions), that provides suggestions for refactorings and code browsing. I mean, you can see

Re: [Pharo-dev] CI down this morning for maintance

Everything is online again! > On 16 Feb 2017, at 10:22, Marcus Denker wrote: > > Hi, > > The ci (pharo and pharo-contrib) has some maintenance this morning and can be > down for some > hours. > > Marcus

[Pharo-dev] [Pharo6][Issue Tracker] Please check older issues

Hi, The issue tracker is at 632 open issues. https://pharo.fogbugz.com/f/filters/57/All-newest-first Please check every issue that you either opened or were part of the discussion. - is this issue still relevant? - if tagged for the Pharo 6 milestone: is it really a

Re: [Pharo-dev] [VM] Windows VM SurfacePlugin.dll LoadLibrary failure

On 16/02/2017 11:06, Peter Uhnak wrote: > Hi, > > recently (couple of days ago) sometimes when I start Pharo there's a box at > the bottom "Debug console" with the following info > > ~~ > # Debug console > # To close: F2 -> 'debug options' -> 'show output

Re: [Pharo-dev] [ANN] Pharo Association: Join or Renew now!

We would be very interesting in ideas/improvements wrt. to the Association/Consortium. if you have any ideas —> send me a mail. Marcus > On 14 Feb 2017, at 15:17, Marcus Denker wrote: > > Hi, > > The new Pharo Association website is up and running for some

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Association: Join or Renew now!

> On 16 Feb 2017, at 16:10, Peter Uhnak wrote: > > On Tue, Feb 14, 2017 at 03:17:42PM +0100, Marcus Denker wrote: >> Hi, >> >> The new Pharo Association website is up and running for some month. >> >> If you are a member, it will bug you once a year to renew. > > Maybe

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

Yes, this has to be solved on the VM level and will be read when it is ready. The release should bot be hold up due to this, therefore I removed the milestone. > On 16 Feb 2017, at 15:50, Ben Coman wrote: > > @Marcus, I was reviewing this issue before I noticed you

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

What Ben says that he thinks it might already be solved. Maybe not on all platforms. > On 16 Feb 2017, at 15:59, denker wrote: > > Yes, this has to be solved on the VM level and will be read when it is ready. > The release should bot be hold up due to this, therefore I

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Association: Join or Renew now!

On Tue, Feb 14, 2017 at 03:17:42PM +0100, Marcus Denker wrote: > Hi, > > The new Pharo Association website is up and running for some month. > > If you are a member, it will bug you once a year to renew. Maybe there should be information that the membership (and fee) is automatic due to

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

No, Our image is not 47 MB… more like 28. My understanding is: -> Cog works with “pages” (is that the term?) of memory. -> if a page is empty, it gets cleaned up and does not cost space when saving. -> if there is some object still allocated, the whole page will be

[Pharo-dev] 17240 Spur, when saving an image, it never shrinks

@Marcus, I was reviewing this issue before I noticed you flipped the milestone from Pharo 6.0 to Later. But is it solved already? In a fresh image 47.7MB in size I did the following a bunch of times to grow the image file to 400MB o ifNil: [o := OrderedCollection new]. 100 timesRepeat: [

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

Hi all, A temporary solution had been integrated in the VM a year ago, but only part of the problem was solved. This issue has been entirely solved in the VM through the implementation of a new compactor for the full GC. The new compactor (called the planning compactor) has been marked as the

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

> On 16 Feb 2017, at 16:22, Sven Van Caekenberghe wrote: > > >> On 16 Feb 2017, at 16:16, denker wrote: >> >> No, >> >> Our image is not 47 MB… more like 28. >> >> My understanding is: >> -> Cog works with “pages” (is that the term?) of memory. >>

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

Thanks, Clément, for this update, really exciting news. Is the new GC faster too ? > On 16 Feb 2017, at 17:16, Clément Bera wrote: > > Hi all, > > A temporary solution had been integrated in the VM a year ago, but only part > of the problem was solved. > > This

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

On Thu, Feb 16, 2017 at 11:16 PM, denker wrote: > > What is fun is that we now ship a 47MB image and nobody ever complains. (or > even asks) > yes thats strange. 640KB ought to have been enough for anyone! cheers -ben

Re: [Pharo-dev] FastTableModel switched from default single-select to multi

I set the case to "Milestone Later"... I reproduced the bug in Pharo 5 On Wed, Feb 15, 2017 at 2:01 PM, Martin Dias wrote: > Reported as https://pharo.fogbugz.com/f/cases/19715/FastTableModel- > Can-t-enable-multiple-selection > > I checked that multiple selection works