December 2020 - Pharo-users

[Video] Transforming code using RewriteToolsSet

by Sebastian Jordan

Hi, If you are interested in applying custom code transformations on a selected set of classes, maybe this tool will be of your interest. I made these mini-tutorial-videos in which I transform the code of a set of classes through a transformation rule using this brand new tool RewriteToolsSet. Thanks! [GitHub's repo: https://github.com/jordanmontt/RewriteToolsSet] - https://www.youtube.com/watch?v=M0ElVhUoWXk - https://www.youtube.com/watch?v=_9v1XTk1J2A [https://www.bing.com/th?id=OVF.rbOc4EaCst%2fncgXkMaTwHA&pid=Api]<https://www.youtube.com/watch?v=M0ElVhUoWXk> Transforming code using RewriteToolsSet<https://www.youtube.com/watch?v=M0ElVhUoWXk> In this video we are going to see another common use case of this set of tools. We are going to reactor the code of all classes of a package using a transformation rule. If you have any question or experience any bug, please do not hesitate open an issue on the GitHub page or contact me. Thank you for you time! GitHub's repository: https ... www.youtube.com

Dec. 2, 2020

Re: [Pharo Mooc] Change colors of test results

by sergio ruiz

ah! i just saw this. thanks for the help.. > On Nov 19, 2020, at 2:20 AM, hogoww <pierre.misse-chanabier(a)inria.fr> wrote: > > The only other way I found would be to recreate the object, but I'm not comfortable enough with UI stuff to help you more than that :/ ---- peace, sergio photographer, journalist, visionary Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV @sergio_101@mastodon.social https://sergio101.com http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Dec. 2, 2020

Re: SmalltalkCI / Github Actions

by Gabriel Cotelli

Take a look at https://github.com/ba-st/Buoy/blob/release-candidate/.github/workflows/buil… On Tue, Dec 1, 2020, 13:18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I have a question and I could not find the answer in the SmalltalkCI doc > I would like to run my tests on different versions of Pharo > I know how to do it in travis but in GA I missed it. > > I read > https://github.com/marketplace/actions/setup-smalltalkci > and tutorials on the net about GA > > So I tried > > name: test > env: > GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} > on: > push: > branches: > - master > jobs: > build: > strategy: > fail-fast: false > matrix: > platform: [ubuntu-latest, macos-latest ] > pharoversion: [Pharo64-8.0, Pharo64-9.0] > runs-on: ${{ matrix.platform }} > steps: > - uses: actions/checkout@v2 > - uses: hpi-swa/setup-smalltalkCI@v1 > id: smalltalkci > with: > smalltalk-version: pharoversion > - run: smalltalkci -s ${{ steps.smalltalkci.outputs.pharoversion }} > shell: bash > timeout-minutes: 15 > > > but it failed. > I do not know how to specify the version of Pharo64-8.0 on mac. > > S. > > -------------------------------------------- > 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 > >

Dec. 1, 2020

SmalltalkCI / Github Actions

by StÃ©phane Ducasse

Hi I have a question and I could not find the answer in the SmalltalkCI doc I would like to run my tests on different versions of Pharo I know how to do it in travis but in GA I missed it. I read https://github.com/marketplace/actions/setup-smalltalkci and tutorials on the net about GA So I tried name: test env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} on: push: branches: - master jobs: build: strategy: fail-fast: false matrix: platform: [ubuntu-latest, macos-latest ] pharoversion: [Pharo64-8.0, Pharo64-9.0] runs-on: ${{ matrix.platform }} steps: - uses: actions/checkout@v2 - uses: hpi-swa/setup-smalltalkCI@v1 id: smalltalkci with: smalltalk-version: pharoversion - run: smalltalkci -s ${{ steps.smalltalkci.outputs.pharoversion }} shell: bash timeout-minutes: 15 but it failed. I do not know how to specify the version of Pharo64-8.0 on mac. S. -------------------------------------------- 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

Dec. 1, 2020

Re: (Re)storing code blocks from text strings (hopefully in STON)

by Offray Vladimir Luna CÃ¡rdenas

Hi Sven, Thanks for your swift and useful response as usual and yes, not only it helps a lot but teach too (as usual with your answers). I will be dealing with some bureaucratic last minute, hard deadline notification I just got yesterday from my university (following local "tradition" in public institutions of total disregard of everybody's schedule and time)... Anyway, I will be having opportunity to test your suggestions until next week, after deadline. I understand the concerns about not serializing code blocks. So far they have not been a necessity for me (as code snippets are stored as "playground trees" in the Grafoscopio notebooks), but I would like to explore this approach before considering something more complex (like Metacello/Iceberg packages for the Brea web themes). I have been using some minor modifications on objects to serialize them, mainly to store playground contents as strings, and they have worked fine until now, but I was learning all along the way and they could be just a not good practice from my file scripting times/needs. Cheers, Offray On 1/12/20 4:54 a.Â m., Sven Van Caekenberghe wrote: > Hi Offray, > > This is a recurring question. BlockClosures are way too general and powerful to be serialised. That is why serialising BlockClosures is not supported in STON. > > The code inside a block can refer to and even affect state outside the block. Furthermore the return operator is quite special as it returns from some outer context. > > A subset of BlockClosures are those that are clean. These do not close over other variables, nor do they contain a return. By using their source code representation, it is possible to serialise/materialise them. > > You can try this by adding the following methods: > > BlockClosure>>#stonOn: stonWriter > self isClean > ifTrue: [ stonWriter writeObject: self listSingleton: self printString ] > ifFalse: [ stonWriter error: 'Only clean blocks can be serialized' ] > > BlockClosure>>#stonContainSubObjects > ^ false > > BlockClosure class>>#fromSton: stonReader > ^ self compilerClass new > source: stonReader parseListSingleton; > evaluate > > With these additions you can do the following: > > STON fromString: (STON toString: [ :x :y | x + y ]). > > Note that the actual class name depends on the Pharo version (BlockClosure in Pharo 7, FullBlockClosure in Pharo 9 and maybe soon CleanBlockClosure - Marcus is working on that last one and that would be very cool because it would say exactly what it it). > > I am still not 100% convinced to add this as a standard feature to STON. Using source code fully exposes the implementation, while using the compiler can be dangerous. It also adds a dependency on source code and the compiler. But it would be good if people can experiment with this feature. > > Does this help you ? > > Regards, > > Sven > > PS: I would not modify an object just to serialise it. > >> On 30 Nov 2020, at 18:19, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Hi, >> >> I'm using STON for all my light storage serialization needs, like the >> Grafoscopio notebooks, and I also love it, as Russ stated in their mail >> question, and I share with him a similar request: for my Brea[1] static >> site generator I would like to store some BreaQuery objects as external >> STON files, and recover them, so I can run the queries that >> recreate/update the website easily. I could store them as Grafoscopio >> notebooks, but I don't want to make Grafoscopio a prerequisite for Brea >> or I could use Fuel, but I would like to store queries as a diff >> friendly text based format. I have considered Metacello/Iceberg packages >> to export code in a diff friendly format, but It maybe overkill. So I >> would like to see if STON can serve me here too. >> >> [1] https://mutabit.com/repos.fossil/brea/ >> [2] https://mutabit.com/repos.fossil/indieweb/ >> >> So far, I'm able to serialize a code block as a string using: >> >> BreaQuery>>asStonModified >> self codeBlock: self codeBlock asString >> ^ STON toStringPretty: self >> >> But I'm unable to populate a block from a string. There is any way to >> make a string, lets say 'a + b', to become the code contents of a block, >> ie: [a + b ] ? >> >> Thanks, >> >> Offray >>

Dec. 1, 2020

Re: (Re)storing code blocks from text strings (hopefully in STON)

by Sven Van Caekenberghe

Hi Offray, This is a recurring question. BlockClosures are way too general and powerful to be serialised. That is why serialising BlockClosures is not supported in STON. The code inside a block can refer to and even affect state outside the block. Furthermore the return operator is quite special as it returns from some outer context. A subset of BlockClosures are those that are clean. These do not close over other variables, nor do they contain a return. By using their source code representation, it is possible to serialise/materialise them. You can try this by adding the following methods: BlockClosure>>#stonOn: stonWriter self isClean ifTrue: [ stonWriter writeObject: self listSingleton: self printString ] ifFalse: [ stonWriter error: 'Only clean blocks can be serialized' ] BlockClosure>>#stonContainSubObjects ^ false BlockClosure class>>#fromSton: stonReader ^ self compilerClass new source: stonReader parseListSingleton; evaluate With these additions you can do the following: STON fromString: (STON toString: [ :x :y | x + y ]). Note that the actual class name depends on the Pharo version (BlockClosure in Pharo 7, FullBlockClosure in Pharo 9 and maybe soon CleanBlockClosure - Marcus is working on that last one and that would be very cool because it would say exactly what it it). I am still not 100% convinced to add this as a standard feature to STON. Using source code fully exposes the implementation, while using the compiler can be dangerous. It also adds a dependency on source code and the compiler. But it would be good if people can experiment with this feature. Does this help you ? Regards, Sven PS: I would not modify an object just to serialise it. > On 30 Nov 2020, at 18:19, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > I'm using STON for all my light storage serialization needs, like the > Grafoscopio notebooks, and I also love it, as Russ stated in their mail > question, and I share with him a similar request: for my Brea[1] static > site generator I would like to store some BreaQuery objects as external > STON files, and recover them, so I can run the queries that > recreate/update the website easily. I could store them as Grafoscopio > notebooks, but I don't want to make Grafoscopio a prerequisite for Brea > or I could use Fuel, but I would like to store queries as a diff > friendly text based format. I have considered Metacello/Iceberg packages > to export code in a diff friendly format, but It maybe overkill. So I > would like to see if STON can serve me here too. > > [1] https://mutabit.com/repos.fossil/brea/ > [2] https://mutabit.com/repos.fossil/indieweb/ > > So far, I'm able to serialize a code block as a string using: > > BreaQuery>>asStonModified > self codeBlock: self codeBlock asString > ^ STON toStringPretty: self > > But I'm unable to populate a block from a string. There is any way to > make a string, lets say 'a + b', to become the code contents of a block, > ie: [a + b ] ? > > Thanks, > > Offray >

Dec. 1, 2020

Re: [Important] The deprecated FileStream removed from Pharo 9

by Guillermo Polito

Thanks Pavel! Just to note, these packages have been deprecated since at least 2018, as Pavelâs blogpost shows :). So it was time to clean up a bit. Please do not hesitate to open an entry in the issue tracker if you find problems, we will solve them ASAP. G. > El 1 dic 2020, a las 9:20, Pavel Krivanek <pavel.krivanek(a)gmail.com> escribiÃ³: > > Hi, > > the Pharo 9 finally removed the DeprecatedFileStream package. Please, check whether your projects stopped to use this deprecated file streams API. > > The migration guide is in the FileStream class comment. > > or here: https://pharoweekly.wordpress.com/2018/03/19/new-files-in-pharo-migration-g… <https://pharoweekly.wordpress.com/2018/03/19/new-files-in-pharo-migration-g…> > > or here: https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD <https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD> > > Cheers, > -- Pavel

Dec. 1, 2020

[Important] The deprecated FileStream removed from Pharo 9

by Pavel Krivanek

Hi, the Pharo 9 finally removed the DeprecatedFileStream package. Please, check whether your projects stopped to use this deprecated file streams API. The migration guide is in the FileStream class comment. or here: https://pharoweekly.wordpress.com/2018/03/19/new-files-in-pharo-migration-g… or here: https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD Cheers, -- Pavel

Dec. 1, 2020