- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ProcessBrowser does not auto-update itself by default? Should it?

by Sven Van Caekenberghe

I believe the reason not to make auto updating the default, is because #updateProcessList is a bit heavy (it calls a GC, does an #allSubInstances, and it is a thread itself). Maybe that is no longer the case ? But adding a button to make auto updating easier to start would probably help. Maybe a button bar for more common actions (like terminate) ? > On 4 Feb 2019, at 11:47, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> wrote: > > Hello, > > The Process Browser does not auto-updates itself by default to show new processes and hide processes that stopped. > > Is there a specific reason for that? The first time I opened it I kind of expected it would auto-update itself, and I think this may be a more "intuitive" behaviour that no auto-updates by default. What do you think? > > Getting auto-updates is "easy" (there is no button in the UI (something to improve?), but one can call the "toggleAutoUpdate" method to get this behaviour). My question is about it not being default. > > Thomas > >

Feb. 4, 2019

ProcessBrowser does not auto-update itself by default? Should it?

by Thomas Dupriez

Hello, The Process Browser does not auto-updates itself by default to show new processes and hide processes that stopped. Is there a specific reason for that? The first time I opened it I kind of expected it would auto-update itself, and I think this may be a more "intuitive" behaviour that no auto-updates by default. What do you think? Getting auto-updates is "easy" (there is no button in the UI (something to improve?), but one can call the "toggleAutoUpdate" method to get this behaviour). My question is about it not being default. Thomas

Feb. 4, 2019

[Pharo 8.0] Build #51: OpalCompiler-Core spelling in class comment

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #51 was: SUCCESS. The Pull Request #2436 was integrated: "OpalCompiler-Core spelling in class comment" Pull request url: https://github.com/pharo-project/pharo/pull/2436 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 4, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Guillermo Polito

