December 2024 - Pharo-users

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

"Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime
by Koen De Hondt Feb. 13, 2025

Feb. 13, 2025

Dear Pharo users and developers, It required an enormous effort to review, rewrite, and extend it, but I am happy to announce that it is finally here: the book on application building in Pharo with Spec 2.0. I wrote a blog post about it <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! Ciao, Koen

8 21

"Evaluation of SUnit" â New blog post on all: objects all: theTime
by Koen De Hondt Jan. 7, 2025

Jan. 7, 2025

Dear Pharo users and developers, I wrote a blog post in which I evaluate SUnit <https://all-objects-all-the-time.st/#/blog/posts/10>. Enjoy reading it! Ciao, Koen

4 6

"Comparing SUnit with RSpec" â New blog post on all: objects all: theTime
by Koen De Hondt Dec. 31, 2024

Dec. 31, 2024

Dear Pharo users and developers, After my previous blog post on SUnit, I added a follow-up post <https://all-objects-all-the-time.st/#/blog/posts/11> on the comparison of SUnit and RSpec for Ruby. Happy reading! This will be my last post for 2024. Happy holidays and all the best for 2025. Ciao, Koen

2 1

Need Help with Changing Message Sends in Compiled Blocks
by Sebastian Jordan Dec. 30, 2024

Dec. 30, 2024

TL;DR: I need help changing the message OrderedCollection new to OrderedCollection --> newTenured <-- at a specific offset in a compiled block. I can do this for regular methods, but I get an error when the method is a Block. Hello everyone, I'm trying to automatically change message sends in my code, but I'm having trouble with compiled blocks. For example, I want to change the message OrderedCollection new to OrderedCollection --> newTenured <-- in a specific method. I have the compiled block and the offset (26) for the message I want to change. However, searching for the selector new doesn't work because there can be multiple messages with the same name, and I only want to change the one at the given offset. theMethod | tmp1 | 1 = tmp1 something: [ "rewrite this message send" OrderedCollection new ]. tmp1 otherStruf: [ Dictionary new "do not rewrite this meesage send" ]. ^ self I can change the message when there is no block without any problem using the IR like this: transformMessageSend: compiledMethodOrBlock offset: offset | oldSelector newSelector irSendNode ir irSequences | oldSelector := (compiledMethodOrBlock sourceNode sourceNodeForPC: offset) selector. newSelector := self makeNewSelector: oldSelector. ir := compiledMethodOrBlock ir. irSequences := ir allSequences flatCollect: #children. irSendNode := (irSequences select: #isSend) detect: [ :e | e selector = oldSelector ]. irSendNode selector: newSelector. ^ ir generate selector: compiledMethodOrBlock selector; yourself But I get an error with ir generate when the compiledMethodOrBlock is a Block. If it's a normal compiled method, it works as expected. Can anyone help me with this? Thanks! PS: I'm not forced to do it with the IR, ir can be done by using the AST. The only thing is that I'd like to avoid doing string manipulation Cheers and merry christmas, Sebastian Jordan

2 1

files.pharo.org scheduled downtime
by Christophe Demarey Dec. 23, 2024

Dec. 23, 2024

Dear Pharo users, We would like to inform you that the files.pharo.org service will be unavailable due to an electrical maintenance intervention in the server room. Downtime Schedule (CET): Start: Thursday, January 2nd, 6:00 PM End: Friday, January 3rd, 10:00 AM We apologize for any inconvenience this may cause and thank you for your understanding. Best regards, The Pharo team Ps: Pharo Launcher and smalltalk-ci uses this service to get fresh Pharo images.

1 0

2nd CfP: SLE 2025 - 18th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis Dec. 20, 2024

Dec. 20, 2024

