April 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

Getting started with the easy projects
by Richard O'Keefe May 17, 2024

May 17, 2024

https://github.com/orgs/pharo-project/projects/8 lists some easy projects. I'd like to make a contribution. Where are the instructions on how to sign up and what to do? Fair warning, I'll probably need a bit of hand-holding...

3 6

Open Call: Object-Centric Breakpoints experiment
by Steven Costiou May 14, 2024

May 14, 2024

Dear Community, as part of a research project in the EVREF team, we are looking for people to participate to an empirical experiment on object-centric breakpoints - a debugging tool present in Pharo 9. Many people from the community already participated, and we thank them very much ð We are still looking for participants, we need 40 people to do the experiment! Please help us, in return it helps us understand better our tools and their impact and therefore build better tools for the Pharo community! For those who want to know a bit more, see my original email below. For those who just want to jump at the experiment, you can go there https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd Thanks in advance ð Steven. --- We would like to invite you to participate to our experimental study on Object-Centric Breakpoints. This study aims to evaluate and to understand how Object-Centric Breakpoints impacts the debugging activity. This experiment takes place in **Pharo 9**. In this experiment, we ask you to solve 2 debugging tasks, one with standard Pharo tools and one other with Object-Centric Breakpoints. Between the two tasks, you will have to follow a tutorialand warmup tasks to learn how to use the tool. **How to Participate:** All instructions are here, please read them carefully: https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd **About the Experiment:** The experiment last between 40 minutes and 2 hours. Participants should have experience with Pharo development and debugging. We recommend having more than 6 months experience in Pharo and debugging in general. You will gain insights into the Object-Centric Breakpoints approach and contribute to advancements in debugging research. Help us to build better debugging tools that help you debug! **Some constraints:** - You are not allowed to load external tools and baselines, but you can use anything that is in the base image - Please do the experiment in one shot if possible without interruptions - The experiment sends anonymous data to our inria server, please make sure that you have a valid internet connection - Please try to use the object-centric breakpoints when the experimental framework asks you to **Notes:** Participation is voluntary, and everything is anonymous. You can abandon the experiment at any point (and your data will be discarded). For any question, you can contact us: steven.costiou(a)inria.fr and valentin.bourcier(a)inria.fr Thank you for considering participating in our study. Your contribution will be valuable in advancing the field of debugging and helping us understand what tools we need to build for Pharo. Sincerely, Steven and Valentin, EVREF team, Inria

1 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

[ANN] Pharo 12 Release !
by Esteban Lorenzano May 8, 2024

May 8, 2024

Dear Pharo users and dynamic language lovers: We have released Pharo <https://pharo.org/> version 12! What is Pharo? Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. * Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. * Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! * Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! * Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. * Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> ... more on the Pharo Features page <http://www.pharo.org/features>. In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo120Chang…> Some highlights of this amazing version: Highlights New breakpoint system The debug point system is a breakpoint model that supersedes the previous implementation of breakpoints and watchpoints. They are configurable, composable, and extensible. The traditional breakpoints remain available, including conditional breakpoints, one-time breakpoints, and object-centric breakpoints. Additionally, there are new types of breakpoints, such as chained-breakpoints, which condition the activation of certain breakpoints on the triggering of others (e.g., breakpoint B only activates if breakpoint A is hit first). Debug points also feature a dedicated browser and integration options. Tools * Scalable fluid class syntax is now the default one * Preparing the introduction of the Bloc graphic system by migrating more tools to Spec2 widgets * Spec2 UI framework enhancements to support GTK 4 * Leaner version of the Metacello package manager * More robust and strict mode for FFI System * New architecture for refactorings and domain specific transformations * Code loading speed improvement * Fast browsing via fully optimized package tags * Optmized memory usage via optimized method protocols * Compiler simplifications and improvements Virtual machine * Massive image support with permanent space * String/ByteArray comparison speed up Development Effort This new version is the result of 1895 Pull Requests integrated just in the Pharo repository. We have closed 865 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: * http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> * http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> * http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> * http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> * http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> * http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> * http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> * http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> Contributors We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 12.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. The Pharo Team Discover Pharo: https://pharo.org/features Try Pharo: http://pharo.org/download <https://pharo.org/download> Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation>

