September 2018 - Pharo-dev - lists.pharo.org

[ANN] Pharo Consortium upgrade to Platinum: ZWEIDENKER

by Marcus Denker

The Pharo Consortium is very happy to announce that ZWEIDENKER has ugraded to be a Platinum member. About - ZWEIDENKER: http://zweidenker.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Sept. 25, 2018

[Pharo 7.0-dev] Build #1264: 22471 prepare pharo7.0.0 rc1 release

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

There is a new Pharo build available! The status of the build #1264 was: SUCCESS. The Pull Request #1817 was integrated: "22471 prepare pharo7.0.0 rc1 release" Pull request url: https://github.com/pharo-project/pharo/pull/1817 Issue Url: https://pharo.fogbugz.com/f/cases/22471 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 25, 2018

Re: [Pharo-dev] [ANN] Success story Mobility Map

by Sven Van Caekenberghe

Wow. Very nice, well done. Any chance on some more technical details, as in what 'connected by a message queue for the communication' exactly means ? How did you approach micro services exactly ? > On 25 Sep 2018, at 12:20, Norbert Hartl <norbert(a)hartl.name> wrote: > > As presented on ESUG here is the brief description of one of our current projects. > > Mobility Map > ââââââ > > Mobility Map is a broker for mobility services. It offers multi-modal routing search enabling users to find the best travel options between locations. Travel options include car sharing, bikes, trains, busses etc. Rented cars can be offered for ride sharing on booking time letting other people find it to participate in the ride. Single travel options are combined in travel plans that can be booked and managed in a very easy way. > > For this project main requirements were scalability to serve a large user base and flexibility to add more additional providers to the broker. The application has been realized using web technologies for the frontend and pharo for the backend. Using a microservice architecture combined with a broker it is easy to extend the platform with additional brokers. Deployment is done using docker swarm for distributing dozens of pharo images among multiple server machines connected by a message queue for the communication. Pharo supported that scenario very well enabling us the meet the requirements with less effort. > > Pharo turned out to be a perfect fit to develop the application in a agile way. Small development cycles with continuous integration and continuous delivery enables fast turnarounds for the customers to validate progress. > > This is a screenshot of the search page for multi-modal results: > > > <Screen Shot 2018-09-21 at 16.54.30.png>

Sept. 25, 2018

[ANN] Success story Mobility Map

by Norbert Hartl

As presented on ESUG here is the brief description of one of our current projects. Mobility Map ââââââ Mobility Map is a broker for mobility services. It offers multi-modal routing search enabling users to find the best travel options between locations. Travel options include car sharing, bikes, trains, busses etc. Rented cars can be offered for ride sharing on booking time letting other people find it to participate in the ride. Single travel options are combined in travel plans that can be booked and managed in a very easy way. For this project main requirements were scalability to serve a large user base and flexibility to add more additional providers to the broker. The application has been realized using web technologies for the frontend and pharo for the backend. Using a microservice architecture combined with a broker it is easy to extend the platform with additional brokers. Deployment is done using docker swarm for distributing dozens of pharo images among multiple server machines connected by a message queue for the communication. Pharo supported that scenario very well enabling us the meet the requirements with less effort. Pharo turned out to be a perfect fit to develop the application in a agile way. Small development cycles with continuous integration and continuous delivery enables fast turnarounds for the customers to validate progress. This is a screenshot of the search page for multi-modal results:

Sept. 25, 2018

[Pharo 7.0-dev] Build #1263: Avoid race conditions between tests by removing parallel runs

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

There is a new Pharo build available! The status of the build #1263 was: SUCCESS. The Pull Request #1824 was integrated: "Avoid race conditions between tests by removing parallel runs" Pull request url: https://github.com/pharo-project/pharo/pull/1824 Issue Url: https://pharo.fogbugz.com/f/cases/22485 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 25, 2018

Re: [Pharo-dev] Files-Core and Zinc-Character-Encoding-Core package load sequence

by Alistair Grant

