August 2020 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo at JPL

by tbrunz

Hi Konrad, I'm the person at JPL who (somehow) got "The Powers That Be" here to agree to join the Consortium. I'm also the major champion of Pharo at JPL, and am leading an effort to get Pharo introduced & infused at JPL. I see the initial "market" for Pharo here to be: * Scientific & engineering data analysis & visualization, * Modeling and simulation, * Internal web servers, * Custom ground support & test systems, * Small-to-medium sized scripting to "support applications". I'm sure more application areas will open up as I get people to start using Pharo in their particular areas of expertise. I'm doing what I can be promoting Pharo, providing introductions & training, and I'm now working on demonstrations that can catch the attention of both engineers and managers -- to see the potential. Wish me luck! -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 28, 2020

Re: [Pharo-users] Checking baseline before publishing

by Jonathan van Alteren

Ah yes, sorry, you're right. You do have to commit/push for that to work. I'm interested to hear what your experience is with using #record. Kind regards, Jonathan van Alteren Founding Member | Object Guild B.V. Sustainable Software for Purpose-Driven Organizations jvalteren(a)objectguild.com On 28 Aug 2020, 20:00 +0200, Esteban Maringolo <emaringolo(a)gmail.com>, wrote: > Hi Jonathan, > > I never thought of SmalltalkCI for that (I use Gitlab) but in essence > it still requires a trial and error approach (of committing the > Baseline and loading it afterwards to see if it works). > > Metacello has a "record" operation that basically does a dry run of > the load, but I don't know if there is a way to do it using the > Baseline in the image instead of one in a repository. > > Regards! > > Esteban A. Maringolo > > On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren > <jvalteren(a)objectguild.com> wrote: > > > > Hi Esteban, > > > > You might want to give smalltalkCI a try: https://github.com/hpi-swa/smalltalkCI > > > > I've recently started using it myself, with GitLab CI and GitHub Actions, but one of the cool things is that you can use it to test your build locally. > > > > For example, create a .smalltalk.ston file for your project which loads the baseline that you want to test, like this: > > > > SmalltalkCISpec { > > #loading : [ > > SCIMetacelloLoadSpec { > > #baseline : 'MyProject', > > #directory : 'source', > > #load : [ 'default' ], > > #onWarningLog : true, > > #platforms : [ #pharo ] > > } > > ], > > #testing : { > > #categories : [ 'MyProject-Tests' ] > > } > > } > > > > Then clone the smalltalkCI repo locally and open a terminal on its location, for example /Users/johndoe/git/smalltalkCI. You can then simply use smalltalkCI to build a Pharo image of your baseline, which effectively tests the correct working of your baseline: > > > > bin/smalltalkci -s "Pharo64-8.0" /Users/johndoe/git/MyProject/.smalltalk.ston > > > > By default, it will run all tests in the image, but you can change the list of tests being run by modifying the .smalltalk.ston file accordingly (see https://github.com/hpi-swa/smalltalkCI#testcase-selection) > > > > Hope this helps! > > > > Kind regards, > > > > Jonathan van Alteren > > > > Founding Member | Object Guild B.V. > > Sustainable Software for Purpose-Driven Organizations > > > > jvalteren(a)objectguild.com > > On 27 Aug 2020, 04:12 +0200, Esteban Maringolo <emaringolo(a)gmail.com>, wrote: > > > > Hi, > > > > How can I check that my baseline works without having to publish > > everything, check that it fails and then going to the origin, fixing, > > etc? > > > > I might be particularly idiot to always miss something, I usually have > > to try at least four times (in a blank image) that my Baseline, > > dependencies, etc. works as expected. > > > > There must be some other way. > > > > Esteban A. Maringolo > > >

Aug. 28, 2020

Re: [Pharo-users] Checking baseline before publishing

by Dale Henrichs

