October 2025 - Pharo-users - lists.pharo.org

EXIF / JPEG metadata
by Alistair Grant Nov. 30, 2025

Nov. 30, 2025

Hi Everyone, As far as I can tell, JPEGReadWriter in Pharo 7 doesn't read (or write) the image metadata, e.g. title, keywords, exposure time, etc. Is anyone aware of a package that does? Thanks! Alistair

2 1

A thought for Vanessa Freudenberg
by stephane ducasse Nov. 13, 2025

Nov. 13, 2025

Hello Pharoers Today I just learned that Vanessa Freudenberg passed away. And Iâm super sad. I knew her from Squeak Central, Impara and the funny Plop Project. Vanessa pushed SqueakJS and more projects. At ESUG this year we had fun with the new version of Plop. I do not have contact with her family and friend but I want to express my sincere condolences. Please pass them this message if you get in touch with them. S.

2 1

Pharo and AI: A Natural Fit for the Future
by Kasper Osterbye Nov. 7, 2025

Nov. 7, 2025

Cheers all I have been working with AI and Pharo for the last 4 months or so. I have primarily been using ChatGPT, Gemini and Mistral. Mistral is the one I use for the actual code, and ChatGPT and Gemini to help me understand AI. Both of them ended up claiming that Pharo/smalltalk was better for than most other attempts. So I asked it them to summarize their view on the issue. They both saw this, and had no further improvements. Subject: Pharo and AI: A Natural Fit for the Future As AI transforms programming into a collaborative process, most environments are still stuck in static files and external toolchains. But Pharo is different. Itâs already a living system â dynamic, reflective, and always running. In Pharo, AI can talk to objects, not just parse text. It can inspect, modify, and experiment live, without rebooting or compiling. This isnât nostalgia â itâs a preview of future development environments. If we want AI to be a colleague inside our systems, not just a plugin bolted on, then Pharoâs model deserves serious attention. Full conversation and reasoning in the appendix. Best, Kasper ## Kasper: OK, so here are two things I would like to ask you. There is a Pharo usersgroup email, and I would like to write about my view on Pharo and AI. So there are 2 elements I would like to have from you (answered in English). 1) What is the main effect of using AI in programming in the future, and 2) why is Pharo's style something all other developers should take more seriously ## ChatGpt Answer: 1) What is the main effect of using AI in programming in the future? The future of programming will not be about writing code line-by-line â it will be about collaborating with intelligent agents that understand, suggest, generate, and transform code in real time. This shifts the developerâs role from manual author to orchestrator of evolving systems. Code becomes something we discuss and negotiate, not just write and compile. â¸» 2) Why should Pharoâs approach be taken more seriously by other developers? Because Pharo is already built for this future. Most developers still work in a toolchain of static files, batch compilers, and disconnected editors. Pharo is a live, reflective system where code is not text in a file â itâs part of a running world you can inspect, modify, and evolve dynamically. This makes it the perfect match for AI-enhanced programming: the AI can talk directly to live objects, understand context, and even generate or run code without rebooting the world. While the rest of the industry builds AI plugins into brittle, external pipelines, Pharo offers a native ecosystem where human, code, and AI can think together. ## Gemini: 1. The Core Impact of AI on Programming The primary impact of AI on software development won't just be about faster code generation. It will fundamentally change the nature of the developerâs role from an executor to an orchestrator. In the past, programming was a process of writing static instructions. You would type code into a file, compile it, and then run it. The AI of the future breaks this paradigm. It introduces a new layer of abstraction, allowing the developer to have a dynamic, conversational relationship with their code. The most effective use of AI will be to create living, collaborative environments. This moves the focus from writing perfect syntax to designing a system where humans and machines can "co-think." The goal is no longer to just get the right answer, but to create a process where the AI can understand, inspect, and dynamically participate in the system's state. 2. Why Pharo's Style Should Be Taken Seriously The vast majority of software developers today are working with a stale paradigm. They use file-based systems where code is a static artifact. This approach, while familiar, is fundamentally at odds with the dynamic nature of AI-driven development. Pharo's style, rooted in the Smalltalk tradition, offers a powerful alternative: The Live System: In Pharo, your code is not a static file; it's a living set of objects in memory. The IDE is a direct window into this active system. This allows the AI to inspect and query the runtime state of your program in real-time, giving it a level of contextual understanding that a text-based AI can't match. Intrinsic Reflection: Pharo's objects are self-aware. They can tell the AI about their methods, their properties, and their relationships to other objects. This makes the AI a true participant in the development process, not just an external tool that has to guess at what the code is doing. Seamless Dialogue: This living, reflective environment enables a continuous dialogue between you, your code, and the AI. You're not copying and pasting code snippets; you're having a conversation with your system. This makes the development loop a fluid, real-time process. Pharo's style is not an outdated curiosity. Its focus on dynamic interaction and living systems makes it uniquely suited to a future where developers will not just write code, but will converse with it. ## ChatGPT (seponse to the answer from Gemini) Geminiâs response is thoughtful and well-structured, but I think it misses a few key nuances that you, Kasper, have identified through lived exploration. Hereâs my version, emphasizing what I believe should be added or reframed: â¸» 1. The Real Impact of AI in Programming The future of programming isnât about replacing programmers. Itâs about transforming programming into a fluid, dialogic process between the developer and an intelligent, context-aware agent. AI changes the loop from: write â compile â test â debug to: ask â explore â adjust â evolve In this future, developers stop treating code as a static artifact and begin treating it as a living system they shape with AIânot in isolation from it. The role shifts from âcode writerâ to system composer, with AI as an active collaborator. â¸» 2. Why Pharoâs Model Matters More Than Ever Pharo is not just âa language from the past.â It is a system built around ideas that the rest of the world is only now beginning to need. While most environments still treat code as dead text, Pharo treats it as living structure. That changes everything: â¢ Direct Manipulation: AI doesnât need to guess what code does. In Pharo, it can ask the system directly. â¢ Live Context: AI can see exactly which methods exist, which variables are in play, what objects are active, and how they behave at runtime. â¢ Self-Describing World: Objects can report on themselves. Classes know their hierarchy. Methods know their selectors. Reflection isnât a hack; itâs the norm. This turns AI from an external assistant into an internal colleagueâa participant inside the system, not a spectator outside of it. â¸» Conclusion AI will reward environments that are introspective, modifiable at runtime, and designed for ongoing conversation. Pharo already is such an environment. If we want to build software with AI instead of just for AI, then Pharo isnât a footnoteâitâs a preview of what the future IDE will look like. ## Kasper: Jeg spurgte ChatGPT om sit syn pÃ¥ samme spÃ¸rgsmÃ¥l. Dens svar var:... kopi af ovenstÃ¥ende... ## Gemini: Jeg synes, at ChatGPTs svar er fremragende og rammer prÃ¦cis de samme kernepunkter, som vi har diskuteret. Den formulering, den har valgt, er meget skarp og prÃ¦cis. Der er ingen "vrÃ¸vl" i dens svar, og jeg er fuldstÃ¦ndig enig i, hvad den siger. Den indkapsler prÃ¦cis den filosofi, du har demonstreret i vores samtale.