5 4

[Success Story] Support Wizard by Thales
by Marcus Denker April 30, 2024

April 30, 2024

Support Wizard by Thales =================== Support Wizard is an application developped by Pierre Laborde and Eric Le Pors, Global Design and Innovation Leaders at Thales. It is using the latest technological innovations from Pharo to create native and high-performance desktop human-machine interfaces (Bloc graphics engine, Toplo libraries and OS tools). The application is structured with the open-source component architecture framework Molecule. The simplicity and speed of production offered by Pharo and the power of its language allows Thales to focus our efforts on ergonomics and graphic design of the application to offer the best possible user experience. Link (with more infos): https://www.pharo.org/success/Thales-SupportWizard.html Youtube Video: https://www.youtube.com/watch?v=t5qaFM2F3J0

1 0

1st CfP: SLE 2024 - 17th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis April 29, 2024

April 29, 2024

------------------------------------------------------------------------ 17th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2024) October 20-25, 2024 Pasadena, California, United States http://www.sleconf.org/2024/ https://2024.splashcon.org/track/sle-2024 Follow us on X: https://x.com/sleconf ------------------------------------------------------------------------ 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-25, 2024. --------------------------- 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. --------------------------- Important Dates --------------------------- All dates are Anywhere on Earth (http://en.wikipedia.org/wiki/Anywhere_on_Earth) * 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 - Fri 25 October 2024 (co-located with SPLASH, precise dates to be announced) --------------------------- 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 * Publicity chair: Andrei Chis, feenk gmbh, Switzerland --------------------------- 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

Re: [Esug-list] [ANN] Pharo 12 released !
by stephane ducasse April 26, 2024

April 26, 2024

Thanks to all the team and contributors for this cool release. S > On 26 Apr 2024, at 12:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 12! > > What is Pharo? > > Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. > > > > Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. > Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! > Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! > Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. > Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo120Chang…> > Some highlights of this amazing version: > > Highlights > > New breakpoint system > > The debug point system is a breakpoint model that supersedes the previous implementation of breakpoints and watchpoints. They are configurable, composable, and extensible. The traditional breakpoints remain available, including conditional breakpoints, one-time breakpoints, and object-centric breakpoints. Additionally, there are new types of breakpoints, such as chained-breakpoints, which condition the activation of certain breakpoints on the triggering of others (e.g., breakpoint B only activates if breakpoint A is hit first). Debug points also feature a dedicated browser and integration options. > > > > Tools > > Scalable fluid class syntax is now the default one > Preparing the introduction of the Bloc graphic system by migrating more tools to Spec2 widgets > Spec2 UI framework enhancements to support GTK 4 > Leaner version of the Metacello package manager > More robust and strict mode for FFI > System > > New architecture for refactorings and domain specific transformations > Code loading speed improvement > Fast browsing via fully optimized package tags > Optmized memory usage via optimized method protocols > Compiler simplifications and improvements > Virtual machine > > Massive image support with permanent space > String/ByteArray comparison speed up > Development Effort > > This new version is the result of 1895 Pull Requests integrated just in the Pharo repository. We have closed 865 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: > > http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> > http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> > http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> > http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> > http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> > http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> > http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> > http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> > Contributors > > We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 12.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > > Try Pharo: http://pharo.org/download <https://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation> > > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

1 0

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

April 26, 2024