Esteban, #record _is_ run against the baseline that is in the image if it is present. This is true for all of the Metacello commands - if the BaselineOf is present it is used, if it is not present it will be loaded. The #get command will load a fresh copy of the baseline from the repository. There is an option to ignore image state (#ignoreImage) when running #record (or any other command) to simulate loading into an "empty" image ... depending upon the volume of output, you could read the report to determine if the packages/projects that you are expecting to see are being loaded and of course if your goal is to expose outright errors #record should do that as well ... Dale On 8/28/20 10:59 AM, Esteban Maringolo wrote: > Hi Jonathan, > > I never thought of SmalltalkCI for that (I use Gitlab) but in essence > it still requires a trial and error approach (of committing the > Baseline and loading it afterwards to see if it works). > > Metacello has a "record" operation that basically does a dry run of > the load, but I don't know if there is a way to do it using the > Baseline in the image instead of one in a repository. > > Regards! > > Esteban A. Maringolo > > On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren > <jvalteren(a)objectguild.com> wrote: >> Hi Esteban, >> >> You might want to give smalltalkCI a try: https://github.com/hpi-swa/smalltalkCI >> >> I've recently started using it myself, with GitLab CI and GitHub Actions, but one of the cool things is that you can use it to test your build locally. >> >> For example, create a .smalltalk.ston file for your project which loads the baseline that you want to test, like this: >> >> SmalltalkCISpec { >> #loading : [ >> SCIMetacelloLoadSpec { >> #baseline : 'MyProject', >> #directory : 'source', >> #load : [ 'default' ], >> #onWarningLog : true, >> #platforms : [ #pharo ] >> } >> ], >> #testing : { >> #categories : [ 'MyProject-Tests' ] >> } >> } >> >> Then clone the smalltalkCI repo locally and open a terminal on its location, for example /Users/johndoe/git/smalltalkCI. You can then simply use smalltalkCI to build a Pharo image of your baseline, which effectively tests the correct working of your baseline: >> >> bin/smalltalkci -s "Pharo64-8.0" /Users/johndoe/git/MyProject/.smalltalk.ston >> >> By default, it will run all tests in the image, but you can change the list of tests being run by modifying the .smalltalk.ston file accordingly (see https://github.com/hpi-swa/smalltalkCI#testcase-selection) >> >> Hope this helps! >> >> Kind regards, >> >> Jonathan van Alteren >> >> Founding Member | Object Guild B.V. >> Sustainable Software for Purpose-Driven Organizations >> >> jvalteren(a)objectguild.com >> On 27 Aug 2020, 04:12 +0200, Esteban Maringolo <emaringolo(a)gmail.com>, wrote: >> >> Hi, >> >> How can I check that my baseline works without having to publish >> everything, check that it fails and then going to the origin, fixing, >> etc? >> >> I might be particularly idiot to always miss something, I usually have >> to try at least four times (in a blank image) that my Baseline, >> dependencies, etc. works as expected. >> >> There must be some other way. >> >> Esteban A. Maringolo >>

Aug. 28, 2020

Re: [Pharo-users] Pharo.exe and PharoConsole.exe VM Difference

by StÃ©phane Ducasse

On windows you cannot have the same executable being to log info or not. So this is why we are forced to have two different versions. S > On 28 Aug 2020, at 03:48, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi, > > What is the difference between the Pharo.exe and PharoConsole.exe? > They have the same size, but are binary different. > > I'd expect the PharoConsole to run headless by default, but it is not the case. > > So... is this documented anywhere? > > Thanks! > > Esteban A. Maringolo > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle 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

Aug. 28, 2020

Re: [Pharo-users] Checking baseline before publishing

by Esteban Maringolo