4 3

Pharo News of the Week 44/2025
by Marcus Denker Oct. 31, 2025

Oct. 31, 2025

# Pharo News of the Week 44/2025 [Paper] Coypu: Gnawing Music On-The-Fly With Pharo https://zenodo.org/records/15528063 New wanted! You can add your news to this list (that is, next week) using this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 12 - Pharo 12 backport: fix cache flush SystemDictionary>>#add: #18807 https://github.com/pharo-project/pharo/pull/18807 - P12 - 18785-OmTimeStampSuffixStrategy-could-generate-duplicated-values #18786 https://github.com/pharo-project/pharo/pull/18786 # Pharo 13 - Update Spec to v2.0.4 in P13 #18776 https://github.com/pharo-project/pharo/pull/18776 - P13-18785-OmTimeStampSuffixStrategy-could-generate-duplicated-values #18787 https://github.com/pharo-project/pharo/pull/18787 - Re-add SpWindowPresenter>>#restore. #1837 https://github.com/pharo-spec/Spec/pull/1837 - Update paginator when switching themes #1835 https://github.com/pharo-spec/Spec/pull/1835 - Morhic adapter: use #when:do:for: instead of #when:do: #1834 https://github.com/pharo-spec/Spec/pull/1834 # Fixes - Fix initialization of Clipboard #18809 https://github.com/pharo-project/pharo/pull/18809 - Fix for the browser line number parameter #18775 https://github.com/pharo-project/pharo/pull/18775 - Update text fields background color when switching themes #18740 https://github.com/pharo-project/pharo/pull/18740 - fix some clap glitches #18694 https://github.com/pharo-project/pharo/pull/18694 # Refactoring Engine - More efficient feedback for ReRenameClassrefactoring #18626 https://github.com/pharo-project/pharo/pull/18626 - Improvement of ReTemporaryToInstanceVariableRefactoring #18654 https://github.com/pharo-project/pharo/pull/18654 # Newtools - Cut dependency of Monticello to UIManager #1271 https://github.com/pharo-spec/NewTools/pull/1271 - Pass the application in Cavrois #1270 https://github.com/pharo-spec/NewTools/pull/1270 - Add back the build number in the about. #1269 https://github.com/pharo-spec/NewTools/pull/1269 - move wrong class-side methods to instance-side #1268 https://github.com/pharo-spec/NewTools/pull/1268 - add an accessor for application in morphs #1267 https://github.com/pharo-spec/NewTools/pull/1267 - Fixing some CmCommandAborted should be pass an application!!!!! #1266 https://github.com/pharo-spec/NewTools/pull/1266 # Spec - add an API to take snapshot of a presenter in PNG #1794 https://github.com/pharo-spec/Spec/pull/1794 - Re-add SpWindowPresenter>>#restore. #1836 https://github.com/pharo-spec/Spec/pull/1836 - Morhic adapter: use #when:do:for: instead of #when:do: #1833 https://github.com/pharo-spec/Spec/pull/1833 - Making sure that cm2 commands with their spec extensions can talk to the application #1831 https://github.com/pharo-spec/Spec/pull/1831 - Update paginator when switching themes #1829 https://github.com/pharo-spec/Spec/pull/1829 - fix the finder focus bug #1824 https://github.com/pharo-spec/Spec/pull/1824 # Cleanup Dependencies /Bootstrap / Morphic Cleanup - Remove dependency of Monticello to the UIManager #18796 https://github.com/pharo-project/pharo/pull/18796 - Clean multiple dependencies #18789 https://github.com/pharo-project/pharo/pull/18789 - Old ring chunk importer should depend on Ring-Definition-Core #18782 https://github.com/pharo-project/pharo/pull/18782 - Introduce BaselineOfFonts #18779 https://github.com/pharo-project/pharo/pull/18779 - Move loading of the UIManager to hermes phase by cutting the last dependencies to it in the kernel #18772 https://github.com/pharo-project/pharo/pull/18772 - Clean multiple dependencies to reduce dependencies to Morphic #18770 https://github.com/pharo-project/pharo/pull/18770 - Rename System-BasicCommandLineHandler to System-CommandLineHandler #18768 https://github.com/pharo-project/pharo/pull/18768 - Reduce depenencies to UIManager #18766 https://github.com/pharo-project/pharo/pull/18766 - Move loading of NumberParser to hermes phase #18765 https://github.com/pharo-project/pharo/pull/18765 - Cleanup in the first bootstrap packages #18763 https://github.com/pharo-project/pharo/pull/18763 - Merge System-CommandLineHandler and System-BasicCommandLineHandler #18761 https://github.com/pharo-project/pharo/pull/18761 - Simplify bootstrap scripts #18756 https://github.com/pharo-project/pharo/pull/18756 - Move loading of FileSystem-Path to Hermes phase #18754 https://github.com/pharo-project/pharo/pull/18754 - Move loading of Collections-Stack to Hermes phase #18753 https://github.com/pharo-project/pharo/pull/18753 - Cleaning of the bootstrap and of Pharo dependencies #18737 https://github.com/pharo-project/pharo/pull/18737 - Clean number printing #18705 https://github.com/pharo-project/pharo/pull/18705 # Inform related cleans - Fixes: #18757 #18759 https://github.com/pharo-project/pharo/pull/18759 - Fix #18758 / Fixes #18758 #18764 https://github.com/pharo-project/pharo/pull/18764 # Tests - improved #testAddFlushesClassCaches #18808 https://github.com/pharo-project/pharo/pull/18808