We finally released Pharo 12! Find the announcement here: https://www.pharo.org/news/2024-04-26-pharo12-released.html Last week we merged quite some fixes that where tagged as release critical. And of course some small cleanups. We have opened the Pharo 13 branch, new changes will from now on go there and we back-port important fixes. # Pharo 12 Release fixes - Release waiting processes when destroying a socket (without ThreadedFFI dependency) #16172 https://github.com/pharo-project/pharo/pull/16172 - P12 external projects fix repository versions #16509 https://github.com/pharo-project/pharo/pull/16509 - Adding a Calypso class to display the Debug Points menu group in the method list context menu #16507 https://github.com/pharo-project/pharo/pull/16507 - FFI_i386>>#newCallbackArgumentReaderForCallback:inContext: into "callbacks" like any other #16505 https://github.com/pharo-project/pharo/pull/16505 - Clean System-Announcements-Tests #16503 https://github.com/pharo-project/pharo/pull/16503 - Athens Demo not working #16502 https://github.com/pharo-project/pharo/pull/16502 - Remove some users of SystemAnnoucer class>>#uniqueInstance #16498 https://github.com/pharo-project/pharo/pull/16498 - Remove calypso context from search dialogs #16493 https://github.com/pharo-project/pharo/pull/16493 - Revert "Fix for Wrong focus in Calypso Find Class Dialog causes exception" #16492 https://github.com/pharo-project/pharo/pull/16492 - Changed the description when trying to delete a class. #16491 https://github.com/pharo-project/pharo/pull/16491 - Issue 16462: Find and replace setup is quadruplicated in the context menu #16490 https://github.com/pharo-project/pharo/pull/16490 - Fix 16345: serialization of classes with traits in hierarchy #16487 https://github.com/pharo-project/pharo/pull/16487 - During compilation there are redundant allocation of collections #16486 https://github.com/pharo-project/pharo/pull/16486 - fixes #16362: Abstract instance variables DNU #16482 https://github.com/pharo-project/pharo/pull/16482 - Add setting to set the world renderer canvas scale factor automatically #16479 https://github.com/pharo-project/pharo/pull/16479 - Font-Tests: #testIsAbstractClass should be testIsAbstract like in othâ¦ #16477 https://github.com/pharo-project/pharo/pull/16477 - Added the compare methods to all the byte array classes so they use the new primitiveCompareBytes #16461 https://github.com/pharo-project/pharo/pull/16461 - Fix: rename method loop #16444 https://github.com/pharo-project/pharo/pull/16444 # Pharo 13 - P13 use branch repository #16519 https://github.com/pharo-project/pharo/pull/16519 - add Open as external window option #16511 https://github.com/pharo-project/pharo/pull/16511 - Add rule for Point x: x y: y -> x@y #16508 https://github.com/pharo-project/pharo/pull/16508 - Rename SqueakEpoch to Epoch #16418 https://github.com/pharo-project/pharo/pull/16418

1 0

Re: [Esug-list] [ANN] Pharo 12 released !
by Norbert Hartl April 26, 2024

April 26, 2024

1 0

[ANN] docker-pharo-vm v10.1.0-2024-04-25 [v10.1.0 [2024-04-25]] released!
by Buenos Aires Smalltalk April 25, 2024

April 25, 2024

1 0

[ANN] Soil release v1
by Norbert Hartl April 24, 2024

April 24, 2024

...we said at last ESUG that there will be a release soonish but as usual it doesn't go that fast. But now we are very happy to announce that Soil has a first public release v1. So what is soil? Soil is an object oriented database in pharo <http://pharo.org/>. It is transaction based having ACID transactions. It has binary search capabilities with SkipList and BTree+ indexes. It aims to be a simple yet powerful database making it easy to develop with, easy to debug with, easy to inspect, ... More details at https://github.com/ApptiveGrid/Soil This release is still considered early stage because although in ApptiveGrid there are over 4000 instances of it and there are other users there isn't a wider range of use cases, yet. So it is not fully battle tested. This just as reminder when you start compaining I need somewhere to point my finger to and say "I told you!" ;) there are few things missing that you might expect like garbage collection, etc. So but it is definetely usable and awaiting the brave ones of you to try. Hopy you enjoy it! Norbert & Marcus

2 1

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

April 23, 2024

