- Pharo-users - lists.pharo.org

IMac Pharo?

by Richard O'Keefe

Iâve been given an imac desktop. It is some kind of PowrrPC running OSX Leopard. Works beautifully but too old to update, and no deceloper tools. I donât suppose thereâs an okd version of Pharo that would run on it?

March 20, 2026

Re: PharoSmalltalk in Apple app store for iPad

by Aaron Wohl

Corrected Apple App Store link (or search PharoSmalltalk): https://apps.apple.com/us/app/pharosmalltalk/id6759073615 ----- Original message ----- From: Aaron Wohl via Pharo-users <pharo-users(a)lists.pharo.org> To: pharo-users(a)lists.pharo.org, squeak-dev(a)lists.squeakfoundation.org Cc: Aaron Wohl <xphu(a)awohl.com> Subject: [Pharo-users] PharoSmalltalk in Apple app store for iPad Date: Thursday, March 19, 2026 4:33 PM PharoSmalltalk is available in the Apple App Store for iPad (primary), iPhone, and Mac as https://apps.apple.com/us/app/pharosmalltalk/id6759073615/PharoSmalltalk It uses a new VM with no JIT (iPad forbids JIT) and small objects encoded in the low bits of pointers rather than in the high bits, due to Apple ASLR restrictions. Many thanks to Tim Mackinnon for over 111 emails and trying 98 test builds. Source https://github.com/avwohl/iospharo Note that I have a strong background in compilers, not Smalltalk. If it does something wrong, please let me know at https://github.com/avwohl/iospharo/issues

March 19, 2026

PharoSmalltalk in Apple app store for iPad

by Aaron Wohl

PharoSmalltalk is available in the Apple App Store for iPad (primary), iPhone, and Mac as https://apps.apple.com/us/app/pharosmalltalk/id6759073615/PharoSmalltalk It uses a new VM with no JIT (iPad forbids JIT) and small objects encoded in the low bits of pointers rather than in the high bits, due to Apple ASLR restrictions. Many thanks to Tim Mackinnon for over 111 emails and trying 98 test builds. Source https://github.com/avwohl/iospharo Note that I have a strong background in compilers, not Smalltalk. If it does something wrong, please let me know at https://github.com/avwohl/iospharo/issues

March 19, 2026

AI Web access - and Pharo works...

by Kasper Osterbye

Cheers I wanted to make parts of Pharo accessible from AI APP chat, and for that I needed Teapot. But I ran into an other issue. That is now on Github https://github.com/kasperosterbye/AI-Experiments/blob/main/experiments/2026… One issue understood, now only 219 confusions left. -- Kasper

March 19, 2026

UKSTUG Meeting: The VAST Platform AI Assistant: Integrating LLMs into a Live Smalltalk Environment - 25 March 2026

by UK Smalltalk

