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

[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

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 #1281: 22433-Review-FloatTest-testCopySignTo-and-testSign
by ci-pharo-ci-jenkins2＠inria.fr Sept. 30, 2018

Sept. 30, 2018

There is a new Pharo build available! The status of the build #1281 was: SUCCESS. The Pull Request #1835 was integrated: "22433-Review-FloatTest-testCopySignTo-and-testSign" Pull request url: https://github.com/pharo-project/pharo/pull/1835 Issue Url: https://pharo.fogbugz.com/f/cases/22433 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1280: 22489-cleanup--CompilationContext-and-doSemanticAnalysis
by ci-pharo-ci-jenkins2＠inria.fr Sept. 30, 2018

Sept. 30, 2018

There is a new Pharo build available! The status of the build #1280 was: SUCCESS. The Pull Request #1830 was integrated: "22489-cleanup--CompilationContext-and-doSemanticAnalysis" Pull request url: https://github.com/pharo-project/pharo/pull/1830 Issue Url: https://pharo.fogbugz.com/f/cases/22489 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1279: 22498-TextEditorsaveContentsInFile-should-not-use-FileStream
by ci-pharo-ci-jenkins2＠inria.fr Sept. 30, 2018

Sept. 30, 2018

There is a new Pharo build available! The status of the build #1279 was: FAILURE. The Pull Request #1839 was integrated: "22498-TextEditorsaveContentsInFile-should-not-use-FileStream" Pull request url: https://github.com/pharo-project/pharo/pull/1839 Issue Url: https://pharo.fogbugz.com/f/cases/22498 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1278: 22397-Add-executable-comments-to-Date-classes
by ci-pharo-ci-jenkins2＠inria.fr Sept. 29, 2018

Sept. 29, 2018

There is a new Pharo build available! The status of the build #1278 was: SUCCESS. The Pull Request #1832 was integrated: "22397-Add-executable-comments-to-Date-classes" Pull request url: https://github.com/pharo-project/pharo/pull/1832 Issue Url: https://pharo.fogbugz.com/f/cases/22397 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1277: 22497-MIMEDocumentsaveToFile-should-not-use-FileStream
by ci-pharo-ci-jenkins2＠inria.fr Sept. 29, 2018

Sept. 29, 2018

There is a new Pharo build available! The status of the build #1277 was: SUCCESS. The Pull Request #1838 was integrated: "22497-MIMEDocumentsaveToFile-should-not-use-FileStream" Pull request url: https://github.com/pharo-project/pharo/pull/1838 Issue Url: https://pharo.fogbugz.com/f/cases/22497 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Artifact and PDFExporter for Roassal
by milton mamani Sept. 28, 2018

Sept. 28, 2018

El jue., 13 sept. 2018 a las 14:06, milton mamani (<akevalion(a)gmail.com>) escribiÃ³: > Hi! > > I am Milton Mamani I work with Roassal2, and now I am in ESUG-Cagliari, > and I have tried to load Artefact with the next piece of code, in the last > Pharo7 image. > > Metacello new > configuration: 'Artefact'; > smalltalkhubUser: 'RMoD' project: 'Artefact'; > version: #stable; > load. > > "To load roassal and pdf roassal exporter" > > Metacello new > configuration: 'GraphQLBeta'; > smalltalkhubUser: 'ObjectProfile' project: 'GraphQL'; > version: #development; > load. > > Gofer new > smalltalkhubUser: 'azazael' project: 'RTPDFExporter'; > package: 'ConfigurationOfRTPDFExporter'; load. > (Smalltalk at: #ConfigurationOfRTPDFExporter) loadDevelopment > > I have a problem, when I tried to export my Roassal-Visualization to pdf > file with for example this piece of code: > > view := RTBoxPlotExample new exampleBoxPlot5 build view. > stream := 'foo.pdf' asFileReference writeStream. > > [RTPDFExporter new > stream: stream; > exportView: view ] ensure: [ stream close ] > > I get a lot of kind exceptions related with the class: PDFStreamPrinter > > In the method visitPDFDataXRefEntry: > And in the logic of the new Stream classes of Pharo7. > > Could you please review Artifact in Pharo7 with this roassal2 > implementation > > Cheers, > Milton > >

3 2

[Pharo 7.0-dev] Build #1276: 22482-AutoCompletion-preview-breaks-code-navigation
by ci-pharo-ci-jenkins2＠inria.fr Sept. 28, 2018

Sept. 28, 2018

There is a new Pharo build available! The status of the build #1276 was: SUCCESS. The Pull Request #1831 was integrated: "22482-AutoCompletion-preview-breaks-code-navigation" Pull request url: https://github.com/pharo-project/pharo/pull/1831 Issue Url: https://pharo.fogbugz.com/f/cases/22482 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0