October 2024 - 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

UKSTUG meeting - Mariano Guerra / Tudor GÃ®rba: - 30 October 2024 @ 7pm GMT
by UK Smalltalk Oct. 27, 2024

Oct. 27, 2024

Join us for an engaging session on the latest in Generative AI and Large Language Models (LLMs), featuring two insightful presentations. *Introduction to Large Language Models and Gloodata* *Speaker: Mariano Guerra* Mariano will walk us through the fundamentals of LLMs and provide a behind-the-scenes look at building the Gloodata application. *A Unique Perspective on LLMs* *Speaker: Tudor Girba* Tudor will offer a distinct view on LLMs, showcasing demos based on GT that highlight their innovative approach. 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/303944944 <https://www.meetup.com/ukstug/events/303944944>) to receive the meeting details. Donât forget to bring your laptop and drinks! [1] http://gloodata.com [2] https://feenk.com PS: we have uploaded the videos for past presentations today. Christian Haider on Values -- https://vimeo.com/ukstug/values <https://vimeo.com/ukstug/values> Javier Pimas on Live Metacircular Runtimes -- https://vimeo.com/ukstug/pocho David Buck on Beagle Smalltalk -- https://vimeo.com/ukstug/beagle

1 0

ARM64
by philip hunt Oct. 25, 2024

Oct. 25, 2024

I'm a newbie so I apologize in advance if this is not the right way to ask my question. I did spend time on dotORG but its rather large and intimidating to find the answers to SIMPLE issues. I have followed Pharo since version 3 and way before that SmalltalkV and even earlier systems - so let me say how impressive the work of the Pharo team is. this is a fantastic product. I've run it on W7-W11 and Ubuntu all on x86 architecture machines. Now I'm running a new Snapdragon X elite laptop W11 and to my surprise I downloaded Pharo (and used the windows version)...I thought that windows PRISM would work, it didn't (for me)...so I edited the exe properties to use SAFE mode (also I tried the others, strict, very strict, too) but although the launcher seems to start ok, I get to the file picker for the image and then nothing. Please educate me here, what am I missing (something simple?) is there a version compiled for ARM64 on W11 ? Or am I going to run using emulation? Its probably rather simple, I hope so... Thank you for any help or pointers you can give me. Phil

3 2

This week (43/2024) on the Pharo Issue Tracker
by Marcus Denker Oct. 25, 2024

Oct. 25, 2024

# News of the Week 42 - [VIDEO] When companies code with Pharo https://www.youtube.com/watch?v=VtRyJnBmEE0 - [ANN] Pharo tree-sitter: https://github.com/badetitou/Pharo-Tree-Sitter - [ANN] BlocIM: IM support for Bloc/Pharo https://github.com/tomooda/BlocIM - [ESUG2024] day one Videos are now in the playlist: https://www.youtube.com/playlist?list=PLJ5nSnWzQXi-uyYOZIVgXg1up_bclQc7e # This week (43/2024) on the Pharo Issue Tracker # Pharo 12 - Moving cursor and stop on upper cases #17297 https://github.com/pharo-project/pharo/pull/17297 # Features / Improvements - Improvements in undo/redo #17305 https://github.com/pharo-project/pharo/pull/17305 # Fixes - Fix export settings #17273 https://github.com/pharo-project/pharo/pull/17273 - Fix renaming protocol with no method #17282 https://github.com/pharo-project/pharo/pull/17282 - Using the stable VM instead of latest, there is an issue in the VM. #17287 https://github.com/pharo-project/pharo/pull/17287 - 17250 debug session cannot update their exception and then provides the debugger incorrect information about the execution state #17288 https://github.com/pharo-project/pharo/pull/17288 - Fix repeat events #17301 https://github.com/pharo-project/pharo/pull/17301 # Tools - Add missing callbacks for setting checkboxes and droplists #871 https://github.com/pharo-spec/NewTools/pull/871 - sort playground pages by modification time #870 https://github.com/pharo-spec/NewTools/pull/870 - Put back correct refresh icon in inspectors #869 https://github.com/pharo-spec/NewTools/pull/869 - merge P13 spec actions #867 https://github.com/pharo-spec/NewTools/pull/867 # Spec - Setter of unfilteredItems #1629 https://github.com/pharo-spec/Spec/pull/1629 - merge P13 spec actions #1628 https://github.com/pharo-spec/Spec/pull/1628 - merge P13 spec actions #1849 https://github.com/pharo-vcs/iceberg/pull/1849 # Refactoring Engine - Migrate Rename Temporary to use the Driver architecture #17300 https://github.com/pharo-project/pharo/pull/17300 - 17280 refactorings cannot use generate accessors #17292 https://github.com/pharo-project/pharo/pull/17292 # Cleanup - Simplify progress bar theme management #17283 https://github.com/pharo-project/pharo/pull/17283 - restore Pharo13 branch to iceberg #17306 https://github.com/pharo-project/pharo/pull/17306 - restore Pharo13 branches for NewTools and Spec #17290 https://github.com/pharo-project/pharo/pull/17290 - Rename RBAbstractTransformation ReAbstractTransformation, RBRefactoriâ¦ #17302 https://github.com/pharo-project/pharo/pull/17302

