- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [rmod] FOSDEM 2020

by StÃ©phane Ducasse

Thank a lot for all the good energy. Iâm still a bit attacked by the flu and I watched pablo videos doing his/mine talk! S > On 2 Feb 2020, at 21:17, Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> wrote: > > I am not sure how much is going to be of benefit of the community. I hope a lot :). But I'am happy to let you know that we had a really nice stand, with a lot of small things. A lot of power users passing by interested in pharo :). > > If you don't follow Pablo in twitter you should! he shared some nice photos on it. Still i am going to share the photos we took in here and pharo.org <http://pharo.org/> during the week. > > I want to thanks a lot to all the people that shared videos, times and advice. And also ofc to Steph to support us on this and of course to Pablo, Angela and Caro, whom spend the weekend rushing after all this. > > I hope we can repeat this epic quest :) > > Santiago -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Feb. 2, 2020

FOSDEM 2020

by Santiago Bragagnolo

I am not sure how much is going to be of benefit of the community. I hope a lot :). But I'am happy to let you know that we had a really nice stand, with a lot of small things. A lot of power users passing by interested in pharo :). If you don't follow Pablo in twitter you should! he shared some nice photos on it. Still i am going to share the photos we took in here and pharo.org during the week. I want to thanks a lot to all the people that shared videos, times and advice. And also ofc to Steph to support us on this and of course to Pablo, Angela and Caro, whom spend the weekend rushing after all this. I hope we can repeat this epic quest :) Santiago

Feb. 2, 2020

[Pharo 9.0] Build #38: [Doc]: Comments Explaining Issue #4883 Behavior

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

There is a new Pharo build available! The status of the build #38 was: FAILURE. The Pull Request #5624 was integrated: "[Doc]: Comments Explaining Issue #4883 Behavior" Pull request url: https://github.com/pharo-project/pharo/pull/5624 Issue Url: https://github.com/pharo-project/pharo/issues/doc_fs Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 2, 2020

Re: [Pharo-dev] Extending a Class by adding an Instance Variable

by ducasse

So far we do not have instance variable extensions. Now what could be done is to have a dictionary of properties in RubSmalltalkEditor and like that method extensions could use it. We can integrate the extension. > On 2 Feb 2020, at 05:21, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > SmalltalkVimMode adds an instance variable to RubSmalltalkEditor so it can > track whether it is in normal/insert mode, etc. Currently, the inst var is > undeclared when the project is loaded and one has to manually edit the class > def to add it. > > Is there an elegant way to handle this? I can't think of a way that isn't > awkward, dirtying packages, or leaving zombie objects around when editors > close... > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Feb. 2, 2020

Extending a Class by adding an Instance Variable

by Sean P. DeNigris

SmalltalkVimMode adds an instance variable to RubSmalltalkEditor so it can track whether it is in normal/insert mode, etc. Currently, the inst var is undeclared when the project is loaded and one has to manually edit the class def to add it. Is there an elegant way to handle this? I can't think of a way that isn't awkward, dirtying packages, or leaving zombie objects around when editors close... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 2, 2020

Re: [Pharo-dev] New Latest VM - Please Test

by tesonep＠gmail.com

Hi Alistair, thank you for testing it, I will try to generate a version for older glibc as soon it does not produce a problem with newer versions. This is an interesting subject to discuss and see what is better for our community. Nowadays, we are centering in producing executable versions for Debian based distributions (especially Ubuntu). We have to decide which are the platforms we are going to support directly generating binaries distributions and what only through support in source code. Having more and more versions and different building environments requires also to have matching testing scenarios and the effort to maintain them. As usual, we have limited resources and we have to decide where to put the efforts. If there are special interests in a given platform it will be nice to know that (and also if you use it and can, please think about how to collaborate with the efforts done by the consortium). Also, I will like to discuss this subject as choosing Debian / Ubuntu is just a casualty and we need to have a thought decision. Cheers On Sat, Feb 1, 2020 at 8:33 AM Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Pablo, > > This VM looks like it will only run with Ubuntu 19.04 or later: > > $ ./pharo --version > /dev/shm/p8/pharo-vm/lib/pharo/5.0-/pharo: > /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found > (required by /dev/shm/p8/pharo-vm/lib/pharo/5.0-/pharo) > > GLIBC 2.29 is delivered with Ubuntu 19.04. > > Ubuntu 18.04 is the current LTS (GLIBC 2.27), and Ubuntu 16.04 is > still supported (GLIBC 2.23), so I'd expect that the VM is linked > against 2.23, or at least 2.27. > > Cheers, > Alistair > > > > > Am 19.01.2020 um 19:10 schrieb tesonep(a)gmail.com: > > > > > > You are right Norbert, sorry I miss the data. > > > This is available through zeroConf. > > > Doing for example: > > > > > > wget -O - get.pharo.org/64/70+vmLatest | bash > > > wget -O - get.pharo.org/64/80+vmLatest | bash > > > > > > Cheers, > > > Pablo > -- Pablo Tesone. tesonep(a)gmail.com

Feb. 1, 2020

[Pharo 9.0] Build #37: 5485-LOC-should-not-count-line-with-space-or-tab-only

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

There is a new Pharo build available! The status of the build #37 was: FAILURE. The Pull Request #5608 was integrated: "5485-LOC-should-not-count-line-with-space-or-tab-only" Pull request url: https://github.com/pharo-project/pharo/pull/5608 Issue Url: https://github.com/pharo-project/pharo/issues/5485 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 1, 2020

Re: [Pharo-dev] New Latest VM - Please Test

by Alistair Grant

Hi Pablo, This VM looks like it will only run with Ubuntu 19.04 or later: $ ./pharo --version /dev/shm/p8/pharo-vm/lib/pharo/5.0-/pharo: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /dev/shm/p8/pharo-vm/lib/pharo/5.0-/pharo) GLIBC 2.29 is delivered with Ubuntu 19.04. Ubuntu 18.04 is the current LTS (GLIBC 2.27), and Ubuntu 16.04 is still supported (GLIBC 2.23), so I'd expect that the VM is linked against 2.23, or at least 2.27. Cheers, Alistair > > Am 19.01.2020 um 19:10 schrieb tesonep(a)gmail.com: > > > > You are right Norbert, sorry I miss the data. > > This is available through zeroConf. > > Doing for example: > > > > wget -O - get.pharo.org/64/70+vmLatest | bash > > wget -O - get.pharo.org/64/80+vmLatest | bash > > > > Cheers, > > Pablo

Feb. 1, 2020

[Pharo 9.0] Build #36: SUCCESS

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

There is a new Pharo build available! The status of the build #36 was: SUCCESS. Could not extract further issue information from commit message: merge v0.2.1 - add code commands - add system navigation commands - fix default sort on list/table/tree (morphic). - SpNotebookMorph now responds better to different scenarios (and some bug fixes too) Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 31, 2020

[Pharo 9.0] Build #35: 5449-Add-executable-comments-in-SequenceableCollection-enumerating

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

There is a new Pharo build available! The status of the build #35 was: FAILURE. The Pull Request #5612 was integrated: "5449-Add-executable-comments-in-SequenceableCollection-enumerating" Pull request url: https://github.com/pharo-project/pharo/pull/5612 Issue Url: https://github.com/pharo-project/pharo/issues/5449 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 31, 2020