April 2023 - 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

The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently...
by mark.odonoghue.2010＠gmail.com May 12, 2024

May 12, 2024

![Image](https://media.discordapp.net/attachments/223421264751099906/1060833258427920385/image.png)

4 4

Re: [Pharo-users] Personal wiki / information manager
by Evan Donahue Sept. 25, 2023

Sept. 25, 2023

Seems that Pharo is a magnet for this kind of project. I've been writing one as well and using it to organize my research notes. Does anyone working on personal info mgmt tools want to talk offline? I expect we're running into some of the same issues, both conceptual and technical. Evan

18 33

Pharo being featured in Exercism's Mind Shifting May
by bajger＠gmail.com May 11, 2023

May 11, 2023

Hi there! Hi there! Pharo track will be promoted on Mind shifting May of Exercism initiative. Here are some details from one Exercism founder (Erik): \ \ https://forum.exercism.org/t/pharo-being-featured-in-mind-shifting-may/5420 There are couple of things we could improve here: \ where it is used: weâd definitely find better and newer examples that ATMs usecaseâ¦ where it is great: I would add productivity, once people get through initial learning curve. It is tightly connected to bullets below (image based approach and liveness and immersive env.) Features: embeddability and interoperability with othe PLs - working on minimal Pharo image that can be part of e.g. C program and vice versa. So if you have ideas, thoughts how this script can be improved, please reply!

4 4

Porting from VW to Pharo
by Steffen MÃ¤rcker May 8, 2023

May 8, 2023

Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following package from Store: - Smalltalk Transform Project 3. Is there a page that documents the process process in general? https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific for PDFtalk like the thread on this list. Kind regards, Steffen

5 14

Collection>>reduce naming
by Steffen MÃ¤rcker April 30, 2023

April 30, 2023

Hi! I wonder whether there was a specific reason to name this method #reduce:? I would have expected #fold: as this is the more common term for what it does. And in fact, even the comment reads "Fold the result of the receiver into aBlock." Whereas #reduce: is the common term for what we call with #inject:into: . I am asking not to annoy anyone but out of curiosity. It figured this out only by some weird behaviour after porting some code that (re)defines #reduce . Ciao! Steffen

4 22

This week (17/2023) on the Pharo Issue Tracker
by Marcus Denker April 28, 2023

April 28, 2023

# Pharo 11 - Refactor block ensure during termination to allow override #13534 https://github.com/pharo-project/pharo/pull/13534 # Pharo 12 ## Small Improvements - Small cleanup #bitShift:, #<< and #<< #13523 https://github.com/pharo-project/pharo/pull/13523 - Clean info of MethodChangeRecord #13519 https://github.com/pharo-project/pharo/pull/13519 - remove some methods that are just copied from a superclass #13504 https://github.com/pharo-project/pharo/pull/13504 - Some RPackage cleanups #13505 https://github.com/pharo-project/pharo/pull/13505 - Adding inspector transmission node #510 https://github.com/pharo-spec/NewTools/pull/510 ## Protocol - Use #protocolOfSelector: in CompiledMethod>>#category #13457 https://github.com/pharo-project/pharo/pull/13457 - Improve ClassDescription>>#addAndClassifySelector:withMethod:inProtocol: #13533 https://github.com/pharo-project/pharo/pull/13533 - Fix case were method is in a class but not in a protocol #13572 https://github.com/pharo-project/pharo/pull/13572 - Simplify ClassOrganization>>removeElement: and remove protocol if empty #13530 https://github.com/pharo-project/pharo/pull/13530 - Classify method before installing them #13539 https://github.com/pharo-project/pharo/pull/13539 - Make Protocol announcements use real protocols #13506 https://github.com/pharo-project/pharo/pull/13506 ## AST - Style literal arrays #13502 https://github.com/pharo-project/pharo/pull/13502 - Do not hardcode stylers #13537 https://github.com/pharo-project/pharo/pull/13537 - AST: cleanup scanner #13562 https://github.com/pharo-project/pharo/pull/13562 - AST: kill multiple keyword token #13554 https://github.com/pharo-project/pharo/pull/13554 - AST: cleanup compiler API (and clients) #13520 https://github.com/pharo-project/pharo/pull/13520 - AST: cleanup extension methods from OpalCompiler #13514 https://github.com/pharo-project/pharo/pull/13514 ## Compiler - Compiler: doSemanticAnalysis yourself #13517 https://github.com/pharo-project/pharo/pull/13517 - add new test RBCodeSnippet class>>#badScanner with special scanner hacks #13553 https://github.com/pharo-project/pharo/pull/13553 - Add compiler option to not optimise special sends #13569 https://github.com/pharo-project/pharo/pull/13569 - Factorize some code in recompilation management #13551 https://github.com/pharo-project/pharo/pull/13551 - Scope: generalize target class #13540 https://github.com/pharo-project/pharo/pull/13540 - RBMethodMode: compiledMethod sould be a simple accessor #13525 https://github.com/pharo-project/pharo/pull/13525 - Detach compilationContext a little #13511 https://github.com/pharo-project/pharo/pull/13511 - Reduce usage of compilationContext from IR* Classes #13513 https://github.com/pharo-project/pharo/pull/13513 ## CompiledMethod trailer cleanup - Compiler: Cleanup trailer for the frontend #13575 https://github.com/pharo-project/pharo/pull/13575 - Compiler: Cleanup for trailer removal in IRByteCodeGenerator #13565 https://github.com/pharo-project/pharo/pull/13565 - Cleanup: do not reference CompiledMethodTrailer in ReflectiveMethod #13564 https://github.com/pharo-project/pharo/pull/13564 - Cleanup: Fuel does not need to use #copyWithTrailerBytes: #13560 https://github.com/pharo-project/pharo/pull/13560 - Cleanup-instanceCreationCompiledMethod #13559 https://github.com/pharo-project/pharo/pull/13559 - Do not use #trailer to read the sourcePointer #13558 https://github.com/pharo-project/pharo/pull/13558 - getSourceFromFile-return-nil #13556 https://github.com/pharo-project/pharo/pull/13556 - Cleanup: CompiledMethodTrailer should not create methods #13555 https://github.com/pharo-project/pharo/pull/13555 - CompiledMethodTrailer-Cleanup-even-more #13550 https://github.com/pharo-project/pharo/pull/13550 - CompiledMethodTrailer: more cleanup, do not use it for #endPC #13546 https://github.com/pharo-project/pharo/pull/13546 - CompiledMethodTrailer: remove #VarLengthSourcePointer support #13545 https://github.com/pharo-project/pharo/pull/13545 - CompiledMethodTrailer: use 4 bytes as sourcePointer #13527 https://github.com/pharo-project/pharo/pull/13527 - Cleanup-Tests-CompiledMethodTrailer #13528 https://github.com/pharo-project/pharo/pull/13528 - Cleanup-CompiledMethod-Source-Embedding #13522 https://github.com/pharo-project/pharo/pull/13522 - remove all unsused encodings from CompiledMethodTrailer. #13510 https://github.com/pharo-project/pharo/pull/13510 - CompiledMethod simplification: remove the last user of #copyWithSource: #13507 https://github.com/pharo-project/pharo/pull/13507 ## Improve Tests - Commit-Deprecation-Rewrites #13567 https://github.com/pharo-project/pharo/pull/13567 - Make shift tests more robust #13570 https://github.com/pharo-project/pharo/pull/13570 - Small cleanings in tests #13576 https://github.com/pharo-project/pharo/pull/13576 - Ensure ThreadedFFI tests terminate all launched processes #13538 https://github.com/pharo-project/pharo/pull/13538 - Make sure class parser tests clean the system #13536 https://github.com/pharo-project/pharo/pull/13536 - Reflectivity: make tests more reliable (and fix a bug) #13544 https://github.com/pharo-project/pharo/pull/13544

1 0

This week (16/2023) on the Pharo Issue Tracker
by Marcus Denker April 21, 2023

April 21, 2023

We merged ~60 PRs this week. # Pharo 11 - Backport #13426: Make protocol of super method a priority in MethodClassifier #13432 https://github.com/pharo-project/pharo/pull/13432 - Use fixed spec version for Pharo 11 #13445 https://github.com/pharo-project/pharo/pull/13445 ## GIT/Iceberg (for Pharo 12, too) - 1279 merge menu should indicate the sense of the action #1680 https://github.com/pharo-vcs/iceberg/pull/1680 - Remove unused variable #1695 https://github.com/pharo-vcs/iceberg/pull/1695 - Fix for adding a SSH credential from UI raises an Error #1638 https://github.com/pharo-vcs/iceberg/pull/1638 - Use ED25519 keys as default instead of RSA to improve security and follow new GitHub standards #1649 https://github.com/pharo-vcs/iceberg/pull/1649 - [fix] prevent Iceberg window to crash when the registry is empty #1670 https://github.com/pharo-vcs/iceberg/pull/1670 - Fix for issue #11969 in pharo repository: Better description "packages unloaded packages #1672 https://github.com/pharo-vcs/iceberg/pull/1672 #Pharo 12 ## Enhancements - Completion menu: some love on the detail window #13473 https://github.com/pharo-project/pharo/pull/13473 - Use Pharo12 branch of Spec and NewTools #13460 https://github.com/pharo-project/pharo/pull/13460 - Fix random failure of Ombu in windows. #13448 https://github.com/pharo-project/pharo/pull/13448 - Make protocol of super method a priority in MethodClassifier #13426 https://github.com/pharo-project/pharo/pull/13426 - Cut dependency from CommandLine to UIManager #13431 https://github.com/pharo-project/pharo/pull/13431 - Fix typo introduced in merge #13446 https://github.com/pharo-project/pharo/pull/13446 - Added inspector extensions for RPackage #509 https://github.com/pharo-spec/NewTools/pull/509 ## RPackage and SystemOrganizer - Synch bug in RPackage removal #13496 https://github.com/pharo-project/pharo/pull/13496 ## Protocol and Categories - Keep pushing protocols usage #13443 https://github.com/pharo-project/pharo/pull/13443 - Add some tests on classifications of methods #13485 https://github.com/pharo-project/pharo/pull/13485 - Rename #removeMethodTag: into #removeProtocolIfEmpty: #13492 https://github.com/pharo-project/pharo/pull/13492 - Make #renameProtocolNamed:toBe: manage nils #13480 https://github.com/pharo-project/pharo/pull/13480 - Cleaning of #classify:inProtocolNamed: #13454 https://github.com/pharo-project/pharo/pull/13454 - Deprecate comment management of ClassOrganization #13464 https://github.com/pharo-project/pharo/pull/13464 - Remove ClassOrganization>>#silentlyRenameProtocolNamed:toBe: in favor of always announcing the rename #13458 https://github.com/pharo-project/pharo/pull/13458 - Improve ClassOrganization copy #13453 https://github.com/pharo-project/pharo/pull/13453 - Do not use #classComment #1376 https://github.com/pharo-spec/Spec/pull/1376 ## Compiler: Syntax Hightlight - SHRBTextStyler class>>#blueStyleTable distinguish some variables #13501 https://github.com/pharo-project/pharo/pull/13501 - Improve style for parenthesis, comments and syntax error #13491 https://github.com/pharo-project/pharo/pull/13491 - CodeSnippet: industrialize the testing of the styler #13490 https://github.com/pharo-project/pharo/pull/13490 - add SHRBStyleAttributionTest>>#testErrorStyle #13489 https://github.com/pharo-project/pharo/pull/13489 - Faulty code: improve highlight and icons #13486 https://github.com/pharo-project/pharo/pull/13486 - Fix bug in parenthesis highlight #13467 https://github.com/pharo-project/pharo/pull/13467 ## Compiler: AST - AST: starting visiting comments #13421 https://github.com/pharo-project/pharo/pull/13421 - Snippet: test more comments and fix some #13500 https://github.com/pharo-project/pharo/pull/13500 - Add support to deprecate globals #13348 https://github.com/pharo-project/pharo/pull/13348 - Compiler: expose the AST #13487 https://github.com/pharo-project/pharo/pull/13487 ## Compiler - Snippets: rename (and negate) isMethod to isScripting #13499 https://github.com/pharo-project/pharo/pull/13499 - Vocabulary: propose "script" in compiler #13301 https://github.com/pharo-project/pharo/pull/13301 - OpalCompiler: permit clients to use receiver: after context: as (a noop) #13498 https://github.com/pharo-project/pharo/pull/13498 - Introduce annotations #13449 https://github.com/pharo-project/pharo/pull/13449 - Use Compiler not #copyWithTrailerBytes #13488 https://github.com/pharo-project/pharo/pull/13488 - Directly update source pointer without creating an additional compiled method #13484 https://github.com/pharo-project/pharo/pull/13484 - remove-embeddSourceInTrailer #13481 https://github.com/pharo-project/pharo/pull/13481 - Compiler: remove #optionEmbeddSources #13479 https://github.com/pharo-project/pharo/pull/13479 - Compiler: explicit the need of requestor scope #13472 https://github.com/pharo-project/pharo/pull/13472 - Kill VariableNotDeclared #13471 https://github.com/pharo-project/pharo/pull/13471 - Factorize UndeclaredVariableErrors #13470 https://github.com/pharo-project/pharo/pull/13470 - Debug can recompile doit and uninstalled method #13469 https://github.com/pharo-project/pharo/pull/13469 - Cleanup OpalCompiler & CompilationContext #13423 https://github.com/pharo-project/pharo/pull/13423 - Compiler: simplify DoIt #13398 https://github.com/pharo-project/pharo/pull/13398 - faulty code: test runtimeSyntaxError #13422 https://github.com/pharo-project/pharo/pull/13422 - Rubric editors (thus calypso) execute doit actions in faulty mode #13450 https://github.com/pharo-project/pharo/pull/13450 - Debugger: can handle new exceptions UndeclaredVariableRead&UndeclaredVariableWrite #508 https://github.com/pharo-spec/NewTools/pull/508 - StTestDebuggerProvider class>>#compileMissingClassContextBuilder use permitUndeclared: #506 https://github.com/pharo-spec/NewTools/pull/506 - add missing SpCodeScriptingInteractionModel>>#needRequestorScope #1378 https://github.com/pharo-spec/Spec/pull/1378 - Spec2-Code: declare 'playground'-related capabilities as a compiler requestor #1377 https://github.com/pharo-spec/Spec/pull/1377 ## Cleanups - Refactoring BlockClosureTest >> testCannotReturn #13459 https://github.com/pharo-project/pharo/pull/13459 ## Trivial - use {} instead of Array with:with: #13483 https://github.com/pharo-project/pharo/pull/13483 - use nested and expression #13475 https://github.com/pharo-project/pharo/pull/13475 - use and expression instead of ifTrueifFalse #13477 https://github.com/pharo-project/pharo/pull/13477 - use and expression instead of ifTrueifFalse #13463 https://github.com/pharo-project/pharo/pull/13463 - Use {} instead of "Array with:" for some usages #13461 https://github.com/pharo-project/pharo/pull/13461

1 0

Yoshiki Ohshima - Croquet Microverse - 26 April 2023
by Giovanni Corriga April 20, 2023

April 20, 2023

For this month's online presentation, Yoshiki Ohshima will demonstrate the Croquet Microverse ( https://croquet.io/ ), which is a 3D collaborative construction environment. It is an incarnation of Smalltalk-based Croquet but instead implemented in JavaScript. Microverse allows a group of users to collaboratively create new objects in a virtual space, and describe their behaviors in the live programming manner that can be used by professional programmers. The object extension mechanism used in the Microverse is heavily influenced by past class and object extension mechanisms, many of which originated from experimentation and implementation in Smalltalk. Likewise, the architecture of the Microverse application framework draws upon other frameworks such as Morphic and AppKit. Yoshiki will explain the connections between those systems and the Microverse. Yoshiki ( https://tinlizzie.org/ohshima/ ) joined Walt Disney Imagineering R&D in 2000 as an intern while attending the graduate school of Tokyo Institute of Technology, and helped develop prototypes of Disney's theme park attractions. He also has been involved in Alan Kay's research group, and participated in the research and development effort of education programming environment Squeak Etoys and later took the leading role. Yoshiki has worked at the Viewpoints Research Institute, SAP Labs CDG, and Y Combinator Research, all of which Dr. Kay founded or helped found. He was awarded his PhD. for designing and implementing a massively parallel particle programming system from Tokyo Institute of Technology. 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/292570084/ ) to receive the meeting details.

1 0

Project and package structure recommendations
by Steffen MÃ¤rcker April 20, 2023

April 20, 2023

Hi, I'd like to ask for your advice or best practices regarding the package structure of a project. So far I have understood: - Iceberg can store multiple packages (project?) in a git repository - A package (or multiple?) and its dependencies is loaded via a baseline - A package can have flags (= categories?) Suppose, a project has - A core part - One or multipel optional parts, that a user may or may not want to load, too - Tests for the core - Tests for each optional part What's the recommended way to structure this in Pharo? For example, I've seen that some code in Pharo has its tests in the same package but flagged/categorized, other code has a separate package for tests. Also, can a (git) repository have multiple baselines? Sorry, if I am asking the obvious but I did not manage to find guidlines in the documentation yet. It might very well an oversight be myself. Kind regards, Steffen

3 3