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

Re: [Pharo-dev] Pharo Papers

by denker

> On 16 Feb 2017, at 23:58, Alexandre Bergel <alexandre.bergel(a)me.com> 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 it to HAL. (you would need to add it (or its meta-data) somewhere, so why not use this infrastructure). Marcus

Feb. 17, 2017

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

by ClÃ©ment Bera

On Thu, Feb 16, 2017 at 6:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> 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 intensive code in very large heaps, you won't see much difference as full GC are uncommon. We still need to make the GC incremental to avoid pauses ... > > On 16 Feb 2017, at 17:16, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > > 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 default full GC compactor for further VM > builds yesterday, replacing the existing Pig compactor. However it seems > that the new compactor has not yet passed all the validation infrastructure > (several builds are currently marked as 'error'). > > > > I would expect VM builds in the incoming days to feature the new > compactor. This problem should therefore be solved very soon in the latest > pharo VMs. > > > > In any case, this problem does not require any image-side changes. It > will be in Pharo 6 if the Pharo 6 release VM features the new compactor. > > > > Best, > > > > Clement > > > > On Thu, Feb 16, 2017 at 4:26 PM, denker <marcus.denker(a)inria.fr> wrote: > > > > > On 16 Feb 2017, at 16:22, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > > > > >> On 16 Feb 2017, at 16:16, denker <marcus.denker(a)inria.fr> wrote: > > >> > > >> 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 saved (partly empty) > > >> > > >> Not sure if that is completely right, but it explains why the image > with > > >> lots of objects allocated new can shrink again, while the 47MB never > shrinks, even though the > > >> image for sure is much smaller. > > >> > > >> => what is missing is a âcleanupâ phase that sweeps together all the > half-empty pages. > > >> > > >> What is fun is that we now ship a 47MB image and nobody ever > complains. (or even asks) > > > > > > Yeah, that proves it is not such a big deal, today. > > > But still, we have to fix this discrepancy between 28 and 47. > > > > > > > > > As I tried to explain: the VM is missing a âcondenserâ that cleans up > half allocated pages. > > > > > Is the 'release cleanup' done on this image each time ? > > > > Yes. > > > > Marcus > > > > >

Feb. 17, 2017

debugger evaluator tab for temporary variables

by Ben Coman

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 impressions for Pharo 6, an [Evaluator] tab next to the existing [Variables] tab with access to the whole method scope would be really nice. cheers -ben

Feb. 17, 2017

debugger highlighting objects up the stack

by Ben Coman

Just a brief throw away idea to share before it floats off on its own, it could be useful from the debugger being able to select a variable, and for the object it contains, ask the debugger to highlight up the stack where that object exists in variables and in code. Could be complicated - may need to: * autoscroll the debugger's inspector pane * annotate previously sent messages with the identity hash of the object returned cheers -ben

Feb. 17, 2017

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

by Stephan Eggermont

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

Feb. 17, 2017

Re: [Pharo-dev] Pharo Papers

by Alexandre Bergel

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 <marcus.denker(a)inria.fr> wrote: > > 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: > https://www.sofa-framework.org/applications/publications/ > > and here âhow to add a paperâ: > > https://www.sofa-framework.org/applications/publications/add-a-publication-… > > I will definitely set this up for Pharo later this year (read: as soon as possible) > > Marcus > > >> On 16 Feb 2017, at 14:30, Ben Coman <btc(a)openinworld.com> wrote: >> >> 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" >> "references" filetype:pdf >> http://tiny.cc/pharo-papers >> >> Probably a lot of overlap between them. >> cheers -ben >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 16, 2017

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