On Mon, Feb 4, 2019 at 9:28 AM Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Stef, > On Mon, 4 Feb 2019 at 09:20, ducasse <stepharo(a)netcourrier.com> wrote: > > > > Hi alistair > > > > >> HI alistair > > >> > > >> you should use the latest pillar. Was dev-7 and now it is 70 > > >> because this is around six months that we removed the dependency to > grease. > > > > > > I can see the dev-7 branch (which is what I'm using in Pharo 8). > > > > > > And this is the one that broke? Strange. > > Now we did not try Pillar in Pharo 80. > > Could you try in Pharo70? > > No, the smalltalkhub version was "broken", but that's to be expected > since it was out of date. > > The dev-7 branch loads fine in Pharo 8. > > > > But what do you mean by "now it is 70â? > > > > I thought that guillermo changed the dev-7 branch. > Nope, I think that name is good, and then we manage releases using tags. We have the following branches: [image: image.png] > > Ok I checked and this is a tag. 7.4.1 > > And that answers my question. > > Thanks, > Alistair > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Feb. 4, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Alistair Grant

Hi Stef, On Mon, 4 Feb 2019 at 09:20, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi alistair > > >> HI alistair > >> > >> you should use the latest pillar. Was dev-7 and now it is 70 > >> because this is around six months that we removed the dependency to grease. > > > > I can see the dev-7 branch (which is what I'm using in Pharo 8). > > > And this is the one that broke? Strange. > Now we did not try Pillar in Pharo 80. > Could you try in Pharo70? No, the smalltalkhub version was "broken", but that's to be expected since it was out of date. The dev-7 branch loads fine in Pharo 8. > > But what do you mean by "now it is 70â? > > I thought that guillermo changed the dev-7 branch. > Ok I checked and this is a tag. 7.4.1 And that answers my question. Thanks, Alistair

Feb. 4, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by ducasse

Hi alistair >> HI alistair >> >> you should use the latest pillar. Was dev-7 and now it is 70 >> because this is around six months that we removed the dependency to grease. > > I can see the dev-7 branch (which is what I'm using in Pharo 8). And this is the one that broke? Strange. Now we did not try Pillar in Pharo 80. Could you try in Pharo70? > But what do you mean by "now it is 70â? I thought that guillermo changed the dev-7 branch. Ok I checked and this is a tag. 7.4.1 > > Thanks, > Alistair >

Feb. 4, 2019

Re: [Pharo-dev] Esteban's ChangeLog week of 28 January 2019

by ducasse

Great ChangeLog!!!! Thanks esteban! > On 4 Feb 2019, at 08:00, estebanlm(a)gmail.com wrote: > > Hello! > > This is my weekly ChangeLog, from 28 January 2019 to 3 February 2019. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=28/1/2019&to=3/2/2019 > > ChangeLog > ========= > > 30 January 2019: > ---------------- > > * Still more work for the [PR](https://github.com/pharo-spec/Spec/pull/208) I submited yesterday. > > It is now ready to merge! > > > 29 January 2019: > ---------------- > > * I made a [PR](https://github.com/pharo-spec/Spec/pull/208) that adds two new elements to Spec 2: > > 1) SpecPanedLayout is a new layout that complements SpecBoxLayout: > > A paned layout is like a Box Layout (it places childen in vertical or horizontal fashion), but it will add a splitter in between, that user can drag to resize the panel. > In exchange, a paned layout can have just two children. > > 2) NotebookPresenter is a new implementation of a tab manager. Needed because old one was not lazy, bad layouted > and too attached to Morphic (while we attempt to be more backend agnostic). > > All of this is still WIP (there are missing functionality still), but what is there is working fine :) > > * I merged this [PR](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/362) from Pavel to > improve keyboard handling on Windows VMs. > > * Now that Pharo 7.0 is out, I started work on the Pharo 8.0 roadmap (that I need to > send to the list, btw). > > Since some weeks I've been working on Spec2 (because we will need it sooner than > expected and I wanted to make some progress on its general design and needs). In Spec2, > some things will be enhanced, some others replaced and some other more added from > scratch. > > I wanted to know mor more or less were we stand to do the job. > > Some work I've made (along with Cyril): > > 1) Layouts will be revamped. Right now there is just one layout which is overpowerful but hard > to use and too attached to morphic (and our goal is to be able to replace the Morphic backend > with a Bloc backend). We decided to go for a different approach: instead one layout that does > all, having different layouts to fulfil different needs: > - +SpecBoxLayout+ (rigid panes) > - +SpecPanedLayout+ (non rigid panes) > - +SpecGridLayout+ (form kind layout) > - +SpecFlowLayout+ (flowing components) > - +SpecXYLayout+ (rigid coordinates) > - And of course there will be need of a kasowary based layout. > - ... ? > > I already implemented +SpecBoxLayout+, +SpecPanesLayout+ and a preliminary version od +SpecGridLayout+ :). > > 2) Interpreter will be removed. Just the old layout makes it necessary today, and it adds a > complexity we do not need. > > 3) We will add a +TablePresenter+ (a good one) and a +TreeTablePresenter+ (again, a good one). > Old versions that try to fullfil same function will be deprecated. There is already a functional > preliminary version of them :) > > 4) We will add components for Numbers, Dates, etc. (+NumberInputFieldPresenter+ is already implemented) > > 5) We will revisit all other components. > > As a roadmap, is pretty ambicious but is looking good so far :) > > > cheers! > Esteban >

Feb. 4, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by Alistair Grant

Hi Stef, On Sun, 3 Feb 2019 at 21:56, ducasse <stepharo(a)netcourrier.com> wrote: > > HI alistair > > you should use the latest pillar. Was dev-7 and now it is 70 > because this is around six months that we removed the dependency to grease. I can see the dev-7 branch (which is what I'm using in Pharo 8). But what do you mean by "now it is 70"? Thanks, Alistair

Feb. 4, 2019

Esteban's ChangeLog week of 28 January 2019

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 28 January 2019 to 3 February 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=28/1/2019&to=3/2/2019 ChangeLog ========= 30 January 2019: ---------------- * Still more work for the [PR](https://github.com/pharo-spec/Spec/pull/208) I submited yesterday. It is now ready to merge! 29 January 2019: ---------------- * I made a [PR](https://github.com/pharo-spec/Spec/pull/208) that adds two new elements to Spec 2: 1) SpecPanedLayout is a new layout that complements SpecBoxLayout: A paned layout is like a Box Layout (it places childen in vertical or horizontal fashion), but it will add a splitter in between, that user can drag to resize the panel. In exchange, a paned layout can have just two children. 2) NotebookPresenter is a new implementation of a tab manager. Needed because old one was not lazy, bad layouted and too attached to Morphic (while we attempt to be more backend agnostic). All of this is still WIP (there are missing functionality still), but what is there is working fine :) * I merged this [PR](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/362) from Pavel to improve keyboard handling on Windows VMs. * Now that Pharo 7.0 is out, I started work on the Pharo 8.0 roadmap (that I need to send to the list, btw). Since some weeks I've been working on Spec2 (because we will need it sooner than expected and I wanted to make some progress on its general design and needs). In Spec2, some things will be enhanced, some others replaced and some other more added from scratch. I wanted to know mor more or less were we stand to do the job. Some work I've made (along with Cyril): 1) Layouts will be revamped. Right now there is just one layout which is overpowerful but hard to use and too attached to morphic (and our goal is to be able to replace the Morphic backend with a Bloc backend). We decided to go for a different approach: instead one layout that does all, having different layouts to fulfil different needs: - +SpecBoxLayout+ (rigid panes) - +SpecPanedLayout+ (non rigid panes) - +SpecGridLayout+ (form kind layout) - +SpecFlowLayout+ (flowing components) - +SpecXYLayout+ (rigid coordinates) - And of course there will be need of a kasowary based layout. - ... ? I already implemented +SpecBoxLayout+, +SpecPanesLayout+ and a preliminary version od +SpecGridLayout+ :). 2) Interpreter will be removed. Just the old layout makes it necessary today, and it adds a complexity we do not need. 3) We will add a +TablePresenter+ (a good one) and a +TreeTablePresenter+ (again, a good one). Old versions that try to fullfil same function will be deprecated. There is already a functional preliminary version of them :) 4) We will add components for Numbers, Dates, etc. (+NumberInputFieldPresenter+ is already implemented) 5) We will revisit all other components. As a roadmap, is pretty ambicious but is looking good so far :) cheers! Esteban

Feb. 4, 2019

Re: [Pharo-dev] ConfigurationOfGrease for Pharo8

by ducasse

HI alistair you should use the latest pillar. Was dev-7 and now it is 70 because this is around six months that we removed the dependency to grease. Now if you need help to migrate a book/doc from pillar 6 to 7 let me know I can help. I migrated many of the books to validate Pillar 70. It is three weeks that we do not find the time to officially release it but it is super stable. Stef > On 3 Feb 2019, at 21:48, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Cyril & Sven, > > I was loading an old version of Pillar, so that solves the Grease version info. > > Thanks again, > Alistair > > > On Sun, 3 Feb 2019 at 19:25, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Cyril & Sven, >> >> Thanks for the pointer. I'll have to figure out why it is being >> loaded from smalltalkhub - maybe Pillar? Anyway, I'll have a look. >> >> Thanks again, >> Alistair >> >> On Sun, 3 Feb 2019 at 19:22, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> >>> >>> >>> On Sun 3 Feb 2019 at 19:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>> >>>> Hi All, >>>> >>>> It looks like Grease is still hosted on smalltalkhub - if not, please >>>> let me know where. >>> >>> >>> Hi, >>> >>> Here: >>> >>> https://github.com/SeasideSt/Grease >>> >>> :) >>> >>>> >>>> Are there any objections to me updating >>>> ConfigurationOfGrease>>release1: to load on Pharo8? >>>> >>>> The updated method is (apologies for loss of formatting): >>>> >>>> release1: aSpec >>>> <symbolicVersion:#'release1'> >>>> aSpec for: #'pharo3.x' version: #'release1.3'. >>>> aSpec for: #'pharo4.x' version: #'release1.3'. >>>> aSpec for: #'pharo5.x' version: #'release1.3'. >>>> aSpec for: #'pharo6.x' version: #'release1.3'. >>>> aSpec for: #'pharo7.x' version: #'release1.3'. >>>> aSpec for: #'pharo8.x' version: #'release1.3'. >>>> aSpec for: #'squeak5.x' version: #'release1.3'. >>>> aSpec for: #'gs3.x' version: #'release1.3'. >>>> aSpec for: #'pharo1.x' version: #'release1.2'. >>>> aSpec for: #'pharo2.x' version: #'release1.2'. >>>> aSpec for: #'squeak4.x' version: #'release1.2'. >>>> aSpec for: #'gs2.x' version: #'release1.2' >>>> >>>> The change is the addition of the #'pharo8.x' line. >>>> >>>> Thanks, >>>> Alistair >>>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >

Feb. 3, 2019