18th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2025) 12-13 June 2025 Koblenz, Germany https://www.sleconf.org/2025/ https://x.com/sleconf ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 18th ACM SIGPLAN International Conference on Software Language Engineering (SLE) which is devoted to the principles of software languages: their design, their implementation, and their evolution. The SLE 2025 conference will be co-located with STAF 2025 and hosted in Koblenz, Germany, on 12-13 June 2025. --------------------------- Important Dates --------------------------- * Abstract submission: Fri 7 Feb 2025 * Paper submission: Fri 14 Feb 2025 * Authors response period: Tue 1 Apr - Sat 5 Apr 2025 * Notification: Tue 15 Apr 2025 * Conference: Thu 12 June - Fri 13 June 2025 (co-located with STAF) All dates are Anywhere on Earth. --------------------------- Topics of Interest --------------------------- SLE covers software language engineering in general, rather than engineering a specific software language. Topics of interest include, but are not limited to: * Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral/executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches - AI-assisted language design and optimisation * Software Language Validation - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages - Model-based testing - AI-assisted validation * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms - AI-assisted refactoring * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and emerging/promising research areas - Generative AI in language engineering (e.g., AI-based language modelling, AI-driven code generation tools) - AI and ML language engineering (e.g., ML compiler testing, code classification) - Quantum language engineering (e.g., language design for quantum machines) - Language engineering for physical systems (e.g., CPS, IoT, digital twins) - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: * Research papers: These are âtraditionalâ papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. * New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. * SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. In this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations, and case study papers on the SLE topics. These can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. * Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. They may optionally include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. Workshops: Workshops will be organised by STAF. Please inform us and contact STAF 2025 organisers if you would like to organise a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the STAF 2025 Website. --------------------------- Submission --------------------------- SLE 2025 has a single submission round for papers, including a mandatory abstract registration and a rebuttal phase, where all authors of research papers will have the possibility of responding to the reviews on their submissions. Authors of accepted research papers will be invited to submit artefacts. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format âacmartâ ( https://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is `\documentclass[sigplan,anonymous,review]{acmart}`. Do not make any changes to this format! Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colours remain distinct and font sizes in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. Accordingly, SLE will follow the double-blind process. Author names and institutions must be omitted from submitted papers, and references to the authorsâ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. The submission website is: https://sle25.hotcrp.com --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy ( https://www.sigplan.org/Resources/Policies/Republication/) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism ( https://www.acm.org/publications/policies/plagiarism-overview) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACMâs general principles, as stated in the ACMâs Publications Policy on Research Involving Human Participants and Subjects ( https://www.acm.org/publications/policies/research-involving-human-particip…) If submissions are found to be violating this policy, they will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning soundness, relevance, novelty, presentation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. SLEBoK papers will be reviewed on their soundness, relevance, originality, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review at the discretion of the PC chairs. For research papers, authors will get a chance to respond to the reviews before a final decision is made. --------------------------- Artefact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artefacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artefacts. --------------------------- Awards --------------------------- * Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished artefact: Award for the artefact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artefact evaluation committee. * Distinguished reviewer: Award for the programme committee member that produced the most useful reviews as assessed by paper authors. * Most Influential Paper: Award for the SLE 2015 paper with the greatest impact, as judged by the SLE Steering Committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. **AUTHORS TAKE NOTE**: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Organisation --------------------------- * General chair: GÃ¶rel Hedin, Lunds Universitet, Sweden * PC co-chair: Regina Hebig, UniversitÃ¤t Rostock, Germany * PC co-chair: Vadim Zaytsev, Universiteit Twente, The Netherlands * Publicity chair: Andrei ChiÅ, feenk gmbh, Switzerland * Local chair: Ralf LÃ¤mmel, UniversitÃ¤t Koblenz, Germany --------------------------- Contact --------------------------- For additional information, clarification, or answers to any questions, please get in touch with the program co-chairs (regina.hebig(a)uni-rostock.de and vadim(a)grammarware.net)

1 0

Pharo News of the Week 51/2024
by Marcus Denker Dec. 20, 2024

Dec. 20, 2024

