- Pharo-users - lists.pharo.org

Re: [Pharo-users] pharo books as audiobooks

by Siemen Baader

Hi Marek, Thanks for the pointer. This is useful and interesting, but I wasn't clear enough - I need the audio on my mobile phone and it needs to bookmark where I left off, like audio book players and podcast apps do. Pocket has a very nice workflow for this because I can bookmark a web site in Firefox, then play back on mobile later. I've also used http://talkify.net and saved the whole .mp3 file as an audio book to my mobile device, but talkify and Pocket only work with HTML accessible over http via a public URL. But thanks, and I'll probably learn something from this tool as well. Besides - another reason why it would be cool if http://books.pharo.org had supplementary HTML builds with unique anchors for chapters and sections because this makes it very easy to point to specific sections in the books when answering questions on the mailing list. cheers, Siemen On Fri, Aug 28, 2020 at 12:37 PM niepiekm <niepiekm(a)gmail.com> wrote: > 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. 29, 2020

Re: [Pharo-users] [Ann] Workshop: IndieWeb with pocket infrastructures

by StÃ©phane Ducasse

I published it on Pharo weekly Keep pushing. I love this local first and your effort. s > On 29 Aug 2020, at 02:08, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi all, > > Due to the confinement in the pandemic, our forms of telepresence become > more important and many suddenly got even more immersed into an > Oligopoly cyberspace (Zoom, Google, Facebook, Twitter, Apple, Amazon, > Microsoft, etc) with opaque algorithms that under extractive logic > commodify our privacy and communications, try to condition our attention > and habits, as well as to shape our current and future behavior. But > this is not the only way to inhabit cyberspace. > > From the Grafoscopio community[1], we would like to invite you to a > series of workshops that we are doing to make visible other ways of > populating and building the web, aligned with the movements of > IndieWeb[1a], from what we have called "pocket infrastructures". You can > find more information about these topics in [2] and in particular about > the workshops in [3] (in Spanish). > > [1] https://mutabit.com/grafoscopio/en.html > [1a] https://indieweb.org/ > [2] https://mutabit.com/repos.fossil/indieweb/ > [3] > https://mutabit.com/repos.fossil/indieweb/doc/trunk/docs/es/index.html#tall… > > > The second workshop will be tomorrow, Saturday, Aug. 29 from 3:15 PM to > 7:15PM CO (GMT - 5) -- I will try to share the other workshops earlier, > but the site in [2] will be the consolidated memory of them, for those > who want to join us asynchronously. > > We will see how IndieWeb sites help us to untangle and reweave that > other web and how this help us to reconnect in this stranger times. > > Rethinking the infrastructure is also to rethink the ways in which it > enables and makes visible (or not) certain ways of being and acting. > Infrastructures are embodied discourses. So thank you in advance for > joining us in rethinking this in practice. > > Of course, Pharo is behind scenes, as usual, powering this experience. > But with these IndieWeb workshops I think we have found a sweet spot > that puts coding in front with a practical introduction and motivation > beyond the kind of boring "Hello World". Following a "local first" > approach, documentation will be in Spanish, but source code[5] and > interactive documentation will be in English to bridge our worlds :-), > > [4] https://mutabit.com/offray/blog/en/entry/dumb-hello-world > [5] https://mutabit.com/repos.fossil/brea/ > > > See you on cyberspace, > > Offray > > > -------------------------------------------- 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. 29, 2020

Re: [Pharo-users] Checking baseline before publishing

by StÃ©phane Ducasse

> On 28 Aug 2020, at 23:45, Jonathan van Alteren <jvalteren(a)objectguild.com> wrote: > > 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. My experience is that there is nothing better than what you propose. > > 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 >>> >> -------------------------------------------- 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. 29, 2020

Re: [Pharo-users] Getting rid of .sources file for deployment

by StÃ©phane Ducasse

Hi Iâm really interested in this. Because we should be able to ship without the sources. FFI needs the source at some point but I guess that this is the first time and that the information could be stored in the compiledMethod. But I do not remember. Now may be esteban or pablo can give you some hints but frankly we are super super super busy but if you have a way and that Pharo should be changed to support this scenario let us know we will support you. S > On 29 Aug 2020, at 04:49, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi, > > Is there a way to get rid the .sources file in a deployment scenario? > > I followed this guide [1], but I cannot get rid of the .sources files, > because I'm using PharoADO (which uses PharoCOM) and it uses some > reflection for FFI and for some reason that implies using the .sources > file. I installed the FFICompilerPlugin as per the instructions, but I > don't have a way to tell whether I did in the right place/moment, nor > how to assess its proper installation. > > If such [2] .sources file cannot be removed, what is the criteria for > the lookup, can it be renamed or modified via some parameter/config? > > Thanks! > > [1] https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > [2] Pharo8.0-32bit-0932da8.sources in my case > > > 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. 29, 2020

Re: [Pharo-users] Pharo at JPL

by StÃ©phane Ducasse

> On 29 Aug 2020, at 01:46, tbrunz <wild.ideas(a)gmail.com> wrote: > > Thanks! > > And I want to give special thanks to Stef and to Alexandre Bergel for being > generous with their time in helping me with my advocacy. > > It's just as you said, Offray: "We live in an attention economy" -- and the > competition is *fierce*! Yes this is what many smalltalking people forgot. Pharo is in competition against many large languages and we are not concerned with the little fight about other dead smalltalk compatibilities. > > (I think it's worse when you're dealing with educated professionals -- they > work hard, they play hard, and there's little left over to "learn something > new" sometimes. But I am not discouraged... I take the long view on this. > Computers taught me patience. I'm using that now... ;^) > > -t > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > -------------------------------------------- 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. 29, 2020