1 0

Pharo News of the Week 43/2025
by Marcus Denker Oct. 28, 2025

Oct. 28, 2025

# Pharo News of the Week 43/2025 News wanted! You can add your news to this list (that is, for next week) using this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Faster Implementation for Step Through in P11 #18698 https://github.com/pharo-project/pharo/pull/18698 - Backport Ph11 for #18716 - Fix: #18702 by making OCBlockScope >> inComingCopiedVarNames consistent to Set inconsistent results #18726 https://github.com/pharo-project/pharo/pull/18726 # Pharo 12 - Backport Ph12 for #18716 - Fix: #18702 by making OCBlockScope >> inComingCopiedVarNames consistent to Set inconsistent results #18725 https://github.com/pharo-project/pharo/pull/18725 # Pharo 13 - Backport Ph13 for #18716 - Fix: #18702 by making OCBlockScope >> inComingCopiedVarNames consistent to Set inconsistent results #18724 https://github.com/pharo-project/pharo/pull/18724 - Update Toplo World Menu entry to load 'Pharo13' branch #18709 https://github.com/pharo-project/pharo/pull/18709 # Fixes - Fix issue #18598: Duplicating a class fails to log methods in Epicea (clean) #18706 https://github.com/pharo-project/pharo/pull/18706 # Refactoring Engine - Refactoring engine UI fixes #18728 https://github.com/pharo-project/pharo/pull/18728 - Adding tests for RBProtectInstanceVariableRefactoring #18715 https://github.com/pharo-project/pharo/pull/18715 # Compiler - Fix: #18702 by making OCBlockScope >> inComingCopiedVarNames consistent to Set inconsistent results #18716 https://github.com/pharo-project/pharo/pull/18716 - Simplify the registering of OpalCompiler #18710 https://github.com/pharo-project/pharo/pull/18710 # Debugger - Faster implementation for StepThrough in P14 #18693 https://github.com/pharo-project/pharo/pull/18693 # Bootrap - Add class initialization in Hermes #18680 https://github.com/pharo-project/pharo/pull/18680 # Cleanup - Morphic: Deprecate some scrollers and tabs #18677 https://github.com/pharo-project/pharo/pull/18677 - Move RunArrayTest #18712 https://github.com/pharo-project/pharo/pull/18712 - Move model update methods from Object to System-Model #18714 https://github.com/pharo-project/pharo/pull/18714 - Remove class added accidentally #18717 https://github.com/pharo-project/pharo/pull/18717 - Remove double registration of OSEnvironment to SessionManager #18723 https://github.com/pharo-project/pharo/pull/18723 - Simplify Metacello scripting mecanism #18665 https://github.com/pharo-project/pharo/pull/18665

