May 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

Recent Pharo's seem to lose first keystroke when you swap to them to paste?
by Tim Mackinnon June 1, 2024

June 1, 2024

For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. Tim

7 10

2nd CfP: SLE 2024 - 17th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis May 31, 2024

May 31, 2024

17th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2024) October 20-21, 2024 Pasadena, California, United States --------------------------- Important Dates --------------------------- * Abstract Submissions: Fri 14 Jun, 2024 * Paper Submissions: Mon 24 Jun, 2024 * Authors Response Period: Mon 12 Aug - Sat 17 Aug, 2024 * Authors Notification: Fri 30 Aug 2024 * Conference: Sun 20 October - Mon 21 October 2024 (co-located with SPLASH) All dates are Anywhere on Earth (https://en.wikipedia.org/wiki/Anywhere_on_Earth) ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 17th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2024), held in conjunction with SPLASH 2024. The conference will be hosted in Pasadena, California, United States on October 20-21, 2024. https://www.sleconf.org/2024/ https://2024.splashcon.org/track/sle-2024 Follow us on X: https://x.com/sleconf --------------------------- 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 * Validation of Software Language Tools and Implementations - Verification and formal methods for language tools and implementations - Testing techniques for language tools and implementations - Simulation techniques for language tools and implementations * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * 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 * Domain-Specific Approaches for Any Aspects of SLE (analysis, design, implementation, validation, maintenance) * Empirical Studies and Experience Reports of Tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and Emerging/Promising Research Areas - 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 cyber-physical systems, IoT, digital twins, etc. - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) - Etc. --------------------------- 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. These papers 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 organized by SPLASH. Please inform us and contact the SPLASH organizers if you would like to organize a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the SPLASH 2024 Website. --------------------------- Submission --------------------------- SLE 2024 has a single submission round for papers, including 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 artifacts. --------------------------- 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 colors 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://sle24.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. --------------------------- Artifact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artifacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artifacts. For more information, please see the Artifact Evaluation (https://2024.splashcon.org/track/sle-2024#Artifact-Evaluation) page. --------------------------- Awards --------------------------- Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. Distinguished artifact: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation 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. --------------------------- SLE and Doctoral Students --------------------------- SLE encourages students to submit to the SPLASH doctoral symposium. Authors of accepted doctoral symposium papers on SLE topics will also have the chance to present their work to the SLE audience. --------------------------- Organisation --------------------------- Chairs: * General chair: Ralf LÃ¤mmel, UniversitÃ¤t Koblenz, Germany * PC co-chair: Peter Mosses, Swansea University and Delft University of Technology, Netherlands * PC co-chair: Juliana Alves Pereira, PontifÃcia Universidade CatÃ³lica do Rio de Janeiro, Brazil * Artifact Evaluation co-chair: Johannes HÃ¤rtel, Software Languages Lab, Vrije Universiteit Brussel * Artifact Evaluation co-chair: Sergio Queiroz de Medeiros, Universidade Federal do Rio Grande do Norte * Publicity chair: Andrei Chis, feenk gmbh, Switzerland Program committee * Andrzej WÄsowski, IT University of Copenhagen * Anthony Anjorin, ZÃ¼hlke Engineering GmbH * Benoit Combemale, University of Rennes, Inria, CNRS, IRISA * Bernd Fischer, Stellenbosch University * Di Wang, Peking University * Dimitris Kolovos, University of York * Elias Castegren, Uppsala University * Elizabeth Scott, Royal Holloway University of London * Esther Guerra, Universidad AutÃ³noma de Madrid * Faezeh Khorram, Huawei Technologies * Fernando Magno QuintÃ£o Pereira, Federal University of Minas Gerais * Prof. Fiona Polack, University of Hull * GÃ¶rel Hedin, Lund University * Guido Salvaneschi, University of St. Gallen * JoÃ£o Saraiva, HASLab/INESC TEC, University of Minho * Johannes HÃ¤rtel, Software Languages Lab, Vrije Universiteit Brussel * Judith Michael, RWTH Aachen University * Manuel Wimmer, JKU Linz * Marc Feeley, UniversitÃ© de MontrÃ©al * Michel Steuwer, Technische UniversitÃ¤t Berlin * Paddy Krishnan, Oracle Labs * Ragnar Mogk, Technische UniversitÃ¤t Darmstadt * Riemer van Rozen, CWI * Roberto Ierusalimschy, PUC-Rio * Sergio Queiroz de Medeiros, Universidade Federal do Rio Grande do Norte * Shigeru Chiba, The University of Tokyo * Stefan Marr, University of Kent * Stephen Chong, Harvard University * TamÃ¡s SzabÃ³, GitHub Next * Thomas Degueule, CNRS * Thomas KÃ¼hn, Martin-Luther-University Halle-Wittenberg * L. Thomas van Binsbergen, University of Amsterdam * Tijs van der Storm, CWI & University of Groningen * Walter Cazzola, UniversitÃ degli Studi di Milano --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please get in touch with the program co-chairs (P.D.Mosses at tudelft.nl and Juliana at inf.puc-rio.br).

1 0

This week (22/2024) on the Pharo Issue Tracker
by Marcus Denker May 31, 2024

May 31, 2024

# Pharo 12 - Backport use of icon #smallPharo in #pharoItemsOn: for WorldState and #menuCommandOn: for ProfStef #16695 https://github.com/pharo-project/pharo/pull/16695 # Fixes - fix Reflectivity API #link:toAST: for metaclasses to fix debug points on class-side methods #16701 https://github.com/pharo-project/pharo/pull/16701 - Pharo13 fficalls athens cairo surface #16679 https://github.com/pharo-project/pharo/pull/16679 - Fix a small bug with FFI calls when passing 'NULL' as argument to the C function #16562 https://github.com/pharo-project/pharo/pull/16562 - eflectivity fixing bytecode to ast mapping #16489 https://github.com/pharo-project/pharo/pull/16489 # Improvements - Add libgit 1.8 support for Pharo 13 #86 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/86 - It should be possible to reset a ZnCharacterReadStream #16707 https://github.com/pharo-project/pharo/pull/16707 - Make #withCloseBox and #withPinBox on MenuTitleMorph use a FormSet for the button label #16696 https://github.com/pharo-project/pharo/pull/16696 - fix #needRequestorScope of StDebuggerContextInteractionModel so that its bindings can be used when evaluating code in the debugger #762 https://github.com/pharo-spec/NewTools/pull/762 - Adopt to new spec #761 https://github.com/pharo-spec/NewTools/pull/761 - Adding entry completion setter to SpRequestDialog #1540 https://github.com/pharo-spec/Spec/pull/1540 # Cleanups - Cleanup TraitTest>>#testRemovingTraitsRemoveTraitedClassMethodsWithSubclasses #16717 https://github.com/pharo-project/pharo/pull/16717 - Cleanup ReOverridingExtentsionMethod>>#basicCheck: #16715 https://github.com/pharo-project/pharo/pull/16715 - Fix lint issue on ZnEncodedStream #16713 https://github.com/pharo-project/pharo/pull/16713 - Fix lint issues on ZnEncodedReadStream #16711 https://github.com/pharo-project/pharo/pull/16711 - Cleanup: ZnCharacterEncoder, ZnEncodedStream, ZnEncodedReadStream and ZnEncodedWriteStream should be abstract classes #16709 https://github.com/pharo-project/pharo/pull/16709

1 0

[SOLVED] Shortcut CMD-v for version history
by Davide Varvello May 26, 2024

May 26, 2024

Hi, If you too miss some shortcuts like... cmd-v to show the versions of a method, here is the solution, you have to add methodShortcutActivation to SycShowMethodVersionCommand class: SycShowMethodVersionCommand class >> methodShortcutActivation <classAnnotation> ^ CmdShortcutActivation by: $v meta for: ClyMethod asCalypsoItemContext HTH Cheers Davide

2 2

3D graphics?
by Kasper Osterbye May 24, 2024

May 24, 2024

Cheers all I am looking for classes which can be used to build 3D pictures. Spheres, Boxes, etc. It is a fun thing for me to build, but on the other hand, if it is already done, I will use them. Also, I am interested in 3D figures being outputtet in STL files. Is that done? It is an easier thing for me to build (have done some work already). I want the stl format as I can pass that on to 3D printers. Are there anyone else who have worked from Pharo to 3D printing (prusa for example). Best, Kasper

2 1

This week (21/2024) on the Pharo Issue Tracker
by Marcus Denker May 24, 2024

May 24, 2024

# Pharo 11 backports - P11 - During compilation there are redundant allocation of collections #16485 https://github.com/pharo-project/pharo/pull/16485 # Pharo 12 - Fix for pharo/pharo-project#16677: libgit2 library not listed in LGitLibrary>>#unix64LibraryName #85 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/85 # Fixes - 15652-Check-and-add-test-for--CompiledCodenewFrom #16663 https://github.com/pharo-project/pharo/pull/16663 - Debug points cleaning fixing #16670 https://github.com/pharo-project/pharo/pull/16670 - Change #pharoItemsOn: for WorldState and #menuCommandOn: for ProfStef to use the icon #smallPharo #16496 https://github.com/pharo-project/pharo/pull/16496 # Scriptable Debugger - Migrate to Tonel V3 #97 https://github.com/pharo-spec/ScriptableDebugger/pull/97 - Cleanup: do not use #notNil, use #isNotNil instead #96 https://github.com/pharo-spec/ScriptableDebugger/pull/96 # Rules / Refactoring Engine - Make class abstract driver #16347 https://github.com/pharo-project/pharo/pull/16347 - proposition for a potential new rule: use deny: instead of assert:equals:false #16668 https://github.com/pharo-project/pharo/pull/16668 # Cleanup - Debug point refactoring #757 https://github.com/pharo-spec/NewTools/pull/757 - Remove empty Manifests from baseline packages, synchronize on the tagâ¦ #16537 https://github.com/pharo-project/pharo/pull/16537 - Remove VariableLayout from tests #16686 https://github.com/pharo-project/pharo/pull/16686 - 16680-Zinc-uses-old-Announcers-API #16681 https://github.com/pharo-project/pharo/pull/16681 - 16608 cleanup crown initialize should call super initialize #16676 https://github.com/pharo-project/pharo/pull/16676 - Deprecate RPackageSet #16675 https://github.com/pharo-project/pharo/pull/16675 - Update call to a deprecated class #16671 https://github.com/pharo-project/pharo/pull/16671 - fixes #16610: Cleanup: simple typo in Crown class comment #16666 https://github.com/pharo-project/pharo/pull/16666

1 0

DATE CORRECTION - UKSTUG Meeting - Javier Pimas -- Live Metacircular Runtimes: The case of Egg Smalltalk - 29 May 2024
by UK Smalltalk May 22, 2024

May 22, 2024

Egg is a new Smalltalk dialect that was designed from scratch to incorporate some interesting features: A module system with namespaces that replaces the old-good Smalltalk global. Dynamic identifiers, which are bound lazily similarly to how methods are lazily bound. A multi-VM architecture, with different VM implementations written in C++, Pharo, JavaScript and Egg. The Egg-in-Egg VM is special in that the VM component is just another module of the system, creating what we have named Live Metacircular Runtimes (LMRs) [1]. The most interesting characteristic of LMRs in Smalltalk is that they can be developed using standard Smalltalk tools, which shorten feedback loops when doing VM development. During the talk I'll show a little bit about Egg and its LMR, and how not only VM developers get more productive when writing VMs, but also application developers can better understand what the VM does behind the scenes. [1] https://arxiv.org/abs/2312.16973 - Live Objects All The Way Down: Removing the Barriers between Applications and Virtual Machines Javier Pimas is a fan of high-level low-level programming. He has been successfully mixing Smalltalk and assembly code for more than a decade. Within Bee Smalltalk, SqueakNOS and now Egg Smalltalk projects he has been trying to make live-programming of system-level concerns more practical to application programmers. Javier works for Labware and Quorum Software, where he applies his expertise to real-world challenges while pursuing a PhD in Computer Science at Buenos Aires University. 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/300511322/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

1 0

UKSTUG Meeting - Javier Pimas -- Live Metacircular Runtimes: The case of Egg Smalltalk - 29 June 2024
by UK Smalltalk May 22, 2024

May 22, 2024

Egg is a new Smalltalk dialect that was designed from scratch to incorporate some interesting features: A module system with namespaces that replaces the old-good Smalltalk global. Dynamic identifiers, which are bound lazily similarly to how methods are lazily bound. A multi-VM architecture, with different VM implementations written in C++, Pharo, JavaScript and Egg. The Egg-in-Egg VM is special in that the VM component is just another module of the system, creating what we have named Live Metacircular Runtimes (LMRs) [1]. The most interesting characteristic of LMRs in Smalltalk is that they can be developed using standard Smalltalk tools, which shorten feedback loops when doing VM development. During the talk I'll show a little bit about Egg and its LMR, and how not only VM developers get more productive when writing VMs, but also application developers can better understand what the VM does behind the scenes. [1] https://arxiv.org/abs/2312.16973 - Live Objects All The Way Down: Removing the Barriers between Applications and Virtual Machines Javier Pimas is a fan of high-level low-level programming. He has been successfully mixing Smalltalk and assembly code for more than a decade. Within Bee Smalltalk, SqueakNOS and now Egg Smalltalk projects he has been trying to make live-programming of system-level concerns more practical to application programmers. Javier works for Labware and Quorum Software, where he applies his expertise to real-world challenges while pursuing a PhD in Computer Science at Buenos Aires University. 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/300511322/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

1 0

[ANN] Package Formulas v1
by HernÃ¡n Morales Durand May 17, 2024

May 17, 2024

Hi everyone. I've updated package formulas to work with Pharo 12 and Pharo 13. You can find the project here: https://github.com/hernanmd/package-formulas Let me know if there's any features you would like to see implemented. Cheers, HernÃ¡n

1 0