# Pharo News of the Week 51/2024 - [ANN] pharox-dependency-visualizer: This tool helps understand/untangle dependencies https://github.com/ironirc/pharox-dependency-visualizer - [ANN] A Pharo/Bloc port of the example code from The Nature of Code book by Daniel Shiffman https://github.com/lucretiomsp/nature-of-code-pharo - [ANN] Pharo UFFI binding with the rtmidi library https://github.com/ironirc/pharo-rtmidi - [ANN] Poster from Audio Developer Conference 2024: "Phausto: fast and accessible DSP programming in Pharo" https://hal.science/hal-04813572v1/file/ADC2024-poster.pdf The weekly newsletter takes a break for the rest of the year. We wish already a happy new year and will be back in the second week of January.! # The week on the Pharo Issue Tracker # Pharo 12 - Fix compiler literals p12 #17532 https://github.com/pharo-project/pharo/pull/17532 # VM - Fixes for 10.3.2 #885 https://github.com/pharo-project/pharo-vm/pull/885 - Enhancement(versionning): Extract full semantic version from git #884 https://github.com/pharo-project/pharo-vm/pull/884 # Features - Breakpoints in debugger #920 https://github.com/pharo-spec/NewTools/pull/920 - Sorting items in bag inspector by default #915 https://github.com/pharo-spec/NewTools/pull/915 - Using the dedicated pointers to image #1647 https://github.com/pharo-spec/Spec/pull/1647 # Fixes - Fix: #17531: We can use string instead of symbols in slot in class definition #17531 #17537 https://github.com/pharo-project/pharo/pull/17537 - fix-SDL-default-renderer-by-platform #17517 https://github.com/pharo-project/pharo/pull/17517 # Refactoring Engine - Fix RBClassRegexRefactoring #17552 https://github.com/pharo-project/pharo/pull/17552 - rename asMethodPreamble (dated concept) to asMethodSignature #17547 https://github.com/pharo-project/pharo/pull/17547 - fix #17543: [RB] Comment on RBClassRegexRefactoring and superclass is wrong #17545 https://github.com/pharo-project/pharo/pull/17545 - Cleaning ReDriver #17541 https://github.com/pharo-project/pharo/pull/17541 - Fixing the rename from call site. #17536 https://github.com/pharo-project/pharo/pull/17536 # Compiler - Fix: #17524 MOve OCASTSemanticCleaner to its only user: Reflectivity #17546 https://github.com/pharo-project/pharo/pull/17546 - improve comment of private method scanToken #17539 https://github.com/pharo-project/pharo/pull/17539 - Deprecate IRFix #17538 https://github.com/pharo-project/pharo/pull/17538 - Improving opal comment4 #17530 https://github.com/pharo-project/pharo/pull/17530 - Better comment in opal #17526 https://github.com/pharo-project/pharo/pull/17526 - Deprecate RBParser and RBPatternParser. #17514 https://github.com/pharo-project/pharo/pull/17514 # Comments - Better class comment for commentTestCase #17540 https://github.com/pharo-project/pharo/pull/17540

1 0

Pharo News of the Week 50/2024
by Marcus Denker Dec. 13, 2024

Dec. 13, 2024

# Pharo News of the Week 50/2024 - [ANN] MasterLu is your electronic music teacher in Pharo: https://github.com/lucretiomsp/MasterLu - [ANN] ESUG 2024: Show Us Your Project playlist https://www.youtube.com/playlist?list=PLJ5nSnWzQXi89jwnBCmGPh9xG6shuvuwb # The week on the Pharo Issue Tracker # Fixes - Fix crash of Mac on 4K display #17496 https://github.com/pharo-project/pharo/pull/17496 - Adding fallback code in the allocation primitives basicNewTenured, basicNewTenured: #17492 https://github.com/pharo-project/pharo/pull/17492 - DynamicLoader: unsing LoadLibraryW instead old LoadLibrary in windows #17479 https://github.com/pharo-project/pharo/pull/17479 - Fix #17471: custom Job interruption #17474 https://github.com/pharo-project/pharo/pull/17474 # VM - Fixes for 10.3.2 #885 https://github.com/pharo-project/pharo-vm/pull/885 - Enhancement(versionning): Extract full semantic version from git #884 https://github.com/pharo-project/pharo-vm/pull/884 # Refactoring Engine - Created new driver for tempToIV refactoring #17490 https://github.com/pharo-project/pharo/pull/17490 - Deprecate RBParser and RBPatternParser. #17514 https://github.com/pharo-project/pharo/pull/17514 # CI - Skip some socket tests on windows #17498 https://github.com/pharo-project/pharo/pull/17498 - Fix release tests #17497 https://github.com/pharo-project/pharo/pull/17497 # Documentation - Update README.md #919 https://github.com/pharo-spec/NewTools/pull/919