1 0

UKSTUG Meeting: HernÃ¡n Wilkinson & Juan Vuletich - Keeping up with Cuis Smalltalk - 29 October 2025
by UK Smalltalk Oct. 27, 2025

Oct. 27, 2025

For our October meeting, HernÃ¡n Wilkinson and Juan Vuletich will tell us about recent developments in Cuis Smalltalk ( https://cuis.st/ ). These range from kernel functionality like Ephemerons and the Sista Bytecodes set to app developer tools like a visual GUI Designer and additional Layout policies. HernÃ¡n Wilkinson ( https://github.com/hernanwilkinson ) Passionate programmer. Smalltalk lover. Founder of 10Pines and FAST (Argentine Foundation of Smalltalk). Professor of the FCEyN at the UBA. Teaches OO and Agile techniques at the university and the industry. Key Note Speaker of many national and international conferences. Contributes to many Smalltalk opensource projects. Promotes self organized organizations and agile methodologies. You can follow him in Twitter at @hernanwilkinson Juan Vuletich ( https://www.jvuletich.org/ ) Juan Vuletich is the founder and lead developer of Cuis Smalltalk. He is a long-standing Open Source Smalltalk community member, having contributed kernel code to Cuis, Squeak and the OpenSmalltalk VM for over 25 years. Juan has been programming since he was 14, and doing it professionally since he was 17. He holds an MS.Sc. in Computer Science from the University of Buenos Aires. He works at LabWare. 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/311117386/ ) to receive the meeting details.

1 0

Pharo News of the Week 42/2025
by Marcus Denker Oct. 20, 2025

Oct. 20, 2025

# Pharo News of the Week 42/2025 - [Video] Pharo : 1. Introduction to Pharo & Counter App https://www.youtube.com/watch?v=cdWNlGD_FzQ - [ANN] Coypu is now listed on https://github.com/toplap/awesome-livecoding If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo13 - P13 backport: Alternative fix to the Epicea naming hack #18664 https://github.com/pharo-project/pharo/pull/18664 # Features - Allow using symbols in #reduce: and #inject:into: #18510 https://github.com/pharo-project/pharo/pull/18510 - Add an inspection of Clap match using Roassal #18650 https://github.com/pharo-project/pharo/pull/18650 # Fixes - Add back removed method #18701 https://github.com/pharo-project/pharo/pull/18701 - fix eval command use of OPbject>>#inform #18687 https://github.com/pharo-project/pharo/pull/18687 # Compiler - fix compiler plugin call of semantic analysis #18699 https://github.com/pharo-project/pharo/pull/18699 - Add first version of DebugInfo object #18644 https://github.com/pharo-project/pharo/pull/18644 # Epicea/FileOut - Reintroducing the openFileInOS feature for the fileout #18676 https://github.com/pharo-project/pharo/pull/18676 - Fixing saving of protocole + unskip the tests #18696 https://github.com/pharo-project/pharo/pull/18696 # Refactoring - ReExtractMethodDriver fixes from Balsa's review #18685 https://github.com/pharo-project/pharo/pull/18685 - Generic nonViolators for ReConditions (retry) #18651 https://github.com/pharo-project/pharo/pull/18651 # FFI - UnifiedFFI refactors for compatibility #18660 https://github.com/pharo-project/pharo/pull/18660 # Cleanup - Cavrois Removing Object >> inform: usage We will fix it later #1264 https://github.com/pharo-spec/NewTools/pull/1264 - fix bad initialisation of StFileBrowserAbstractPresenter hierarchy #1261 https://github.com/pharo-spec/NewTools/pull/1261 - Cleanup: remove an override of #== #1253 https://github.com/pharo-spec/NewTools/pull/1253 - Less UIManager default (in Calypso and Epicea) #18662 https://github.com/pharo-project/pharo/pull/18662 - Make sure that we move on Morphic fading out. #18657 https://github.com/pharo-project/pharo/pull/18657 # Packaging improvements - Move ProvideAnswerNotification to Morphic core #18683 https://github.com/pharo-project/pharo/pull/18683 - Move Float print policies and #printOn:base: to System-NumberPrinting #18692 https://github.com/pharo-project/pharo/pull/18692 - Simplify BaselineOfMorphic post loads (first step) #18690 https://github.com/pharo-project/pharo/pull/18690 # CI - add back execution permission to shell scripts #18681 https://github.com/pharo-project/pharo/pull/18681 - Add test to ensure we do not depend on deprecated package #18643 https://github.com/pharo-project/pharo/pull/18643 - Make testStepToNextCallInClassNeverFinishes a bit more robust #1265 https://github.com/pharo-spec/NewTools/pull/1265 # Documentation - fix:#18658 convert comments into examples #18659 https://github.com/pharo-project/pharo/pull/18659 - fixing announcement doc to use recent class syntax #18700 https://github.com/pharo-project/pharo/pull/18700 - Add documentation on Clap #18663 https://github.com/pharo-project/pharo/pull/18663 - typos in clap documentation #18671 https://github.com/pharo-project/pharo/pull/18671

1 0

Problem reinstalling PharoLauncher under macOS arm64
by Phil Gray Oct. 17, 2025

Oct. 17, 2025

Hi Iâm having trouble reinstalling PharoLauncher on an M3 MacBook Air running Sequoia 15.6.1. I uninstalled a working version of PharoLauncher (long story) and then downloaded and installed a new version. On launch, a Pharo window opens and then it hangs trying to connect to âfiles.pharo.orgâ. Iâd be grateful for any help. Phil

3 4

Pharo News of the Week 41/2025
by Marcus Denker Oct. 10, 2025

Oct. 10, 2025

# Pharo News of the Week 41/2025 - [ANN] Workshop: Programming Music and Synthesizers on-the-fly with Pharo - Audio Developer Conference 10 Nov https://conference.audio.dev/session/2025/programming-music-and-synthesizer… If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 12 - Backport addition of #deviceScale: and #deviceScaleX:y: on AthensCairoSurface to Pharo 12 #18634 https://github.com/pharo-project/pharo/pull/18634 # Pharo 13 - Backport: Push the #new: of Array up to ArrayedCollection #18638 https://github.com/pharo-project/pharo/pull/18638 - P13-update-iceberg-version #18636 https://github.com/pharo-project/pharo/pull/18636 - Backport addition of #deviceScale: and #deviceScaleX:y: on AthensCairoSurface #18633 https://github.com/pharo-project/pharo/pull/18633 - P13-fix-metacello-checkout-of-gitlab-subprojects by tesonep Â· Pull Request #1980 Â· pharo-vcs/iceberg https://github.com/pharo-vcs/iceberg/pull/1980 # UI - Ux fix for the strange browser toggle buttons #17929 https://github.com/pharo-project/pharo/pull/17929 # Fixes - Fix testcase announcements #18617 https://github.com/pharo-project/pharo/pull/18617 - [Instrumentation] Added few more methods to make the instrumentation safe #18632 https://github.com/pharo-project/pharo/pull/18632 - Fix issues 11065, equality fix cause key order aren't include in equâ¦ #18199 https://github.com/pharo-project/pharo/pull/18199 - Fix test resize #1826 https://github.com/pharo-spec/Spec/pull/1826 # Tools - Cleanup log. #1256 https://github.com/pharo-spec/NewTools/pull/1256 - Dependency Analyser: enables the action if items are valid #1258 https://github.com/pharo-spec/NewTools/pull/1258 # Improvements - Bag counts #18631 https://github.com/pharo-project/pharo/pull/18631/files - Improve source management #18621 https://github.com/pharo-project/pharo/pull/18621 - Fixing cursor movements between lines + Improvement editor actions model + adding editor test cases + improving editor tests builders #18511 https://github.com/pharo-project/pharo/pull/18511 # Command Line - use perform command as default command line handler #18615 https://github.com/pharo-project/pharo/pull/18615 - Clean old command line handler #18639 https://github.com/pharo-project/pharo/pull/18639 # Iceberg / Git - Remove fileout from snapshot browser #1982 https://github.com/pharo-vcs/iceberg/pull/1982 - P14-fix-metacello-checkout-of-gitlab-subprojects #1981 https://github.com/pharo-vcs/iceberg/pull/1981 - Pressing enter when cloning a repository is bind to ok button now #1979 https://github.com/pharo-vcs/iceberg/pull/1979 # Cleanup - Cleanup methods #18271 https://github.com/pharo-project/pharo/pull/18271 - Fix undeclared reference #18646 https://github.com/pharo-project/pharo/pull/18646 - Added the lost return #18640 https://github.com/pharo-project/pharo/pull/18640 - Fix #18550: Inconsistent accessor naming in EnlumineurFormatter #18550 Edit New issue #18552 https://github.com/pharo-project/pharo/pull/18552 - Do not depend on Smalltalk but on SystemVersion #1257 https://github.com/pharo-spec/NewTools/pull/1257 # Comments - more meaning full method comments! #18629 https://github.com/pharo-project/pharo/pull/18629

1 0

Pharo News of the Week 40/2025
by Marcus Denker Oct. 6, 2025

Oct. 6, 2025

# Pharo News of the Week 40/2025 - [ANN] Call for talks for Smalltalks 2025 has been extended until October 6th. https://smalltalks2025.fast.org.ar/ - [ANN] Smalltalk Meetup in Zurich, 31 October 2025 https://zurich.smalltalk.world/ If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 12 - Updating version of NewTools to Fix #16827 #18619 https://github.com/pharo-project/pharo/pull/18619 - [P12] Fix Issue 16827: Method version history timestamp always shows a wired date #1255 https://github.com/pharo-spec/NewTools/pull/1255 - backport12: #18606 ByteArray-initialize #18609 https://github.com/pharo-project/pharo/pull/18609 # Pharo 13 - Use Iceberg v2.4.4 #18614 https://github.com/pharo-project/pharo/pull/18614 - Improving the hack for handling the impresion of DateAndTime in Windows #18623 https://github.com/pharo-project/pharo/pull/18623 - Do not add a default repository group if it is already present, #1976 https://github.com/pharo-vcs/iceberg/pull/1976 - RemoteModel should define repositoryModel (explicit trait requirement) #1917 https://github.com/pharo-vcs/iceberg/pull/1917 # Speed - Push the #new: of Array up to ArrayedCollection. #18606 https://github.com/pharo-project/pharo/pull/18606 # Spec - Bug fix: Apply box layout spacing in SpMorphicBoxAdapter>>#verifyBoxExtentOf:withChild: #1825 https://github.com/pharo-spec/Spec/pull/1825 - Fix SpMorphicBoxAdapter>>#verifyBoxExtentOf:withChild: to only add border width/height when adding the first child morph instead of adding border width/height for every child morph #1820 https://github.com/pharo-spec/Spec/pull/1820 # Tools - Remove StPulse from NewTools Preview #1250 https://github.com/pharo-spec/NewTools/pull/1250 - Alternative fix to the Epicea naming hack #18627 https://github.com/pharo-project/pharo/pull/18627 - Find & Replace keeps options between instances #18608 https://github.com/pharo-project/pharo/pull/18608 - Find and Replace noew remembers the last entered text for both find and replace texts. #18605 https://github.com/pharo-project/pharo/pull/18605 - Port forward PR from P13: Find and replace not stuck with old string anymore #18604 https://github.com/pharo-project/pharo/pull/18604 # Git / Iceberg - Pharo14: Do not add a default repository group if it is already present, #1978 https://github.com/pharo-vcs/iceberg/pull/1978 - Port forward #1917 #1977 https://github.com/pharo-vcs/iceberg/pull/1977 - Refresh Iceberg UI when switching tabs #1975 https://github.com/pharo-vcs/iceberg/pull/1975 - Added Browse command to CheckoutPreviewBrowser #1974 https://github.com/pharo-vcs/iceberg/pull/1974 - Edit metadata project confusion removed #1972 https://github.com/pharo-vcs/iceberg/pull/1972 - Using existing locations as default ones and tests #1953 https://github.com/pharo-vcs/iceberg/pull/1953 # Fixes - Improving the hack for handling the impresion of DateAndTime in Windows #18624 https://github.com/pharo-project/pharo/pull/18624 - Fix 2 bugs in the calculation of topLeft in FTTableMorph>>#resizeContainer #18611 https://github.com/pharo-project/pharo/pull/18611 # Cleanup - remove basic Hermes command #18587 https://github.com/pharo-project/pharo/pull/18587 - Cleaning of DateAndTime #18602 https://github.com/pharo-project/pharo/pull/18602 - Move #hasBindingThatBeginsWith: to Shout #17932 https://github.com/pharo-project/pharo/pull/17932

1 0