Hi Jonathan, I never thought of SmalltalkCI for that (I use Gitlab) but in essence it still requires a trial and error approach (of committing the Baseline and loading it afterwards to see if it works). Metacello has a "record" operation that basically does a dry run of the load, but I don't know if there is a way to do it using the Baseline in the image instead of one in a repository. Regards! Esteban A. Maringolo On Fri, Aug 28, 2020 at 10:10 AM Jonathan van Alteren <jvalteren(a)objectguild.com> wrote: > > Hi Esteban, > > You might want to give smalltalkCI a try: https://github.com/hpi-swa/smalltalkCI > > I've recently started using it myself, with GitLab CI and GitHub Actions, but one of the cool things is that you can use it to test your build locally. > > For example, create a .smalltalk.ston file for your project which loads the baseline that you want to test, like this: > > SmalltalkCISpec { > #loading : [ > SCIMetacelloLoadSpec { > #baseline : 'MyProject', > #directory : 'source', > #load : [ 'default' ], > #onWarningLog : true, > #platforms : [ #pharo ] > } > ], > #testing : { > #categories : [ 'MyProject-Tests' ] > } > } > > Then clone the smalltalkCI repo locally and open a terminal on its location, for example /Users/johndoe/git/smalltalkCI. You can then simply use smalltalkCI to build a Pharo image of your baseline, which effectively tests the correct working of your baseline: > > bin/smalltalkci -s "Pharo64-8.0" /Users/johndoe/git/MyProject/.smalltalk.ston > > By default, it will run all tests in the image, but you can change the list of tests being run by modifying the .smalltalk.ston file accordingly (see https://github.com/hpi-swa/smalltalkCI#testcase-selection) > > Hope this helps! > > Kind regards, > > Jonathan van Alteren > > Founding Member | Object Guild B.V. > Sustainable Software for Purpose-Driven Organizations > > jvalteren(a)objectguild.com > On 27 Aug 2020, 04:12 +0200, Esteban Maringolo <emaringolo(a)gmail.com>, wrote: > > Hi, > > How can I check that my baseline works without having to publish > everything, check that it fails and then going to the origin, fixing, > etc? > > I might be particularly idiot to always miss something, I usually have > to try at least four times (in a blank image) that my Baseline, > dependencies, etc. works as expected. > > There must be some other way. > > Esteban A. Maringolo >

Aug. 28, 2020

Re: [Pharo-users] Checking baseline before publishing

by Jonathan van Alteren

Hi Esteban, You might want to give smalltalkCI a try:Â https://github.com/hpi-swa/smalltalkCI I've recently started using it myself, with GitLab CI and GitHub Actions, but one of the cool things is that you can use it to test your build locally. For example, create a .smalltalk.ston file for your project which loads the baseline that you want to test, like this: SmalltalkCISpec { Â Â #loading : [ Â Â Â SCIMetacelloLoadSpec { Â Â Â Â #baseline : 'MyProject', Â Â Â Â #directory : 'source', Â Â Â Â #load : [ 'default' ], Â Â Â Â #onWarningLog : true, Â Â Â Â #platforms : [ #pharo ] Â Â Â } Â Â ], Â Â #testing : { Â Â Â #categories : [ 'MyProject-Tests' ] Â Â } } Then clone the smalltalkCI repo locally and open a terminal on its location, for example /Users/johndoe/git/smalltalkCI. You can then simply use smalltalkCI to build a Pharo image of your baseline, which effectively tests the correct working of your baseline: bin/smalltalkci -s "Pharo64-8.0" /Users/johndoe/git/MyProject/.smalltalk.ston By default, it will run all tests in the image, but you can change the list of tests being run by modifying the .smalltalk.ston file accordingly (seeÂ https://github.com/hpi-swa/smalltalkCI#testcase-selection) Hope this helps! Kind regards, Jonathan van Alteren Founding Member | Object Guild B.V. Sustainable Software for Purpose-Driven Organizations jvalteren(a)objectguild.com On 27 Aug 2020, 04:12 +0200, Esteban Maringolo <emaringolo(a)gmail.com>, wrote: > Hi, > > How can I check that my baseline works without having to publish > everything, check that it fails and then going to the origin, fixing, > etc? > > I might be particularly idiot to always miss something, I usually have > to try at least four times (in a blank image) that my Baseline, > dependencies, etc. works as expected. > > There must be some other way. > > Esteban A. Maringolo >

Aug. 28, 2020

Re: [Pharo-users] pharo books as audiobooks

by niepiekm

Hi Siemen, all, you may listen to PDF files from the Web via 'Read Aloud' Chrome extension (https://chrome.google.com/webstore/detail/read-aloud-a-text-to-spee/hdhinad…) and use its service at https://assets.lsdsoftware.com/read-aloud/page-scripts/pdf-upload.html to open and listen to local PDF files. Simply open a local PDF file via the service and click on the extension button. Regards, Marek -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 28, 2020

pharo books as audiobooks

by Siemen Baader

Hi all, I'm interested in listening to the pharo books as audiobooks, away from my desk. I read them to learn higher level concepts and can get back to the code boxes later to look up the details, so I'm not too worried about how to exactly convert the code boxes to audio. One way to enable this would be if the books were served publicly as static HTML. One can then use the Pocket App to save them and listen on the go. In theory this should be something that the CI system could just be set up to do, right? (There are apps to convert PDFs to audio too, but those I have been able to find are inconvenient and / or expensive.) Is anyone who is already familiar with the CI system interested in setting this up? I'd love to help but don't have the time, unfortunately. But I'm happy to provide feedback. I'v cheers Siemen

Aug. 28, 2020

Pharo at JPL

by Konrad Hinsen

Hi everyone, I just saw the news (on Twitter) that JPL (NASA's Jet Propulsion Laboratory) has joined the Pharo Consortium. Does anyone here know what JPL is doing with Pharo? If it's related to scientific/engineering applications, that would be a nice marketing argument in the scientific/engineering community. Konrad.

Aug. 28, 2020

Re: [Pharo-users] Pharo.exe and PharoConsole.exe VM Difference

by Cyril Ferlicot D.

On 8/28/2020 3:48 AM, Esteban Maringolo wrote: > Hi, > > What is the difference between the Pharo.exe and PharoConsole.exe? > They have the same size, but are binary different. > > I'd expect the PharoConsole to run headless by default, but it is not the case. > > So... is this documented anywhere? > > Thanks! > > Esteban A. Maringolo > Hi, IIRC the PharoConsole.exe is able to manage stdout and stderr while Pharo.exe is not. -- Cyril Ferlicot https://ferlicot.fr

Aug. 28, 2020