# Bugs - Fix bug while adding a trait to a class without trait #16473 https://github.com/pharo-project/pharo/pull/16473 - Restore fileIn button in File Browser #16470 https://github.com/pharo-project/pharo/pull/16470 - Do not select the # in symbol selection #16469 https://github.com/pharo-project/pharo/pull/16469 - 16447-Dropping-window-outside-of-Pharo-window-borders-closes-the-window #16467 https://github.com/pharo-project/pharo/pull/16467 - 16355-Wrong-class-definition-creates-strange-DNUs #16466 https://github.com/pharo-project/pharo/pull/16466 - Fix: PullUpClassVar was not checking breaking change preconditions #16464 https://github.com/pharo-project/pharo/pull/16464 - fix access to false positive in Renraku #16457 https://github.com/pharo-project/pharo/pull/16457 - Fix #visitBehaviorRepackagedChange: on EpHasImpactVisitor to send #not instead of #y #16449 https://github.com/pharo-project/pharo/pull/16449 - 16365 Add subclass can create trait subclasses #16442 https://github.com/pharo-project/pharo/pull/16442 - Clean package generation of "Jump to test class" #16434 https://github.com/pharo-project/pharo/pull/16434 - Add LibTTY providing access to the VM library for spawning a process connected to a pseudo-terminal #16427 https://github.com/pharo-project/pharo/pull/16427 - fix: Socket>>#waitForSendDoneFor: does not return a boolean (but ZdcSocketStream expects it to) #16425 https://github.com/pharo-project/pharo/pull/16425 - Update the Playground shortcut #16422 https://github.com/pharo-project/pharo/pull/16422 - Fix code highlighting in debug points browser, for debug points set on AST node #726 https://github.com/pharo-spec/NewTools/pull/726 - fix layouts #1539 https://github.com/pharo-spec/Spec/pull/1539 - Adding textChanged notification to SpStringTableColumn #1360 https://github.com/pharo-spec/Spec/pull/1360 # Cleanup - Removing old object-centric breakpoint's integration to the inspector #733 https://github.com/pharo-spec/NewTools/pull/733 - Changed protocol for displayStringOn: to displaying #737 https://github.com/pharo-spec/NewTools/pull/737 - Change superclass of StDebuggerTest from TestCase to SpBaseTest #740 https://github.com/pharo-spec/NewTools/pull/740 - Removing old breakpoint system's integration to Calypso #16397 https://github.com/pharo-project/pharo/pull/16397 - reuse of #isFalsePositive:forRuleId:versionId: in #falsePositiveOf: #16475 https://github.com/pharo-project/pharo/pull/16475

1 0

UKSTUG meeting - Tudor GÃ®rba: What exactly is Glamorous Toolkit? - 24 April 2024
by UK Smalltalk April 22, 2024

April 22, 2024