by Martin Dias

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 <tinchodias(a)gmail.com> wrote: > Reported as https://pharo.fogbugz.com/f/cases/19715/FastTableModel- > Can-t-enable-multiple-selection > > I checked that multiple selection works with ListModel (the superclass of > FastTableModel). > > Martin > > > On Wed, Feb 15, 2017 at 1:56 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Hi, >> >> I can't reproduce in #60394. In fact I *want* multiple selection and only >> get single selection: >> >> FastTableModel new beMultipleSelection; items: (1 to: 10) asArray; >> openWithSpec. >> >> Martin >> >> >> >> On Mon, Feb 13, 2017 at 9:03 PM, Stephan Eggermont <stephan(a)stack.nl> >> wrote: >> >>> On 13/02/17 12:52, Andrei Chis wrote: >>> >>>> Is this in the Glamour model or in the Spec one? >>>> >>> >>> In the Spec one, so I might be a bit late in noticing. >>> >>> Stephan >>> >>> >>> >>> >> >

Feb. 16, 2017

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

by Sven Van Caekenberghe

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 <bera.clement(a)gmail.com> wrote: > > 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 default full GC compactor for further VM builds yesterday, replacing the existing Pig compactor. However it seems that the new compactor has not yet passed all the validation infrastructure (several builds are currently marked as 'error'). > > I would expect VM builds in the incoming days to feature the new compactor. This problem should therefore be solved very soon in the latest pharo VMs. > > In any case, this problem does not require any image-side changes. It will be in Pharo 6 if the Pharo 6 release VM features the new compactor. > > Best, > > Clement > > On Thu, Feb 16, 2017 at 4:26 PM, denker <marcus.denker(a)inria.fr> wrote: > > > On 16 Feb 2017, at 16:22, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > >> On 16 Feb 2017, at 16:16, denker <marcus.denker(a)inria.fr> wrote: > >> > >> 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 saved (partly empty) > >> > >> Not sure if that is completely right, but it explains why the image with > >> lots of objects allocated new can shrink again, while the 47MB never shrinks, even though the > >> image for sure is much smaller. > >> > >> => what is missing is a âcleanupâ phase that sweeps together all the half-empty pages. > >> > >> What is fun is that we now ship a 47MB image and nobody ever complains. (or even asks) > > > > Yeah, that proves it is not such a big deal, today. > > But still, we have to fix this discrepancy between 28 and 47. > > > > > As I tried to explain: the VM is missing a âcondenserâ that cleans up half allocated pages. > > > Is the 'release cleanup' done on this image each time ? > > Yes. > > Marcus >

Feb. 16, 2017

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

by Ben Coman

On Thu, Feb 16, 2017 at 11:16 PM, denker <marcus.denker(a)inria.fr> 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

Feb. 16, 2017

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

by ClÃ©ment Bera

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 default full GC compactor for further VM builds *yesterday,* replacing the existing Pig compactor. However it seems that the new compactor has not yet passed all the validation infrastructure (several builds are currently marked as 'error'). I would expect VM builds in the incoming days to feature the new compactor. This problem should therefore be solved very soon in the latest pharo VMs. In any case, this problem does not require any image-side changes. It will be in Pharo 6 if the Pharo 6 release VM features the new compactor. Best, Clement On Thu, Feb 16, 2017 at 4:26 PM, denker <marcus.denker(a)inria.fr> wrote: > > > On 16 Feb 2017, at 16:22, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > >> On 16 Feb 2017, at 16:16, denker <marcus.denker(a)inria.fr> wrote: > >> > >> 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 > saved (partly empty) > >> > >> Not sure if that is completely right, but it explains why the image with > >> lots of objects allocated new can shrink again, while the 47MB never > shrinks, even though the > >> image for sure is much smaller. > >> > >> => what is missing is a âcleanupâ phase that sweeps together all the > half-empty pages. > >> > >> What is fun is that we now ship a 47MB image and nobody ever complains. > (or even asks) > > > > Yeah, that proves it is not such a big deal, today. > > But still, we have to fix this discrepancy between 28 and 47. > > > > > As I tried to explain: the VM is missing a âcondenserâ that cleans up half > allocated pages. > > > Is the 'release cleanup' done on this image each time ? > > Yes. > > Marcus >

Feb. 16, 2017