1 0

installation problem
by ilikemytandem＠gmail.com Oct. 21, 2024

Oct. 21, 2024

Iâve downloaded and installed PharoLauncher on an old MacBook Air (intel). When I try to run it I get the following error:\ \ PrimitiveFailed: primitive #createDirectory: in MacStore failed I assume itâs a permissions problem, but I donât know how to fix it.\ \ Any suggestions?\ \ Tnx, Phil

1 0

This week (42/2024) on the Pharo Issue Tracker
by Marcus Denker Oct. 18, 2024

Oct. 18, 2024

# News of the Week 42 I think we can use the mail to have not just the issue tracker summary, but other kind of news, too. (If you have ideas what to add here or want to announce something, send me a mail) - [ESUG2024] Videos of ESUG are now being posted at https://www.youtube.com/@esugboard, subscribe and enable notifications to not miss them - [ESUG2024] All Slides are now on Slideshare https://slideshare.net/esug/presentations, PDFs are in the ESUG Archive: http://archive.esug.org/ - [ANN] BlocEmoji: enable emoji on Bloc/Pharo https://github.com/tomooda/BlocEmoji - [ANN] Stash is a serializer for Pharo that generate source-code: https://github.com/Nyan11/Stash - [Blog Post] 10 Billion Integers Walk Into an Array https://donraab.medium.com/10-billion-integers-walk-into-an-array-37097386c… # This week (42/2024) on the Pharo Issue Tracker And here the PRs merged this week: # VM - Fixing cygpath conversion for newer version of cmake #860 https://github.com/pharo-project/pharo-vm/pull/860 - Improving Implementation of CompositeImageFormat and PermanentSpace #855 https://github.com/pharo-project/pharo-vm/pull/855 # Fixes - reintroduce waitTimeoutMSecs: #17279 https://github.com/pharo-project/pharo/pull/17279 - Restore the Calypso tab copy button to copy method name(s) to Clipboard #17260 https://github.com/pharo-project/pharo/pull/17260 - Correct evaluation of dynamic variables from the debugger #854 https://github.com/pharo-spec/NewTools/pull/854 # Refactoring Engine - Fix Pull Up precondition bug #17274 https://github.com/pharo-project/pharo/pull/17274 - Updates during mutation testing #17269 https://github.com/pharo-project/pharo/pull/17269 - Fix ALL refactoring related failing and skipped tests #17266 https://github.com/pharo-project/pharo/pull/17266 - Rename inst var renames accessors #17265 https://github.com/pharo-project/pharo/pull/17265 - Use allNonMetaClasses in Duplicate Class driver #17263 https://github.com/pharo-project/pharo/pull/17263 # Tools - Support methods for the new setting browser #17268 https://github.com/pharo-project/pharo/pull/17268 - Remove dialog usage from setting button presenter. #864 https://github.com/pharo-spec/NewTools/pull/864 - 858 debugger add an inspect button to the actual vs expected view #861 https://github.com/pharo-spec/NewTools/pull/861 # Spec - Adapt to actiongroups #17144 https://github.com/pharo-project/pharo/pull/17144 - Add missing selectedItems method #1624 https://github.com/pharo-spec/Spec/pull/1624 - Fix slider #1619 https://github.com/pharo-spec/Spec/pull/1619 # Cleanup - Remove hardcoded SystemAnnouncer in System-Sources #17179 https://github.com/pharo-project/pharo/pull/17179 - method categorization fix https://github.com/pharo-project/pharo/pull/17271

1 0

This week (41/2024) on the Pharo Issue Tracker
by Marcus Denker Oct. 11, 2024

Oct. 11, 2024

