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

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
by monty Oct. 3, 2018

Oct. 3, 2018

Again, for the record, I have no idea who "monty kamath" (monthkamath@gmailcom) is. Do not send any inquiries to him about those projects. 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. ___ montyos.wordpress.com > Sent: Saturday, September 29, 2018 at 5:26 AM > From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: monty <monty2(a)programmer.net>, montykamath(a)gmail.com > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > I think that would be monty, email addresses (CC-ed) > > monty2(a)programmer.net > montykamath(a)gmail.com > > I should note that he has been very good at maintaining the XML packages (the specs of which are super complex), and as far as I know, the code works under Pharo 7 ... > > What does not work for you ? > > Sven > > > On 29 Sep 2018, at 10:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > Hi > > > > I contacted the maintainer (but I'm not sure in fact who it is :) ) > > about the XML related packages in Pharo extras. > > > > XMLParser > > XMLParserHTML > > XMLParserStAX > > XMLSupport > > XMLWriter > > XPath > > > > I did not get any answer so may be I sent a mail to the wrong email address. > > Probably. > > Now the question still remains: who is planning to migrate the XML packages. > > I was planning to do it but I will not consider history because I do > > not know how to do it and I do not have the time to do it (sorry). And > > yes I work the weekends and this is bad and this is not even on Pharo. > > > > I was planning to spend some time on the baseline and making sure that > > we can load everything and run the tests. > > So let me know. > > > > Stef > > > >

1 0

Slowness when loading code in Pharo 7?
by Andrei Chis Oct. 3, 2018

Oct. 3, 2018

Hi, Are there any know slowdowns when loading code in Pharo 7? Usually on my machine (Mac - HighSierra) loading GToolkit in a Pharo 6.1 images takes around 9 minutes. In the latest Pharo 7 it takes 20 minutes. On two other newer laptops running Mac results are similar (15 minutes on Pharo 7 64it, and 7 minutes on Pharo 6.1 64bit). We have the impression that most of the times, the regression happens because of reading sources file. And the sources files are read because of checking Epicea method changes. We have not done a deep research on it, just whenever we do CMD+. it stops in that stage. Cheers, Andrei

4 3

Tonel support for Travis CI smalltalkCI for Pharo < 6.1
by Sven Van Caekenberghe Oct. 2, 2018

Oct. 2, 2018

Hi, I managed to get successful BaselineOf builds out of a GitHub in Tonel format for Pharo 7 (64 & 32 bits) and Pharo 6.1 using Travis CI and smalltalkCI. However, this does not seem to work for Pharo 6 or 5. Is this to be expected ? You can see a build failure here: https://travis-ci.org/svenvc/ztimestamp/builds/436146649 If this does not work, does that then mean that for those versions of Pharo, they cannot load Tonel projects ? This is of course related to my previous question about the reach of Tonel/github. Thx, Sven

3 4

[Pharo 7.0-dev] Build #1289: 21919-MessageTally-testTallySends-is-yellow-on-64-bit-Ubuntu-while-green-on-32-bit-Windows
by ci-pharo-ci-jenkins2＠inria.fr Oct. 2, 2018

Oct. 2, 2018

There is a new Pharo build available! The status of the build #1289 was: FAILURE. The Pull Request #1850 was integrated: "21919-MessageTally-testTallySends-is-yellow-on-64-bit-Ubuntu-while-green-on-32-bit-Windows" Pull request url: https://github.com/pharo-project/pharo/pull/1850 Issue Url: https://pharo.fogbugz.com/f/cases/21919 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

ZipArchive and symbolic links
by Cyril Ferlicot Oct. 2, 2018

Oct. 2, 2018

Hi! I just found that ZipArchive does not honor symbolic links (at least in Pharo 7). I would like to know if this is a known bug? I found out because I was using Pharo to unzip some Pharo vms and it broke all the dynamic libraries :( -- Cyril Ferlicot https://ferlicot.fr

3 2

[ANN] Success story Mobility Map
by Norbert Hartl Oct. 2, 2018

Oct. 2, 2018

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:

6 11

[Pharo 7.0-dev] Build #1288: Use /tmp (or analog in other OSs) instead of the working "directory"
by ci-pharo-ci-jenkins2＠inria.fr Oct. 2, 2018

Oct. 2, 2018

There is a new Pharo build available! The status of the build #1288 was: SUCCESS. The Pull Request #1849 was integrated: "Use /tmp (or analog in other OSs) instead of the working "directory"" Pull request url: https://github.com/pharo-project/pharo/pull/1849 Issue Url: https://pharo.fogbugz.com/f/cases/21167 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Reach of Iceberg/git/tonel ?
by Sven Van Caekenberghe Oct. 2, 2018

Oct. 2, 2018

Hi, So the future for Pharo is Iceberg/git/tonel and that is fine. My question however is: if I convert my external libraries to this new format, what is the reach of this new technology ? Can people still load code in older versions of Pharo ? I think 6.x is no problem, but what about earlier versions ? What about other Smalltalk implementations ? What is the official answer here ? A second question: suppose a repo is converted, is then still possible to copy a version over to an old MC repo ? Just to keep it in sync. Thx, Sven

6 7

[ANN] Migrated Artefact to GitHub
by Stephane Ducasse Oct. 2, 2018

Oct. 2, 2018

Hi guille I deeply appreciated that you spent your time to bring Artefact to Pharo 70 and in general all the positive energy you put around Pharo. I love Iceberg! and more! I quit these mailing-lists in the past because of these little aggressions, the "You should do that" I registered today again to this mailing list just to publicly talk to you, while I could come to your office (I will do it too). I did a port of Artefact to Pharo 60 a while ago and started to fix Artefact aspects I did not like and I would like to integrate my fixes to yours. Please let me know where it is. :) I do not care of the history because I prefer the future. If people care then this is their duties. Easy. If they are not happy. This is THEIR PROBLEM. You see people often tells me that I cannot control and that github is decentralised. It is! So enjoy but @People try to avoid to piss on good will of others. Now sorry Norbert your point that Guillemo would be rude because he spent his time to help Milton and made sure that Artefact in Pharo 70 is clearly out of context and misplaced. You see I did the same in github.com/olivierauverlot because I needed it. And this is like that. Period. You are not happy. This is ok. You do not like it. This is ok too. This is several times that I noticed that your are not nice with emails so do the same than me: think about the impact on others. You have no idea about what guille is doing and what it is paid for and this is certainly not to fix Artefact. And you may notice that we know what is to work on others unmaintained code because we do it all the time, we even create documentation on systems we do not understand because some people are too busy to write method and class comments so imagine documentation. So I would like to thanks again guille and I would like to have artefact on Pharo 70. Stef

5 11

[Pharo 7.0-dev] Build #1287: 22271-Fix-IndexedSlots-in-combination-with-StatefulTraits-
by ci-pharo-ci-jenkins2＠inria.fr Oct. 1, 2018

Oct. 1, 2018

There is a new Pharo build available! The status of the build #1287 was: SUCCESS. The Pull Request #1730 was integrated: "22271-Fix-IndexedSlots-in-combination-with-StatefulTraits-" Pull request url: https://github.com/pharo-project/pharo/pull/1730 Issue Url: https://pharo.fogbugz.com/f/cases/22271 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0