1 0

Pharo News of the Week 49/2024
by Marcus Denker Dec. 11, 2024

Dec. 11, 2024

# Pharo News of the Week 49/2024 - [New blog] Music and Sounds with Pharo https://lucretiomsp.github.io/musicwithpharo/ - [Blog Post] Phausto at IFC24 https://lucretiomsp.github.io/musicwithpharo/2024/11/24/phaustoIFC24.html # The week on the Pharo Issue Tracker # Fixes - Fix the possibility to put methods as extensions #17489 https://github.com/pharo-project/pharo/pull/17489 - 17487-SignalLogger-should-unsubscribe-on-intance-reset #17488 https://github.com/pharo-project/pharo/pull/17488 - Add tests for safeMethodNameFor:basedOn: and revisit it #17486 https://github.com/pharo-project/pharo/pull/17486 - Do not change the border color of an ImageMorph if it already has a color #17475 https://github.com/pharo-project/pharo/pull/17475 - Fix default behavior of literalEqual: #17467 https://github.com/pharo-project/pharo/pull/17467 - Fixes 17483 on Pharo putting finder in browse menu #918 https://github.com/pharo-spec/NewTools/pull/918 # Spec - add drag transfer customization #1678 https://github.com/pharo-spec/Spec/pull/1678 - Fix implementors of #transferFrom:event: that no longer add #shouldCopy from the TransferMorph to the SpDragAndDropTransfer #1677 https://github.com/pharo-spec/Spec/pull/1677 # Iceberg / Git - Fixes # 1861 on Pharo : location not a git repo when Importing existing clone #1862 https://github.com/pharo-vcs/iceberg/pull/1862 - Pressing enter activates ok action in new branch dialog #1869 https://github.com/pharo-vcs/iceberg/pull/1869 - Enabled cancel button / selected the first option by default ( if the list is not empty ) #1868 https://github.com/pharo-vcs/iceberg/pull/1868 - Fixes #1863 changed title desc for assertion failure #1865 https://github.com/pharo-vcs/iceberg/pull/1865 # Refactoring Engine - refactorings (R) rename method is fixed #17495 https://github.com/pharo-project/pharo/pull/17495 - Extract temp continued #17478 https://github.com/pharo-project/pharo/pull/17478 - Adding comments and protocols reoganisation for RBMethod. #17484 https://github.com/pharo-project/pharo/pull/17484 # VM - Prepare release 10.3.2 #879 https://github.com/pharo-project/pharo-vm/pull/879 - Update README #878 https://github.com/pharo-project/pharo-vm/pull/878 - fix unused-local-typedef #877 https://github.com/pharo-project/pharo-vm/pull/877 - When patching JITed code after become of a class, the class index can look like a negative number #873 https://github.com/pharo-project/pharo-vm/pull/873 - Add default values to --help parameters #872 https://github.com/pharo-project/pharo-vm/pull/872 - Cleanups and improvements #871 https://github.com/pharo-project/pharo-vm/pull/871 # Cleanup - Rename temp var; remove dot after comment #17463 https://github.com/pharo-project/pharo/pull/17463 - Remove some of the last users of SystemAnnouncer uniqueInstance #17372 https://github.com/pharo-project/pharo/pull/17372 - fix a baseline problem #917 https://github.com/pharo-spec/NewTools/pull/917 # Pharo 12 - [Backport] Undo fixes p12 #17309 https://github.com/pharo-project/pharo/pull/17309 - Fix ring global variable #17470 https://github.com/pharo-project/pharo/pull/17470

1 0