Smalltalk environments have long been pioneers in developer productivity. With the VAST Platform AI Assistant, Instantiations is extending that tradition by integrating Large Language Models (LLMs) directly into the VAST platform. This new tool is designed to bring AI capabilities directly into your daily workflow. In this session, Johan, Kris, and Mariano will share a user experience report and a live demonstration of the assistantâs current capabilities, powered by Googleâs Gemini. Youâll see how it goes beyond simple chat by directly interacting with the live VAST image through the LLMâs âtoolsâ capabilities. This allows investigating source code as it responds to your questions. These examples will demonstrate how the VAST Platform AI Assistant leverages the live nature of Smalltalk to act as a true pair programmer. Weâll also look ahead at our enterprise-focused roadmap, including support for local models to ensure privacy and security, integration with additional LLM providers, and our vision for deeper IDE-level capabilities and Runtime Intelligence. Join us to explore how we are shaping the future of AI-assisted development in VAST to better empower software developers. See it in action, try it out, and join the conversation on GitHub ( https://github.com/instantiations/VAST-Platform-AI-Assistant ). Johan Brichau ( https://be.linkedin.com/in/johanbrichau ) is a seasoned software engineer with over 25 years of experience across a wide range of Smalltalk environments. He joined the VAST Platform development team at Instantiations in January 2025. Prior to that, he spent nearly 15 years as co-founder and CTO of Yesplan, a world-leading online venue management platform. Johan holds a PhD in computer science from the Vrije Universiteit Brussel (2005) and has actively contributed to several open source projects. Kris Gybels recently joined Instantiations to work on the VAST Platformâs AI-based tool support. He previously spent a number of years in academia researching Declarative Meta Programming and its application to Aspect-Oriented Programming, and over a decade co-developing the Yesplan venue management system, during which he made a number of contributions to Pharo, most notably Pharo 12âs improved Mac âRetina displayâ support, as well as to Seaside and its Parasol web testing framework. Mariano Martinez Peck ( https://ar.linkedin.com/in/mariano-martinez-peck ) is a systems engineer specializing in dynamic programming language software. In 2018, he joined Instantiations to further develop the VAST Platform through the addition of new frameworks, libraries and tools, as well as improving the existing code base of VAST. He is active in the Smalltalk development community, and has used his expertise to co-author numerous open source projects. Mariano has a PhD in Computer Science, and his academic research has been published across various international journals. In addition to his development duties, he currently leads the VAST Platform engineering team at Instantiations. In his personal time, Mariano enjoys traveling as well as outdoor activities like camping and fishing. This will be an online meeting. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/313492185/ ) to receive the meeting details.

March 18, 2026

"Steps for Interaction with Spec Presenters in Hera â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, I posted a third article in the series about describing Spec application behaviour with Hera. The first post explained how Hera manages open Spec windows. The second post explained how Hera identifies presenters so they can be referenced in Gherkin scenarios. This post explains how Hera expresses steps to interact with Spec presenters. https://all-objects-all-the-time.st/#/blog/posts/22 As always, all feedback is welcome. Happy reading! Ciao, Koen

March 14, 2026

[ANN] Soil version 4

by Norbert Hartl

We are happy to announce the availability of Soil version 4. What is new? Indexes (both skip list and Btree+) now have forward and backward pointer (those have been added) so there is new possibilities to have indexes that are traversable in each direction. This needed to be done in a not backward-compatible way. All databases prior to v4 need to be migrated. A migration procedure is available at https://github.com/ApptiveGrid/Soil/blob/main/docs/versions/migration.md The indexes prior to v4 have been implemented closely to the interface and behavior of a Dictionary. We've added support for duplicated keys which is necessary when doing secondary indexes. A lot of the changes in v4 are regarding to that because it changed quite a bit how things work. NOTE: duplicate keys are considered a preview in v4. They should be usable but might need to settle a bit more. Until now there is no feature supported making use of duplicated keys. Indexes have unique keys as default. They resemble the old behavior and should just work as before journals are now used by a transaction right from the start and creates it while the code operates on it. This way we could remove all brittle intermediate dictionaries like newValues, removedValues in the handling which improved the code a lot There is a first version of read-only transactions where one can make sure every attempt to write to the database should end up in an error There is also a first version of a graph exporter and importer. This can export a graph on the database level which works even if the application code is not present. This is useful for copying or moving a sub-graph from one database to another in an efficient way. There are plenty of code cleanups and performance improvements. The more detailled view can be seen here: https://github.com/ApptiveGrid/Soil/blob/main/docs/versions/changelog-v4.md What is planned for v5? Multi-index collection. This resembles what most other database have. You have one list of objects but multiple indexes to the same data in order to speed up search for different use cases partial indexes. These is a special kind of view to a database index. It consists of a predicate and stores only the elements that pass the predicate. Searching is way faster and things like size are almost for free windows support. There has been a PR provided https://github.com/ApptiveGrid/Soil/pull/980 which needs to be fixed as the way soil handles streams is not compatible with windows If all goes well we will remove the need for the markDirty: calls completely. Cluster modification tracking will then be automatic and removes a huge annoyance when using soil Hope you like it. Give it a spin and then tell us! Norbert & Marcus

March 12, 2026

Fwd: New releases: Bloc:v2.8.0, Toplo:v0.9.0 and more

by stephane ducasse

> Begin forwarded message: > > From: LABORDE Pierre <pierre.laborde(a)fr.thalesgroup.com> > Subject: RE: New releases: Bloc:v2.8.0, Toplo:v0.9.0 and more > Date: 12 March 2026 at 09:27:11 CET > To: MartÃn Dias <tinchodias(a)gmail.com>, lse-openbloc <lse-openbloc(a)inria.fr> > Reply-To: LABORDE Pierre <pierre.laborde(a)fr.thalesgroup.com> > > De : lse-openbloc-request(a)inria.fr <mailto:lse-openbloc-request@inria.fr> <lse-openbloc-request(a)inria.fr <mailto:lse-openbloc-request@inria.fr>> De la part de MartÃn Dias > EnvoyÃ© : jeudi 12 mars 2026 02:01 > Ã : lse-openbloc <lse-openbloc(a)inria.fr <mailto:lse-openbloc@inria.fr>> > Objet : New releases: Bloc:v2.8.0, Toplo:v0.9.0 and more > > Hello! the following are the new releases in Bloc/Toplo projects: > > Bloc v2.8.0 <https://github.com/pharo-graphics/Bloc/releases/tag/v2.8.0> > â¢ Fix code styling error in Pharo 14 by @tinchodias in #839 > â¢ Move TBlLayoutResizable to Bloc-Layouts-Support package by @plantec in #834 > â¢ Fix deprecated message send by @tinchodias in #845 > â¢ Send #waitTimeoutMilliseconds: instead of #wait: to Semaphore by @tinchodias in #847 > â¢ Generate baseline with explicit requirements to avoid loading warnings by @tinchodias in #832 > > Toplo v0.9.0 <https://github.com/pharo-graphics/Toplo/releases/tag/v0.9.0> > â¢ Circular menu by @plantec in #368 > â¢ List hierarchy refactoring by @plantec in #360 > â¢ Move defaultNodeFactory to the root abtract class by @plantec in #358 > â¢ Finite data source manager ng by @plantec in #362 > â¢ Simplified node configuration by @plantec in #363 > â¢ List node configuration by @plantec in #365 > â¢ Checkbox selection refactoring by @plantec in #366 > â¢ Improved ToInfiniteListElementEventHandler to fixe selection update iâ¦ by @plantec in #367 > â¢ Make #class: and #iconImageFor: on ToExMiniBrowserClassNodeContent use the FormSet for each of the icons by @Rinzwind in #329 > â¢ Investigating list selection management by @plantec in #370 > â¢ Fix some circular dependencies by @tinchodias in #371 > > Spec-Toplo v0.9.0 <x-msg://28/Spec-Toplo/releases/tag/v0.9.0> > â¢ Diff adapter, begin miler layout, fix selection tree table by @badetitou in #46 > â¢ Improve Code Editor by @badetitou in #47 > â¢ Toplo file selector by @badetitou in #49 > â¢ Add keyshortcut to main window by @badetitou in #50 > â¢ Improve small aspect issue by @badetitou in #51 > â¢ Miller layout by @badetitou in #52 > â¢ Little cleanups by @tinchodias in #53 > â¢ Fix to do list demo by @tinchodias in #81 > â¢ Add a Spec adapter for SpBlocPresenter to the Morphic backend by @tinchodias in #83 > â¢ Load proper group of Roassal by @tinchodias in #86 > â¢ Load Roassal package not baseline by @tinchodias in #88 > > Alexandrie v2.8.0 <https://github.com/pharo-graphics/Alexandrie/releases/tag/v2.8.0> > â¢ Add binding for hb_version_atleast and use it by @tinchodias in #121 > â¢ Cairo context's #newContextDo: initialize the surface > > Album v0.9.0 <https://github.com/pharo-graphics/Albumv0.9.0> > â¢ Few changes needed by Toplo by @plantec in #54 > â¢ Add AlbEditorElement>>lineIndexAtTextIndex: by @plantec > â¢ fixes #infiniteDo: to return the result of the block > â¢ Remove TBlLayoutResizable uses since it is used by BlElement > â¢ The cursor was not blinking by default > > PharoSDL3 <https://github.com/pharo-graphics/PharoSDL3/releases/tag/v0.0.2> > 102 commits in 2026: https://github.com/pharo-graphics/PharoSDL3/compare/964543a2cd6ac278fd208c3… > > > Best regards, > MartÃn

March 12, 2026

Smalltalk Meetup in Zurich, 24 April 2026

by Peter Ursprung

Hi all, We are organizing the next Smalltalk Meetup in Zurich, Switzerland. It will be on Friday, 24 April 2026, starting at 18:00. We will meet in a meeting room where we will have short Smalltalk talks, then we will go to a nearby restaurant. If you are interested, please register by Friday, 17 April 2026, on this website: https://zurich.smalltalk.world We are still looking presentations: if you have something interesting to show, please mention it in the registration. Regards, Peter

March 4, 2026

Re: iPad Pharo test release

by Aaron Wohl

Claude has a code review mode. One of the phases does performace improvements. Also, CLAUDE has done comparisons with the timing of the full test suite on the Mac standard vm vs our vm. Some digital math factorial functions were missing. But after that, it all seems to come down to the lack of JIT. It hurts a lot. Claude suggested pre-compiling (at build time) all hotspots into C code. This would be part of a fake JIT. You could change the Smalltalk code, and it would invalidate the JIT and get slow. But only for that function. I suppose if you made a change to the Object, all JIT would be lost. But I haven't looked into it yet. There was also a suggestion to have a serious Smalltalk group petition Apple for a workaround to the JIT ban. Originaly Apple banned all code that can write code. But I recently published a Z80 CP/M emulator, and Apple had no problem with that. Although they did hold up the Mac version half a month due to a zork1 copyright inquiry (but the iPad with zork1 was fine). So Apple can loosen up and still be squirrely at the same time. ----- Original message ----- From: Tim Mackinnon <tim(a)testit.works> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>, Richard O'Keefe <raoknz(a)gmail.com> Cc: Aaron Wohl <xphu(a)awohl.com> Subject: Re: [Pharo-users] Re: iPad Pharo test release Date: Monday, March 02, 2026 5:21 AM Its worth adding to this, to set expectations - I have been testing on an iPhone 13 pro (so a few years old) and an iPad Pro 2nd Gen (from about the same time period). While the iPad has more CPU cores, the A15 bionic chip of the iPhone does run this better, and its a bit sluggish on the ipad and a bit nippier on the iPhone. If I change the Color Theme from the startup screen, both devices will pause for 15seconds or more while they process that - however things like code lookup or evaluating factorial, or dragging windows all are acceptable. An iPad 6 is 30-70% slower than my iPad pro, so I suspect it will work but be quite laggy without the jitter. Still its a worth a shot. I think that modern M series ipads will probably work quite well - and the lack of a jitter might not be a big impediment. It worth a shot, and maybe Claude might spot some interesting optimisations - its kind of amazing how its churning through my feedback to Aaron so far. Today its added useful toolbar icons and its starting to look like a viable part time coding environment - i'm quite stunned. Tim On Mon, 2 Mar 2026, at 12:53 AM, Aaron Wohl via Pharo-users wrote: > The motion code is not released yet. Probably tomorrow > > can you reasearch the earliest iPad and or iOS this will run on. a user writes ... > Here's the research summary: > > *iPad 6 (A1893) â Yes, it will work.* > > - iPad 6 has an A10 Fusion (arm64) and supports up to iPadOS 17 > - Our deployment target is iOS/iPadOS 15.0, so it's well within range > - It won't get iPadOS 18+, but iPadOS 17 is fine for us > > *Minimum* *supported* *devices* *(iOS* *15.0* *deployment* *target):* > > iPads: iPad 5th gen (2017) and newer, iPad Air 2 (2014), iPad mini 4 (2015) > iPhones: iPhone 6s / 6s Plus (2015), iPhone SE 1st gen (2016) > > *Storage* *requirements:* > > * * *App* *itself* *(debug* *build):* *~15* *MB* > * * *Pharo* *13* *image:* *~56* *MB* > * * *Pharo* *sources* *file:* *~43* *MB* > * * *Changes* *file:* *~20* *KB* > * * *TestFlight* *app:* *~30* *MB* *(from* *App* *Store)* > > Total: ~150 MB for everything > > So even a 32 GB iPad 6 has plenty of room. > > *Re:* *TestFlight* *instructions* â that's a good idea for the README. *Re:* *Core* *Motion* *binding* â that would be a fun Pharo FFI > project (accelerometer, gyroscope, compass on iPad). > > Want me to update the README with TestFlight install instructions? > ... > Added the following: > | data | â > â "Start motion updates" â > â <primitive: 'primitiveMotionStart' module: 'CoreMotionPlugin'>. â > â â > â "Read latest sample â Float64Array of 13 elements" â > â data := <primitive: 'primitiveMotionData' module: 'CoreMotionPlugin'>. â > â "Elements: accelX,Y,Z (1-3), gyroX,Y,Z (4-6), magX,Y,Z (7-9), â > â roll,pitch,yaw (10-12), timestamp (13)" â > â â > â "Stop updates" â > â <primitive: 'primitiveMotionStop' module: 'CoreMotionPlugin'>. â > > ----- Original message ----- > From: Richard O'Keefe <raoknz(a)gmail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: Aaron Wohl <xphu(a)awohl.com> > Subject: Re: [Pharo-users] iPad Pharo test release > Date: Sunday, March 01, 2026 7:10 PM > > I have an iPad 6 (model A1893 if anyone cares). > Will Pharo run on that device? > How much storage do I need to install Pharo on this iPad? > (And TestFlight itself.) > I've never heard of the test store before; could the README in GitHub > be extended with instructions about how to install the beta? > > If you had infinite time and I had money to pay for it ... > it would be nice to have a binding for Core Motion. > But having Pharo on the iPad? Huge thanks. > > On Thu, 26 Feb 2026 at 02:19, Aaron Wohl via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> Pharo 13 for iPad in the test Apple Store (open in the Apple TestFlight app); >> Phone or Mac https://testflight.apple.com/join/kGmPQFr9 >> Due to Appleâs no JIT, it's not snappy. But maybe it's still useful? >> Source https://github.com/avwohl/iospharo about 100K lines of new source code. >> >> This is my first venture into using Pharo. I could use advice on where this project fits in Pharo/Smalltalk land. In the early 80s, I used the Xerox Parc Alto at Carnegie Mellon to run Smalltalk. I got laid off, went on a cruise, sat down in a beach chair with LEARN PHARO and an iPad. But, no Pharo for iPad. So I did the natural thing and told Claude Code to port Pharo to iPad. 54 days and 1347 commits later, out popped a usable iPad app. I do have a background in compilers, working on the Production Quality Compiler project at CMU in the early 1980s, mostly on lexers. But I didnât write any code for this. I mostly told CLAUDE a few times a day stop doing workarounds, do what the real VM does, and thatâs a workaround. CLAUDE would never have succeeded I think if I hadnât started insisting a focus on getting the test suite to pass rather than the app to work. >> >> The main snag using the real VM was encoding the encoding of type info in the high bits of pointers for immediate types. It seemed simple to me to shift the type info to the low 3 bits. But Claude could not get the real VM to stop looking in the high bits; perhaps I should have pushed harder on that. But I had always heard how easy it was to port Smalltalk, so I just went with a new VM with the type info in the low bits. Loading a standard image translates the addresses. >> The other issue was that Apple forbids JIT on iPad. So this new VM has no JIT. >> Issues: >> - Should this be a separate VM? Should I push harder on getting the standard VM to work with type info in the low bits and no JIT? Even if that would be better, is it worth the bother now that this works? >> >> - I donât want to suck up the PharoSmalltalk name in the Apple stores if it causes offense. I can call it VibeTalk or something to leave the name free for a hand-coded version. Or move off the name if a real contender ever shows. >> >> - Without JIT, is it too slow to bother releasing? Is there some other optimization that could bridge the gap if it is too slow? >> >> - Are there any users who can give the iPad version a really good workout in real work? The VM passes the test suite. But it just started working on the iPad today. There will be UI issues. >> >> - On the iphone the menu bar is cut off, and the welcome window is mostly off the screen. The menu bar layout is in the image, not the VM. I am not sure the VM should work around it. Should these be fixed in the image to have a multi-line menu bar as needed, and reshape initial window layouts on phones? If so is anyone willing to do the Smalltalk side or help me do it (I have written mostly other languages) >

March 2, 2026