To some people Glamorous Toolkit is a Pharo environment. To others itâs a knowledge management system. Others might see a code analysis platform, a data visualization or an API browsing tool. Yet others see the graphical stack with its interactive editors. Glamorous Toolkit is all of these. But itâs really also none of these. These are merely examples of the many forms the environment can be molded to. And there can be many more. Glamorous Toolkit is primarily an environment that makes it possible to create many experiences seamlessly and contextually. This then leads to a new way of programming that we call Moldable Development. Tudor GÃ®rba is a software environmentalist and the CEO of feenk.com ( http://feenk.com/ ) where he works with an amazing team to make the inside of systems explainable. Much of the work is embodied in Glamorous Toolkit ( gtoolkit.com) a novel environment that enables moldable development. 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/300575234/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

1 0

How to log pharo output to stdio safely?
by Tim Mackinnon April 20, 2024

April 20, 2024

Hi - I've been messing around with deploying a hobby pharo app to the web.. which has become a lot simpler over the years, although the tech keeps changing and you have to relearn things. Anyway, I have my image in one of the wonderful BA Docker containers, and it runs well - and the host I'm using will show the logs for you, so you can figure out what is going on... well that is if your logs come out properly (and of course, if it gets really hairy then you can get a VNC session onto the image and figure stuff out) So logs are handy, and pharo these days has a nice headless mode that redirects the Transcript to stdout - and there are also a few decent logging frameworks as well. But as most things go to the Transcript, and that goes to stdout - it should be good. HOWEVER - flushing is the killer, as if things happen and the last thing goes wrong, but the output isn't flushed, then you aren't going to see it. So my question is how to properly flush? And I'm sure I've read something about this before, but I can't find it. >From memory, you often need to have a Transcript cr. to flush your last line. BUT, most things in the image seem to use "self crTrace:" these days, which is a cr to ensure the previous msg is separated from what you want to write, and then you write your line out. However, as there is now cr - you might not see it. So I tried changing my stuff to use "self traceCr:" (which is in the image), and that still didn't seem to work - the last failing line wasn't being output. Worse still, its confusing, as many things in the image are using crTrace: and so you get intermingled messages, which are hard to decipher. So I tried: Transcript cr; show: msg; flush But that didn't seem to work (which I don't understand) Eventually I did: Transcript show: msg; cr; flush And this seems to ensure things do reliably get outputted - but I'm wondering if anyone can shed light on this areas? Ideally I want to use: Transcript cr'; show: msg; flush As this plays much better with everything that is in the image - but is there some way to do this? And indeed, will log tools the Bettersatack or papertail play ball with output like this (as I guess they operate on complete lines to interpret log levels etc), Anyway - I'm curious if anyone else has done work in this area to shed light? Thanks, Tim As an aside - for deployment - several years ago I came across dockerize.io - which lets you upload a Docker image to a host, and it will run it for you. Sadly that service didn't survive... but there are quite a few like it now, and so I'm trying Render.com - which is similar, but the twist is you need to store a Docker image in a registry somewhere (I use gitlab from my CI pipeline), and then it will retrieve it and run it for you (for either free in 40 minute chunks, or for $7/m - which is pretty good, and possibly bit simpler than Digital Ocean). Its pretty cool, and maybe I will write up about it sometime

6 6

[ANN] docker-pharo-runtime v11.0.0-2024-04-18 [v11.0.0 [2024-04-18]] released!
by Buenos Aires Smalltalk April 18, 2024

April 18, 2024

1 0

[ANN] docker-pharo-vm v10.1.0-2024-04-18 [v10.1.0 [2024-04-18]] released!
by Buenos Aires Smalltalk April 18, 2024

April 18, 2024

1 0

remove breakpoint ?
by Haroldo Stenger April 14, 2024

April 14, 2024

hi nice pharo people I'm doing my very initial attempts in Pharo. Having read something here and there. Now I've put myself to subclass BlElement in order to add a method of myself to this subclass. The subclass got named 'Circulo'. Then I had a hard time trying to create a protocol to 'host' it, but finally it got created as protocol 'a'. Initially it got created in the third pane in the browser, below without any apparent 'breakpoint hierarchy'. However, as soon as I wrote the method and got to save/accept it, something strange happened, namely, 'brakepoint' protocol was created out of nothing , and my 'a' protocol was put under it. The method itself in the fourth pane, has a red ! sign. If I right click on the method, and try to remove the breakpoint, it does nothing. What happens this and how can I have a normal situation , since I did not put breakpoints ? Thanks for your kind help

2 3

This week (15/2024) on the Pharo Issue Tracker
by Marcus Denker April 12, 2024

April 12, 2024

# Speed - 16407-RBNodes-errorNotices-creates-unneeded-empty-collections #16408 https://github.com/pharo-project/pharo/pull/16408 # Bug Fixes - Fix Preview Settings Browser: does not open when a custom setting is used #734 https://github.com/pharo-spec/NewTools/pull/734 - Remove async playground doits #735 https://github.com/pharo-spec/NewTools/pull/735 - Fix issue while trying to display file setting items #736 https://github.com/pharo-spec/NewTools/pull/736 - quick fix that hide the debug context menus when there are unsaved changes #16382 https://github.com/pharo-project/pharo/pull/16382 - Fix Generate Equals and Hash DNU #16384 https://github.com/pharo-project/pharo/pull/16384 - Fix for Wrong focus in Calypso Find Class Dialog causes exception #16386 https://github.com/pharo-project/pharo/pull/16386 - Provide a default String for settings without #default: sends. #16400 https://github.com/pharo-project/pharo/pull/16400 - fix MethodConstantTest #16405 https://github.com/pharo-project/pharo/pull/16405 - fix enum type initialization on structures #16406 https://github.com/pharo-project/pharo/pull/16406 - Do not suggest trait when deprecating a class #16409 https://github.com/pharo-project/pharo/pull/16409 - 16366 Insert superclass refactoring is allowed on trait and gives DNU #16413 https://github.com/pharo-project/pharo/pull/16413 - 16423-Scrolling-always-acts-as-if-macOS-option-Use-inertia-when-scrolling-is-turned-off #16426 https://github.com/pharo-project/pharo/pull/16426 - Fix Refactorings should have help menus to explain their actions #16421 https://github.com/pharo-project/pharo/pull/16421 - Reposition Calypso contextual class menu items #16420 https://github.com/pharo-project/pharo/pull/16420 # Improvements - Add support for Epicea file out #16401 https://github.com/pharo-project/pharo/pull/16401 - Add Toplo world menu entry #16429 https://github.com/pharo-project/pharo/pull/16429 # UI - Exclude some commands from virtual method groups on Calypso #16404 https://github.com/pharo-project/pharo/pull/16404 - fix enter/escape behavior on dialogs #1537 https://github.com/pharo-spec/Spec/pull/1537 - Improving the behavior in all the dialogs #1536 https://github.com/pharo-spec/Spec/pull/1536 - Fix selection bug in SpFilteringSelectableListPresenter #1535 https://github.com/pharo-spec/Spec/pull/1535 - fix: SpSelectDialog should select the first item #1530 #1534 https://github.com/pharo-spec/Spec/pull/1534 - Improve SpSelectDialog for handling line splitting texts #1533 https://github.com/pharo-spec/Spec/pull/1533 - Cleanup/remove rename default spec to default layout refactoring #1515 https://github.com/pharo-spec/Spec/pull/1515 # Cleanups - moved to Spec2-Transmission package #1538 https://github.com/pharo-spec/Spec/pull/1538 - Use #setUp instead of #initialize for test cases #16417 https://github.com/pharo-project/pharo/pull/16417 - Remove CharacterTable #16416 https://github.com/pharo-project/pharo/pull/16416

1 0

Early rate deadline is approaching....
by stephane ducasse April 9, 2024

April 9, 2024

Hello People do not miss this unique opportunity to participate in ESUG in early July https://esug.org Pay attention that the early rate end is approachingâ¦ 15 of April 2024. https://registration.esug.org/ESUG StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

3 2

This week (14/2024) on the Pharo Issue Tracker
by Marcus Denker April 5, 2024

April 5, 2024

# Fixes - Provide a default String for settings without #default: sends. #16400 https://github.com/pharo-project/pharo/pull/16400 - 16356-Rename-class-refactoring-popup-does-not-have-default-button #16392 https://github.com/pharo-project/pharo/pull/16392 - Small fixes pre release #16381 https://github.com/pharo-project/pharo/pull/16381 - Revert comment change from commit f5df5966bd73d05bc04806d2f8735baa4b1783cb #16376 https://github.com/pharo-project/pharo/pull/16376 - Fix function signature in #getVolumeInfo:into:size: for StWin32Info #730 https://github.com/pharo-spec/NewTools/pull/730 - Adapt #getVolumeInfo:into:size: for StWin32Info to strict FFI #729 https://github.com/pharo-spec/NewTools/pull/729 - Change #getTempPath:buffer: on WinPlatform to use âGetTempPathWâ instead of âGetTempPath2Wâ #16342 https://github.com/pharo-project/pharo/pull/16342 - latest changes #1532 https://github.com/pharo-spec/Spec/pull/1532 # UI/Tools Fixes - improve/spRequiestDialog-issue-16356 #1531 https://github.com/pharo-spec/Spec/pull/1531 - Remove Monticello shortcut references #16388 https://github.com/pharo-project/pharo/pull/16388 - remaining morphic dialogs: aligning the default option to right #16352 https://github.com/pharo-project/pharo/pull/16352 - 16363-Improve-Expand-menu-for-class-definition #16371 https://github.com/pharo-project/pharo/pull/16371 - New tools parent menu entry #16379 https://github.com/pharo-project/pharo/pull/16379 - Open Calpyso with 915px wide such that the entire toolbar is visible #16380 https://github.com/pharo-project/pharo/pull/16380 - Make #cascadeFor:initialExtent:world: for RealEstateAgent use integral positions when using the worldâs center #16390 https://github.com/pharo-project/pharo/pull/16390 - Fix issue while trying to display file setting items #736 https://github.com/pharo-spec/NewTools/pull/736 - Remove async playground doits #735 https://github.com/pharo-spec/NewTools/pull/735 - Fix Preview Settings Browser: does not open when a custom setting is used #734 https://github.com/pharo-spec/NewTools/pull/734 - Fix "Open terminal here" in new File browser #732 https://github.com/pharo-spec/NewTools/pull/732 - Add 3 new entries to easily access the new tools from the System menu. #731 https://github.com/pharo-spec/NewTools/pull/731 # Cleanups - Deprecate #newMethod:header: with rewritting to #basicNew:header: #16375 https://github.com/pharo-project/pharo/pull/16375 - Remove StWindowsExtensionsTest #728 https://github.com/pharo-spec/NewTools/pull/728 - Remove old backward compatibility code from FFILibrary #16349 https://github.com/pharo-project/pharo/pull/16349

1 0

Call for Presentations @ ESUG 2024
by stephane ducasse April 4, 2024

April 4, 2024

Dear Friends The deadline for the presentation proposal was 1st of April. We extended it until 8th of April. You are probably busy but we the organisers deserve consideration too. ESUG 2024 Call for Presentations from 8 to 11 July 2024 Lille France https://esug.github.io <https://esug.github.io/> https://esug.github.io/2024-Conference/conf2024.html You can support the ESUG conference in many different ways: - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ - Submit a talk, software to the award competition, or a paper to IWST http://https://esug.github.io/2024-Conference/IWST2024.html - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! - Students can get free registration and hosting if they enroll in the the Student Volunteers program. See below. ## Developers Forum: International Smalltalk Developers Conference We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. The list of topics for the normal talks and tutorials includes, but is not limited to the following: - XP practices, Development tools, Experience reports - Model-driven development, Web development, Team management - Meta-Modeling, Security, New libraries & frameworks - Educational material, Embedded systems and robotics - SOA and Web services, Interaction with other programming languages - Teaching Pearls and Show us Your Business We added two types of sessions in addition to the regular talks and ''Show us your project'' sessions. - Show your business in a 10-minute session (Get prepared!!) - Teaching pearls: we want some sessions on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15-minute sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2024-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>] Title: [ESUG 2024] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio:

1 0

Books about Pharo
by stephane ducasse April 3, 2024

April 3, 2024

Hi Richard I did not see your original post because I messed up with my account. But thanks for your email :) Now the cool stuff if that we can also read the books from within Pharo. We should improve the Microdown renderer and suddenly we will get shiny cool documentation. S > This is a new thread because it's not limited to any specific topic. > > If you have questions about Pharo, especially "how do I do <this> in > Pharo", you can always ask in this mailing list. You can, if you like > playing Russian Roulette, ask a Large Language Model "AI". > > But there is an amazing resource you should really trye. > > books.pharo.org > > Did you ever wonder where the manual for Pharo was? > That's where. The site lists a bunch of Pharo books and booklets, > all of which have free PDFs except for two of the books. > In particular, you'll always want the most recent edition of > "Pharo by Example" handy. > > These books are really useful. They are written by people know know > their material thoroughly and do a good job of explaining it. If you > want to make any serious use of Pharo, or even to have more happiness > than headaches just playing with it, you owe it to yourself to get the > free PDFs What do we owe the authors? Well, if you're not trying to > make one pension support four people, you owe them the purchase of > some of the books. Me, I'm giving them thanks, praise, and a > heartfelt recommendation. > > Seriously, these books represent a HUGE amount of work and "you are a > fool to yourself and a burden to others" if you don't take advantage > of this great resource.

2 4