- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #367: 2611-Activating-slots-break-MCSnapshotBrowserTesttestClassSideClassSelected

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

There is a new Pharo build available! The status of the build #367 was: SUCCESS. The Pull Request #3588 was integrated: "2611-Activating-slots-break-MCSnapshotBrowserTesttestClassSideClassSelected" Pull request url: https://github.com/pharo-project/pharo/pull/3588 Issue Url: https://github.com/pharo-project/pharo/issues/2611 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 21, 2019

[Pharo 8.0] Build #366: 3444-Mis-spelled protocol name 'acccessing'

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

There is a new Pharo build available! The status of the build #366 was: SUCCESS. The Pull Request #3593 was integrated: "3444-Mis-spelled protocol name 'acccessing'" Pull request url: https://github.com/pharo-project/pharo/pull/3593 Issue Url: https://github.com/pharo-project/pharo/issues/issue Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 21, 2019

Re: [Pharo-users] Information on Spec development

by Alexandre Bergel

Thanks for sharing this. You guys are doing an amazing job. I do not mind having a couple of warning times to time. Cheers, Alexandre > On Jun 20, 2019, at 11:29 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hello everyone! > > This is an important update about the development of Spec. > > As you might have heard, we are working on Spec to release a new > version in Pharo 8. One goal is to unify all Pharo interfaces behind > one GUI framework and a second goal is to allow multiple back-ends > (Morphic but also GTK, Bloc, ...). To reach those goals we have been > updating the current version of Spec. We see now, however, that > updating Spec directly creates troubles with migration. For example, > we currently have a lot of deprecation warnings in Iceberg, because we > can't update it without breaking Pharo 7 compatibility. > > After some discussions between the engineers working on Spec, here is > our plan to improve the situation: We will copy all classes of Spec > and rename them with the "Sp" prefix. (We will also ensure that every > class of Spec started with the same prefix for consistency). For > extensions methods, we will rename them to have a version different > from Spec 1 (The spec from Pharo 7). Once done we will integrate this > new version in Pharo 8. From there we will wait some weeks to let > users who started to use the updated Spec change their projects to use > this new Spec2. Finally, we will revert all changes that happened on > Spec 1 and deprecate the packages. We hope this will make things > easier for everyone. > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr >

June 20, 2019

Information on Spec development

by Cyril Ferlicot

Hello everyone! This is an important update about the development of Spec. As you might have heard, we are working on Spec to release a new version in Pharo 8. One goal is to unify all Pharo interfaces behind one GUI framework and a second goal is to allow multiple back-ends (Morphic but also GTK, Bloc, ...). To reach those goals we have been updating the current version of Spec. We see now, however, that updating Spec directly creates troubles with migration. For example, we currently have a lot of deprecation warnings in Iceberg, because we can't update it without breaking Pharo 7 compatibility. After some discussions between the engineers working on Spec, here is our plan to improve the situation: We will copy all classes of Spec and rename them with the "Sp" prefix. (We will also ensure that every class of Spec started with the same prefix for consistency). For extensions methods, we will rename them to have a version different from Spec 1 (The spec from Pharo 7). Once done we will integrate this new version in Pharo 8. From there we will wait some weeks to let users who started to use the updated Spec change their projects to use this new Spec2. Finally, we will revert all changes that happened on Spec 1 and deprecate the packages. We hope this will make things easier for everyone. Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

June 20, 2019

[Pharo 8.0] Build #365: 3561-clean-up-SystemNavigationremoveAllButPackages

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

There is a new Pharo build available! The status of the build #365 was: FAILURE. The Pull Request #3562 was integrated: "3561-clean-up-SystemNavigationremoveAllButPackages" Pull request url: https://github.com/pharo-project/pharo/pull/3562 Issue Url: https://github.com/pharo-project/pharo/issues/3561 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 20, 2019

Re: [Pharo-dev] Status Pharo and PI / ARM

by Marcus Denker

> On 20 Jun 2019, at 07:27, ducasse <stepharo(a)netcourrier.com> wrote: > > Allex can you prepare modifications so that we can change the download page and we should add this information somewhere also in the main pharo > website. > Yes, we were waiting for the website to have all the tutorialsâ¦ when this is done it needs to be officially announced and linked on the main page. Marcus

June 20, 2019

Re: [Pharo-dev] Status Pharo and PI / ARM

by ducasse

