- Pharo-users - lists.pharo.org

[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

"Atlas is a Spec application" â New blog post on all: objects all: theTime
by Koen De Hondt May 6, 2024

May 6, 2024

Dear Pharo users and developers, I added the next blog post <https://all-objects-all-the-time.st/#/blog/posts/8> to the series on Atlas, a new browser for Pharo. It describes the relationship between Atlas and Spec, the UI framework of Pharo. The blog post introduces the basic building blocks of the Atlas UI. It also explains the struggle with some aspects of Spec and the Morphic backend. Happy reading! Ciao, Koen

2 1

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

May 3, 2024

With Pharo12 being released, we started to merge more changes in Pharo13. # Pharo12 - Pharo12: ProcessorScheduler>>#activeProcess added no instrumentation pragma #16557 https://github.com/pharo-project/pharo/pull/16557 - Add Toplo world menu entry (part 2) #16478 https://github.com/pharo-project/pharo/pull/16478 # Graphics - Change default value for setting #autoSetCanvasScaleFactor to true #16529 https://github.com/pharo-project/pharo/pull/16529 - missing stroke paint method #16531 https://github.com/pharo-project/pharo/pull/16531 - Change #shrinkTo: on FreeTypeCache to selectively remove entries rather than all of them #16419 https://github.com/pharo-project/pharo/pull/16419 # Bugs - ExteranlAddress>>fromString: converts string to UTF-8 first #16560 https://github.com/pharo-project/pharo/pull/16560 - ProcessorScheduler>>#activeProcess added no instrumentation pragma #16551 https://github.com/pharo-project/pharo/pull/16551 # Refactoring Engine - Refactoring of the RefactoryChange manager #16526 https://github.com/pharo-project/pharo/pull/16526 - Composite extract method refactoring #16525 https://github.com/pharo-project/pharo/pull/16525 # Speed - Announcer: Return early if there isn't any subscriber #16336 https://github.com/pharo-project/pharo/pull/16336 # Cleanup / Misc - New pass at removing SystemAnnouncer references #16518 https://github.com/pharo-project/pharo/pull/16518 - update with latest changes from Pharo12 #16523 https://github.com/pharo-project/pharo/pull/16523 - remove interactionState: #16559 https://github.com/pharo-project/pharo/pull/16559 - the tests use #category: from the package Deprecated12 #743 https://github.com/pharo-spec/NewTools/pull/743 # Tests - add tests for testDoWhileFalse: and testDoWhileTrue: #16532 https://github.com/pharo-project/pharo/pull/16532 - 5 test for rules #16524 https://github.com/pharo-project/pharo/pull/16524

1 0

[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