Re: [Pharo-users] Image crashed, how can I restore the Playground?

by Esteban Maringolo

Hi Offray, Never thought of Graffoscopio as a replacement for Playground, but it seems like a good way to extend the behavior with some missing features (like explicit save, export, etc.). Is there a way to install such "core" feature without pulling Roassal nor any of the "hardcore" parts of Graffoscopio itself? Thanks! Esteban A. Maringolo On Fri, Aug 28, 2020 at 8:45 PM Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi Davide, > > You can use Grafoscopio[1] to store and structure your playgrounds as an > interactive notebook. > > [1] https://mutabit.com/grafoscopio/en.html > > Your notebooks can combine prose and be exported to other formats > (Markdown, HTML and PDF). Also, you can use your preferred source control > system to store the notebooks. For example, I use Grafoscopio notebooks and > Fossil[2] repositories to make workshop interactive notes. > > [2] https://fossil-scm.org/ > > I'm still debugging an annoying issue with keystroke capturing in > playgrounds. But Grafoscopio notebooks has been a good bridge between > coding and scripting for our local community and a great help in workshops. > > Hope that helps, > > Offray > On 26/08/20 2:33 p. m., Davide Varvello via Pharo-users wrote: > > Thanks StÃ©ph, > I guess the right directory is {imageDirectory}*/pharo-local/play-cache/* > there are some .ph files representing several playgrounds. > > One further question: it seems to me there isn't a history of the > playground, right? So if I make multiple changes to a single playground, > they are lost. > > Cheers > Davide > >

Aug. 29, 2020

Getting rid of .sources file for deployment

by Esteban Maringolo

Hi, Is there a way to get rid the .sources file in a deployment scenario? I followed this guide [1], but I cannot get rid of the .sources files, because I'm using PharoADO (which uses PharoCOM) and it uses some reflection for FFI and for some reason that implies using the .sources file. I installed the FFICompilerPlugin as per the instructions, but I don't have a way to tell whether I did in the right place/moment, nor how to assess its proper installation. If such [2] .sources file cannot be removed, what is the criteria for the lookup, can it be renamed or modified via some parameter/config? Thanks! [1] https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… [2] Pharo8.0-32bit-0932da8.sources in my case Esteban A. Maringolo

Aug. 29, 2020

[Ann] Workshop: IndieWeb with pocket infrastructures

by Offray Vladimir Luna CÃ¡rdenas

Hi all, Due to the confinement in the pandemic, our forms of telepresence become more important and many suddenly got even more immersed into an Oligopoly cyberspace (Zoom, Google, Facebook, Twitter, Apple, Amazon, Microsoft, etc) with opaque algorithms that under extractive logic commodify our privacy and communications, try to condition our attention and habits, as well as to shape our current and future behavior. But this is not the only way to inhabit cyberspace. >From the Grafoscopio community[1], we would like to invite you to a series of workshops that we are doing to make visible other ways of populating and building the web, aligned with the movements of IndieWeb[1a], from what we have called "pocket infrastructures". You can find more information about these topics in [2] and in particular about the workshops in [3] (in Spanish). [1] https://mutabit.com/grafoscopio/en.html [1a] https://indieweb.org/ [2] https://mutabit.com/repos.fossil/indieweb/ [3] https://mutabit.com/repos.fossil/indieweb/doc/trunk/docs/es/index.html#tall… The second workshop will be tomorrow, Saturday, Aug. 29 from 3:15 PM to 7:15PM CO (GMT - 5) -- I will try to share the other workshops earlier, but the site in [2] will be the consolidated memory of them, for those who want to join us asynchronously. We will see how IndieWeb sites help us to untangle and reweave that other web and how this help us to reconnect in this stranger times. Rethinking the infrastructure is also to rethink the ways in which it enables and makes visible (or not) certain ways of being and acting. Infrastructures are embodied discourses. So thank you in advance for joining us in rethinking this in practice. Of course, Pharo is behind scenes, as usual, powering this experience. But with these IndieWeb workshops I think we have found a sweet spot that puts coding in front with a practical introduction and motivation beyond the kind of boring "Hello World". Following a "local first" approach, documentation will be in Spanish, but source code[5] and interactive documentation will be in English to bridge our worlds :-), [4] https://mutabit.com/offray/blog/en/entry/dumb-hello-world [5] https://mutabit.com/repos.fossil/brea/ See you on cyberspace, Offray

Aug. 29, 2020

Re: [Pharo-users] Pharo at JPL

by tbrunz

JPL has its own Slack server... Of course I started a channel: <http://forum.world.st/file/t372161/jpl-slack-pharo-channel.png> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 28, 2020

Re: [Pharo-users] Image crashed, how can I restore the Playground?

by Offray Vladimir Luna CÃ¡rdenas

Hi Davide, You can use Grafoscopio[1] to store and structure your playgrounds as an interactive notebook. [1] https://mutabit.com/grafoscopio/en.html Your notebooks can combine prose and be exported to other formats (Markdown, HTML and PDF). Also, you can use your preferred source control system to store the notebooks. For example, I use Grafoscopio notebooks and Fossil[2] repositories to make workshop interactive notes. [2] https://fossil-scm.org/ I'm still debugging an annoying issue with keystroke capturing in playgrounds. But Grafoscopio notebooks has been a good bridge between coding and scripting for our local community and a great help in workshops. Hope that helps, Offray On 26/08/20 2:33 p.Â m., Davide Varvello via Pharo-users wrote: > Thanks StÃ©ph, > I guess the right directory is {imageDirectory}/pharo-local/play-cache/ > there are some .ph files representing several playgrounds. > > One further question: it seems to me there isn't a history of the > playground, right? So if I make multiple changes to a single playground, > they are lost. > > Cheers > Davide

Aug. 28, 2020