Allex can you prepare modifications so that we can change the download page and we should add this information somewhere also in the main pharo website. Stef > On 19 Jun 2019, at 16:26, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > (answers from Allexâ¦) > >> On 19 Jun 2019, at 13:31, Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: >> >> Back in 2015 I played with Pharo and the PI and wrote an article on Medium about the installation [1]. >> Today we have new IoT projects like PharoThings [2] and my understanding is that latest ARM VM is >> available on [3]. >> >> But PI and ARM Support is nowhere mentioned on the pharo.org <http://pharo.org/> Website. ARM and PI Support is also not >> mentioned in the Download section http://www.pharo.org/download <http://www.pharo.org/download> >> >> >> 1. What is the status of the ARM port? Is my assumption correct that it is already built using CI and >> receiving latest VM code changes too? >> > > Yes, currently, the Pharo VM is running on ARM and built using CI. > >> 2. Should it be mentioned already on the Pharo Download page? If so who can add it? >> > > Currently, the ARM VM is being mentioned on the PharoThings repository docs. But yes, it's a good idea to be mentioned in the Pharo Download page too. > >> 3. Is it already included into ZeroConf so one can easily grab VM+image on a raspbian system >> using commandline? >> > > Yes, "wget -O - get.pharoiot.org/server <http://get.pharoiot.org/server> | bash". PharoThings has a dedicated website pharoiot.org <http://pharoiot.org/>, where there are tutorials, videos, books about it. There is a multi-platform zip file that you can download it and run in (Linux, Windows, Mac, Raspberry). All process to generate the zip files is be doing by Travis CI at github.com/pharo-iot/Ci <https://github.com/pharo-iot/Ci> > > see get.pharoiot.org <http://get.pharoiot.org/server> >> 4. Can we use a recent image like Pharo 7 and Pharo 8 on the PI? >> > > Yes. "wget -O - get.pharoiot.org/server <http://get.pharoiot.org/server> | bash" already comes with Pharo 7 and ARM VM. > >> 5. Is it possible to remotely access a Pharo image running on PI via TelePharo? > > Yes, you can access it via TelePharo. You can see details in pharoiot.org <http://pharoiot.org/>. By VNC not yet. > You can see the last improvements on the Pharo IoT project in these slides: https://www.slideshare.net/MrAllexOliveira/pharo-iot-installation-improveme… <https://www.slideshare.net/MrAllexOliveira/pharo-iot-installation-improveme…> >> Is there an updated RFB package for Pharo 7/8 to also use the image via VNCViewer >> > > You're welcome! Thanks for the report too. > >> Thanks for an update... >> >> Bye >> T. >> >> [1] https://medium.com/concerning-pharo/pharo-pi-9eef257b6a21 <https://medium.com/concerning-pharo/pharo-pi-9eef257b6a21> >> [2] https://github.com/pharo-iot/PharoThings <https://github.com/pharo-iot/PharoThings> >> [3] http://files.pharo.org/vm/pharo-spur32/linux/armv6/ <http://files.pharo.org/vm/pharo-spur32/linux/armv6/>

June 20, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Tudor Girba

Hi Monty, Did you have the chance to move XMLSupport to GitHub? Cheers, Doru > On Mar 7, 2019, at 11:19 AM, monty <monty2(a)programmer.net> wrote: > > I will move it to github, if that makes things easier for everyone else. > > ___ > montyos.wordpress.com > > >> Sent: Wednesday, January 30, 2019 at 3:13 PM >> From: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Cc: monty <monty2(a)programmer.net> >> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ >> >> >> >>> On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: >>> >>> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. >> >> Has there been any progress in this area ? >> >> It would be really great if this important project moved to GitHub. >> >> Sven >> >> > -- feenk.com âLive like you mean it."

June 20, 2019

[Pharo 8.0] Build #364: 3580-unify-RGMethodDefinition-creation-in-SystemNavigation-and-methodReference

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

There is a new Pharo build available! The status of the build #364 was: SUCCESS. The Pull Request #3581 was integrated: "3580-unify-RGMethodDefinition-creation-in-SystemNavigation-and-methodReference" Pull request url: https://github.com/pharo-project/pharo/pull/3581 Issue Url: https://github.com/pharo-project/pharo/issues/3580 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 19, 2019

[Pharo 8.0] Build #363: Correctly deprecate RGPackage and introduce Deprecated80 package

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

There is a new Pharo build available! The status of the build #363 was: FAILURE. The Pull Request #3544 was integrated: "Correctly deprecate RGPackage and introduce Deprecated80 package" Pull request url: https://github.com/pharo-project/pharo/pull/3544 Issue Url: https://github.com/pharo-project/pharo/issues/3542 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 19, 2019