# Pharo 12 - Pharo12: update spec to v1.3.3 #17245 https://github.com/pharo-project/pharo/pull/17245 - update to spec version 1.3.2 #17208 https://github.com/pharo-project/pharo/pull/17208 - update spec version to 1.3.1 #17207 https://github.com/pharo-project/pharo/pull/17207 - Set enablement of button in SpCommand>>#configureAsButtonOfClass: #1621 https://github.com/pharo-spec/Spec/pull/1621 - Add SpMenuPresenter>>#fillWith: that applies for SpMenuBarPresenter as well, and add tests and example #1611 https://github.com/pharo-spec/Spec/pull/1611 # Fixes - Include only bare addresses in MailMessage>>recipientList as needed byy SMTPClient (fixes #17240) #17241 https://github.com/pharo-project/pharo/pull/17241 - 17139-isInClassHierarchyOf-does-not-work-for-Metaclasses #17237 https://github.com/pharo-project/pharo/pull/17237 - Fix #17170: DrTest does not set the /pass/error/failure state on the test method (in systemBrowser) #17184 https://github.com/pharo-project/pharo/pull/17184 # Improvements / Feature - Speed up some Package code #17200 https://github.com/pharo-project/pharo/pull/17200 - Improve word-by-word text navigation + tests #17183 https://github.com/pharo-project/pharo/pull/17183 - Adding the generation of a preference file from Pharo First version without the possibility to edit it. #17187 https://github.com/pharo-project/pharo/pull/17187 - Set enablement of button in SpCommand>>#configureAsButtonOfClass: #1622 https://github.com/pharo-spec/Spec/pull/1622 # Refactoring Engine - Fix Generate accessors does not work anymore in the source code pane #17246 https://github.com/pharo-project/pharo/pull/17246 - Cleaning monolithic extract method #17242 https://github.com/pharo-project/pharo/pull/17242 - [Refactorings] Fix classes and traits iteration API #17201 https://github.com/pharo-project/pharo/pull/17201 - Fixing rb tests #17214 https://github.com/pharo-project/pharo/pull/17214 - Fixing pull up refactoring #17215 https://github.com/pharo-project/pharo/pull/17215 - Clean pull up more #17228 https://github.com/pharo-project/pharo/pull/17228 - 17222 rb should revisit check superclass in pull up #17236 https://github.com/pharo-project/pharo/pull/17236 # Tests - Add tests for optimization rules #16913 https://github.com/pharo-project/pharo/pull/16913 # Cleanup - Remove Calypso dependencies #851 https://github.com/pharo-spec/NewTools/pull/851 - Remove senders of scaledByDisplayScaleFactor and displayScaleFactor #852 https://github.com/pharo-spec/NewTools/pull/852 - Remove senders of scaledByDisplayScaleFactor and displayScaleFactor #1610 https://github.com/pharo-spec/Spec/pull/1610 - Migrated Calypso "Extra" method menu items to Commander 2 #17243 https://github.com/pharo-project/pharo/pull/17243 - fix the boring dependency tests #17221 https://github.com/pharo-project/pharo/pull/17221 - Migrating Gx -> x icon names #17210 https://github.com/pharo-project/pharo/pull/17210 - Migrating Gx -> x icon names #855 https://github.com/pharo-spec/NewTools/pull/855 - Migrating Gx -> x icon names #1617 https://github.com/pharo-spec/Spec/pull/1617 - Cleaning of #dialog: method in GraphicFontSettings #17159 https://github.com/pharo-project/pharo/pull/17159 - Detach Calypso navigation model #17174 https://github.com/pharo-project/pharo/pull/17174

1 0

1st CfP: SLE 2025 - 18th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis Oct. 9, 2024

Oct. 9, 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

This week (40/2024) on the Pharo Issue Tracker
by Marcus Denker Oct. 4, 2024

Oct. 4, 2024

# Pharo 12 - [Backport] adding a nice documentation about the fluid class definition syntax #17154 https://github.com/pharo-project/pharo/pull/17154 # Fixes - Fix bug in loading of methods that failed to load before #17199 https://github.com/pharo-project/pharo/pull/17199 - Fix default value for âZoom factorâ setting #17192 https://github.com/pharo-project/pharo/pull/17192 - 17059 Update ReGuardClauseRule severity #17182 https://github.com/pharo-project/pharo/pull/17182 - [CI] Fix Refactoring related tests failing on the CI #17165 https://github.com/pharo-project/pharo/pull/17165 # Improvements - Introduce SpMenuPresenter>>#fillWith: and add tests and example #1602 https://github.com/pharo-spec/Spec/pull/1602 - Add a simple code file editor so that we can use it for the preferences. #1612 https://github.com/pharo-spec/Spec/pull/1612 - Differentiate Morph scale factor from World zoom factor. #17172 https://github.com/pharo-project/pharo/pull/17172 - Add some useful methods on Color #17176 https://github.com/pharo-project/pharo/pull/17176 - Improve the Duplicate class refactoring #17180 https://github.com/pharo-project/pharo/pull/17180 # Cleanup - Remove unused sound support #17186 https://github.com/pharo-project/pharo/pull/17186 - Move NumberParsingTests to NumberParser-Tests package #17181 https://github.com/pharo-project/pharo/pull/17181 - Deprecate BlockClosure>>#valueWithoutNotifications #17178 https://github.com/pharo-project/pharo/pull/17178 - Cleanup: remove not used SystemSettingLauncher #17177 https://github.com/pharo-project/pharo/pull/17177 - Cleanup: unify printing CleanBlockClosure #17173 https://github.com/pharo-project/pharo/pull/17173

1 0