December 2022 - Pharo-users

Creating tiny Pharo images

by erik.stel＠gmail.com

Hi all.\ \ I have created a bootstrap helper package to create tiny Pharo images. I use this for CodeParadise, but it can also be used to create tiny images which run outside the browser. It can create both 32 and 64 bit images. A tiny image is around 200 to 300Kb.\ \ Two example usages are present. See the README in the repo.\ \ [https://github.com/ErikOnBike/TinyBootstrap](https://github.com/ErikOnBike/… "https://github.com/ErikOnBike/TinyBootstrap")\ \ Happy 2023 and happy Smalltalking!

Dec. 31, 2022

[ANN] PI version 0.7

by HernÃ¡n Morales Durand

Hello "PI", which stands for "Pharo Install", is a command line interface (CLI) to query and install Pharo packages: https://github.com/hernanmd/pi. With PI you can install Pharo packages in a unix-like shell command line interface. For example: $ pi install ISO3166 To get your repository listed with the "pi list" command, just tag your GitHub repository with "pharo". If there are multiple repositories with the same name, you can disambiguate specifying the repository owner: $ pi install user-name/repository-name Please let me know if this tool is also useful to you; and do not hesitate to ask a question that might appear using pi. Enjoy, HernÃ¡n

Dec. 30, 2022

CodeParadise runs on P10

by erik.stel＠gmail.com

Hi all. A small holiday present for anyone interested: [https://github.com/ErikOnBike/CodeParadise](https://github.com/ErikOnBike/C… "https://github.com/ErikOnBike/CodeParadise") now runs on P10 (and P11 with some care)! If you are using it on P8, please unload the CP-ClientEnvironment and reload it using the "pharo8" branch: ``` Metacello new repository: 'github://ErikOnBike/CP-ClientEnvironment:pharo8'; baseline: 'CodeParadise'; load. ``` P11 seems to have some issues sometimes with restarting the image. Have not found the exact cause. Will look into this.\ \ Happy holidays!

Dec. 28, 2022

Polyphemus VMIL talk

by Pierre Misse-Chanabier

Hello, I'm quite proud to provide my presentation for the VMIL talk I did on Polyphemus https://www.youtube.com/watch?v=-phxX8ia630. Hope this may be of interest to some of you ! Feel free to ping me for questions :) Cheers ! On 16/08/2022 10:36, pmissech wrote: > Hello, > > Although i will not be able to attend ESUG'22, a friend agreed to > present one of our projects to the innovation award. > **Polyphemus** is aÂ VM related, but public aims at any kind of > developers. > Particularly, the video submission talks about how to look at an image > and how to **recover** dead images. > Feel free to contact me if you have any questions ! > Enjoy (and vote for Polyphemus!). > > 5 minutes video, Innovation Technology Award submission: > https://youtu.be/zf3cCtNW830 > Repository: github.com/hogoww/Polyphemus/ > Additionnal information on image recovery: > https://github.com/hogoww/Polyphemus/blob/main/Documentation/ResurrectingDe… > > Cheers !

Dec. 27, 2022

ANSI instance creation methods for RunArray

by Richard O'Keefe

Here's a teeny tiny Christmas present: ANSI-compatible instance creation methods for RunArray.

Dec. 24, 2022

UK Smalltalk User Group meeting - 28 December 2022

by Giovanni Corriga

For the UKSTUG 2023 holiday meeting, Simberon's David Buck will present Beagle Smalltalk. Over the past 8 years, David has been developing a Smalltalk virtual machine. He used it to release two Smalltalk Games written in VisualWorks to run on Andriod and iPhone devices. More recently, he's re-written the VM to use its own bytecode set and written his own Smalltalk compiler to make it a stand-alone Smalltalk environment called Beagle Smalltalk named after the ship that took Darwin on his voyage of discovery. David plans to release this as an open-source Smalltalk to help and encourage kids to explore the world of programming. In this talk, David presents the current status of the project and where he hopes to go with it. David Buck is the president of Simberon ( http://simberon.com/ ) - a company that has been providing Smalltalk training and consulting for over 25 years. Along with James Robertson, David produced the Industry Misinterpretations podcast and later the Smalltalk Reflections podcast with Craig Latta. David remains a Smalltalk enthusiast and works to spread the word about Smalltalk. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/290409453/ ) to receive the meeting details.

Dec. 19, 2022

This week (50/2022) on the Pharo Issue Tracker

by Marcus Denker

This week, we merged 19 PRs, we closed 36 issues on the main issue tracker. Features ======== - Fix 12044 introduces hexString and related tests #12045 https://github.com/pharo-project/pharo/pull/12045 Blocks ====== - Enable Constant Block Compilation by default #11931 https://github.com/pharo-project/pharo/pull/11931 - 11984-CompiledBlockhasMethodReturn-is-not-a-good-name #12020 https://github.com/pharo-project/pharo/pull/12020 - 11965-Implement-ContextactiveHome-without-using-home #12063 https://github.com/pharo-project/pharo/pull/12063 - 12014-HECompiledBlockvalue-send-non-exiting-selector-encoderClassName #12070 https://github.com/pharo-project/pharo/pull/12070 - 12034-Context-we-have-both-home-and-methodReturnContext #12098 https://github.com/pharo-project/pharo/pull/12098 - Context: unify #selector and #methodSelector #12100 https://github.com/pharo-project/pharo/pull/12100 Fixes ===== - 12066-CI-test-failing-on-CI-SystemDependenciesTesttestExternalBasicToolsDependencies #12073 https://github.com/pharo-project/pharo/pull/12073 - Add missing keyDown: message in FTSearchFunction #12087 https://github.com/pharo-project/pharo/pull/12087 - Fix: #12089 the metaclass was placing one # while it should not! + adâ¦ #12090 https://github.com/pharo-project/pharo/pull/12090 - Fix class editor not refreshing when switching between class/instance sides #12095 https://github.com/pharo-project/pharo/pull/12095 - 12110-ReAbstractCritique-asModalWindow #12111 https://github.com/pharo-project/pharo/pull/12111 - Debugger-Implementors-Of #1337 https://github.com/pharo-spec/Spec/pull/1337 - Fix Filetree to Tonel transformation #1646 https://github.com/pharo-vcs/iceberg/pull/1646 - Introduce input validation as first precondition of a refactoring #12050 https://github.com/pharo-project/pharo/pull/12050 Cleanups ======== - merge ReAssignmentWithoutEffectRule and ReRemoveAssignmentWithoutEffectRule #12071 https://github.com/pharo-project/pharo/pull/12071 - Factorize the list of VM parameters #12072 https://github.com/pharo-project/pharo/pull/12072 - Cleanup: lint cleanup regarding class side #initialize categorization for Metacello classes #12076 https://github.com/pharo-project/pharo/pull/12076 - Small lint issue in Athens cairo tests #12092 https://github.com/pharo-project/pharo/pull/12092 - Cleanup: Fix typo in DailyNonInteractiveTranscript>>#initializeStream #12094 https://github.com/pharo-project/pharo/pull/12094

Dec. 16, 2022

Re: Mardeep as a format to (re)publish and exchange Pharo powered data narratives, lesson and book(let)s

by PAUL DEBRUICKER

Nice write up > On Dec 13, 2022, at 3:15 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > As I told in a previous message, we, at the Grafoscopio[1][1a][1b] community, are migrating some lessons learned since 2015 to the new capabilities available since last year via Lepiter[2]. And one of such lessons is the use of human friendly data formats for exchanging and publishing data narratives. > > [1] https://mutabit.com/grafoscopio/en.html > [1a] https://mutabit.com/repos.fossil/grafoscopio/doc/tip/intro.md > [1b] https://mutabit.com/repos.fossil/grafoscopio/doc/tip/readme.md.html > [2] https://lepiter.io/feenk/introducing-lepiter--knowledge-management--e2p6apq… > > Originally, in Grafoscopio, we made this friendly format by embedding Markdown inside STON, as shown in the Grafoscopio Manual (PDF[3], source code [3a]) and now we are flipping the strategy: embedding STON metadata in Mardeep[4]/Markdown, which allows us to exchange and publish Pharo powered data narratives, lessons and book(let)s in a pretty light format as shown by the republication of the "PetitParser: Building Modular Parsers" chapter (18th )from the Deep into Pharo book[4] as a Markdeep data narrative[4a]. The chapter was rewritten in Lepiter and can be exported/imported to/from Markdeep, so new updates or learning notes can be created pretty easily[4b]. Because we combine this with Fossil SCM[5], it is also possible to have the history of the documents (look at [4a1][4b1]) in a self contained environment for collaborative publishing/writing that is easier to use, in comparison with Git based alternatives (as shown in our practices introducing this tools and workflows to non-programmers). > > [3] https://mutabit.com/repos.fossil/grafoscopio/uv/Docs/En/Books/Manual/manual… > [3a] https://mutabit.com/repos.fossil/grafoscopio/file?name=Docs/En/Books/Manual… > [4] http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf > [4a] http://mutabit.com/repos.fossil/mutabit/doc/tip/wiki/en/petitparser-buildin… > [4b] http://mutabit.com/repos.fossil/mutabit/doc/tip/wiki/en/petitparser-buildin… > [4a1] http://mutabit.com/repos.fossil/mutabit/timeline?uf=1680c3899 > [4b1] http://mutabit.com/repos.fossil/mutabit/finfo?name=wiki/en/petitparser-buil… > [5] https://fossil-scm.org/ > > I like the results with so far with this light (re)publishing workflow based in Markdeep, despite some bugs, like subsection numbering done in Markdeep when combined with HTML divs[6] (a bug already reported to the author). For more detailed control of the output or the combination with HTML graphical libraries, like Apache Echarts, we're testing a similar strategy using Pandoc's Markdown with promising features. For example, we can have interactive snippets in the HTML exported document [6a]. > > [6] https://nitter.net/offrayLC/status/1585701931728740352#m > [6a] https://twitter.com/offrayLC/status/1555229528355651586 > > Such light, human readable and diff friendly publishing and exchange formats are kind of a dehydrated data narrative for the web and/or the file-system than can be re-hydrated back into a full Pharo/GToolkit image for total interactivity/moldability and meanwhile you can tease the casual web reader/explorer with data stories and visualizations without s/he having the need to have Pharo/GToolkit in her/his machine. > > Cheers and thanks for the community and technologies that make this possible. I will be posting more advances as they come. > > Offray

Dec. 15, 2022

Re: [Pharo-dev] Pharo VM Release - v9.0.21

by Stewart MacLean

Hi Pablo, I'm on Pharo 10 and intermittently experience "the spinning wheel" when making LibC calls. The spin dump is below. I'm wondering if the last fix: - Allocating the opcodes and fixup structs only once and reusing them (Reducing risk of C Stack Overflow)) would potentially rectify this? Thanks to you and the whole team for all the great work on the machine! Stewart Thread 0x9a54d 1000 samples (1-1000) priority 46 (base 46) 1000 ??? [0x1062e1a78] 1000 ??? [0x1063c2374] 1000 ??? [0x1062e1ab8] 1000 ??? [0x10637a0e0] 1000 ??? [0x10637a324] 1000 ??? [0x1062e27f4] 1000 ??? [0x10637763c] 1000 ??? [0x1062e070c] 1000 ceStackOverflow + 196 (libPharoVMCore.dylib + 451716) [0x10453a484] 1000 checkForEventsMayContextSwitch + 828 (libPharoVMCore.dylib + 430696) [0x104535268] 1000 ioProcessEvents + 16 (libPharoVMCore.dylib + 25800) [0x1044d24c8] 1000 aioPoll + 80 (libPharoVMCore.dylib + 788412) [0x10458c7bc] 1000 _sigtramp + 56 (libsystem_platform.dylib + 17636) [0x1a20a84e4] 1000 handleSignal + 80 (libUnixOSProcessPlugin.dylib + 46264) [0x11cf674b8] 1000 signalSemaphoreWithIndex + 264 (libPharoVMCore.dylib + 786524) [0x10458c05c] 1000 aioInterruptPoll + 104 (libPharoVMCore.dylib + 789424) [0x10458cbb0] 1000 platform_semaphore_wait + 20 (libPharoVMCore.dylib + 36804) [0x1044d4fc4] 1000 _dispatch_semaphore_wait_slow + 132 (libdispatch.dylib + 18420) [0x1a1ed37f4] 1000 <patched truncated backtrace> 1000 semaphore_wait_trap + 8 (libsystem_kernel.dylib + 6544) [0x1a2055990] *1000 ??? (kernel.release.t8101 + 575116) [0xfffffe000799868c] On Tue, Dec 13, 2022 at 2:30 AM tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Hello, > I have released a new version of the Pharo VM for Pharo 9, Pharo 10 and > Pharo 11. This VM is accessible right now from Zero-Conf, updating it in > the Pharo Launcher or using the usual downloads (as described in > pharo.org/download) > > This version includes a series of bug fixes and upgrades on the > third-party libraries. > > Changelog: > > - Implementing High resolution clock for ARM64 (Used during profiling) > - Updating third party libraries for all the graphic layer. > - Fixing a performance regression on the allocation of opcodes and fix-ups. > Cleaning only the ones that are going to be used. > Like this, this version has the same speed than before when > allocating in the stack. > - Correctly handling the encoding of the command line arguments of the VM > (Windows) > - Allocating the opcodes and fixup structs only once and reusing them > (Reducing risk of C Stack Overflow) > > Thanks a lot, and any doubt please let me know. > Cheers, > > Pablo on behalf of the whole Pharo team. > > -- > Pablo Tesone. > tesonep(a)gmail.com >

Dec. 14, 2022

[Issue Tracker] Please check your issues

by Marcus Denker

Hi, The issue tracker has a bit the problem that outdated issues are never cleaned - sometimes PRs are merged but the issue is not closed because it was never connected to the PR ( github sometimes just does not do it correctly ) - Duplicated reports, bug is fixed but the other issue was closed - Problem fixed due to other reasons Or your issue might have seen someone asking a question. People tend to just wait for an answer to those. Or maybe the issue has just not enough information for others to take action? Maybe you could submit a PR instead of just describing the change you think should be done? The best would be if everyone who opened an issue would check all the issues they submitted. you can just add a filter to https://github.com/pharo-project/pharo/issues, e.g. author:MarcusDenker shows you all that I submitted Marcus

Dec. 14, 2022