Hi Sven & Guille, On Tue, 25 Sep 2018 at 10:49, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > On Mon, Sep 24, 2018 at 11:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >> >> > On 24 Sep 2018, at 21:55, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> > >> > Hi Guille, Sven, Esteban and Everyone, >> > >> > Can someone (dis)confirm that the Zinc-Character-Encoding-Core package is >> > considered part of the pharo "core" image? >> >> Yes, for me anyway, it is (or should be) part of core. > > > Yes, they are part of the Core image. Simply because an image without any I/O is an image you cannot interact with, so it's kind of useless :) > And an image doing I/O without managing encoding is pretty useless too... Thanks for the confirmation. I suspected this was the case, but didn't want to be wrong later on. > Also, keep in mind that we try to maintain Zn packages in sync with Sven's repository, and we try to keep them loadable/compatible with other pharo versions. > Usually Zn encoders should be stable enough in terms of API and features, but in case you need to extend them in some way we should keep Sven in the loop so we can sync both repositories ^^. Sure, at the moment I can't envisage any required changes. Thanks again, Alistair

Sept. 25, 2018

Re: [Pharo-dev] Files-Core and Zinc-Character-Encoding-Core package load sequence

by Guillermo Polito

On Mon, Sep 24, 2018 at 11:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 24 Sep 2018, at 21:55, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Guille, Sven, Esteban and Everyone, > > > > Can someone (dis)confirm that the Zinc-Character-Encoding-Core package is > > considered part of the pharo "core" image? > > Yes, for me anyway, it is (or should be) part of core. > Yes, they are part of the Core image. Simply because an image without any I/O is an image you cannot interact with, so it's kind of useless :) And an image doing I/O without managing encoding is pretty useless too... Also, keep in mind that we try to maintain Zn packages in sync with Sven's repository, and we try to keep them loadable/compatible with other pharo versions. Usually Zn encoders should be stable enough in terms of API and features, but in case you need to extend them in some way we should keep Sven in the loop so we can sync both repositories ^^. Guille

Sept. 25, 2018

Re: [Pharo-dev] update linux info page again, please [CentOS/RHEL]

by Marcus Denker

Hello, I have added it. https://pharo.org/gnu-linux-installation-64 > On 23 Sep 2018, at 18:32, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: update linux info page again, please [CentOS/RHEL] > Date: 23 September 2018 at 18:32:00 CEST > To: pharo-dev(a)lists.pharo.org > > > Hello, > > please, edit CentOS7 installation page: > https://pharo.org/gnu-linux-installation-64 > > and add workaround for CentOS7 section, wihout this symlink, iceberg is broken: > > (do as root) > cd /usr/lib64 > ln -s libcurl.so.4 libcurl-gnutls.so.4 > > Best solution is to put this in the RPM post installation step (I mean RPM from official Pharo CentOS repository) - but we will wait for this fix for months, maybe years, so, workaround info on that page is necessary and easy to manage. > > More details here: > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2018-July/272624… > > Thanks! pf > > >

Sept. 25, 2018

[ANN] Pharo Consortium New Bronze Member: Spesenfuchs

by Marcus Denker

The Pharo Consortium is very happy to announce that Spesenfuchs has joined the Consortium as a Bronze Member. About - Spesenfuchs: http://spesenfuchs.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Sept. 25, 2018

Re: [Pharo-dev] Files-Core and Zinc-Character-Encoding-Core package load sequence

by Sven Van Caekenberghe

> On 24 Sep 2018, at 21:55, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Guille, Sven, Esteban and Everyone, > > Can someone (dis)confirm that the Zinc-Character-Encoding-Core package is > considered part of the pharo "core" image? Yes, for me anyway, it is (or should be) part of core. > The reason I ask is that I'd like to know whether the File class (which > is part of the Files-Core package) can count on ZnUTF8Encoder (which is > part of the Zinc-Character-Encoding-Core package) being present in the > image. > > If File can count on ZnUTF8Encoder being present then for FileAttributes > I will make UTF8 encoding / decoding available from File, and thus UTF8 > file names will be supported. If it can't count on ZnUTF8Encoder being > present then File will only be able to handle ascii file names (unless > the names are somehow already UTF8 encoded) and support for UTF8 file > names will effectively be restricted to FileSystem. > > > Thanks, > Alistair >

Sept. 24, 2018