March 2024 - Pharo-users - lists.pharo.org

IWST 24 â International Workshop on Smalltalk Technologies Lille, France; July 8th to 11th, 2024
by Steven Costiou March 14, 2024

March 14, 2024

IWST 24 INFORMATION AND CALL FOR PAPERS IWST 24 -- International Workshop on Smalltalk Technologies Lille, France; July 8th to 11th, 2024 GOALS AND SCOPE The goals of the workshop is to create a forum around contributions and experiences in building or using technologies related to Smalltalk. While maturity of presented ideas and results is not crucial, it is expected that their presentation triggers discussion and exchange of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Authors are invited to submit research articles or industrial papers. IMPORTANT DATES * Extended abstract submission deadline: MARCH 31ST, 2024 * Extended abstract notification deadline: April 7th, 2024 * Full/short paper submission deadline: May 19th, 2024 * Full/short paper first-round notification deadline: June 30th, 2024 * Workshop: July 9-10, 2024 * Full/short paper resubmission deadline: July 21st, 2024 * Full/short paper final notification deadline: July 31st, 2024 * Camera ready package submission deadline: August 25th, 2024 TOPICS We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: * Code Analysis * Automated Testing * Debugging * Compilers, Virtual Machines and Language implementations * Meta-programming and Meta-modeling * Refactorings * Design patterns * Experience reports * Libraries and frameworks * New dialects or languages implemented in Smalltalk * Interaction and integration with other languages * Tools SUBMISSIONS, REVIEWS, AND SELECTION Authors interetsed to present their work at the IWST 2024 are invited to submit an abstract of the intended talk before the extended abstract submission deadline. The extended abstract should be not longer than 2 pages following the CEUR ART style [1]. Author of the submitted extended abstratcs will be notified and invited to present their work by the extended abstract notification deadline which enables presenters to register at the early registration prices. Authors of the accepted abstracts are also invited to submit a paper to be subject of the review and a potential acceptance for publishing in the IWST 2024 Proceedings. We are looking for papers of two kinds: * Short position papers (5 to 10 pages) describing fresh ideas and early results. * Full research papers (more than 10 pages) with deeper description of experiments and of research results. Paper accepted for publishing will be published within a CEUR-WS Proceedings [2]. Hence, both submissions and final papers must be prepared using the CEUR ART style [1]. All submissions must be sent via EasyChair submission page [3]. Pay attention, for organisation constraints, when submitting your article you are expected to register to the conference and pay the conference fees. REVIEWING As the workshop format encourages bringing fresh ideas and early results to be presented and discussed, and aims for giving a chance to young community members to learn and grow, we will allow submissions with a discussion potential to be conditionally accepted. In this case, authors are expected to follow the recommendation of the reviewers. Consequently, the reviewing process will be organized in two rounds: * in the first round, all submissions will be reviewed by at least 3 reviewers. Based on these reviews authors will receive a notification with reviewers comments, advises, and requirements and papers that are not rejected will be invited to be resubmitted in an improved form together with change log and answrers to the reviewers. * in the second round, PC chairs in collaboration with the reviewers where needed and possible, will evaluate the improved paper version and notifiy authors about final decision on acceptance/rejection. BEST PAPER AWARD To encourage the submission of high-quality ideas, contributions, and papers, the IWST organizing committee is very proud to announce a Award competition in the categories of BEST IDEA, BEST CONTRIBUTION TO THE COMMUNITY and BEST PAPER FOR THIS EDITION OF IWST. The ranking will be decided by the program committee during the review process and by the audience voting during the conference. The awards will be given during the ESUG conference social event. The Awards will take place only with a minimum of six submissions. Notice also that to be eligible, a paper/abstract must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. PROGRAM CHAIRS * Steven Costiou, Inria Lille, France (chair), * Guille Polito, Inria Lille, France (chair), * Gordana Rakic, University of Novi Sad, Serbia (chair) PROGRAM COMMITTEE to be published ... Links: ------ [1] https://ceur-ws.org/Vol-XXX/CEURART.zip [2] imap://scostiou@zimbra.inria.fr:993/fetch%3EUID%3E/Sent%3E105178?part=1.2.2&filename=text.html [3] https://easychair.org/conferences/?conf=iwst2024

1 0

"Introducing Atlas" â New blog post on all: objects all: theTime
by Koen De Hondt March 13, 2024

March 13, 2024

Dear Pharo users and developers, Some people already know that I am working on a browser for Pharo. With this announcement, I make it official ð. In my latest blog post <https://all-objects-all-the-time.st/#/blog/posts/6>, I introduce Atlas as an ambitious successor of Calypso. It is the first post in a series. Happy reading! Ciao, Koen

6 6

ESUG24 Call for Student Volunteers, 8-11 July, Lille, France
by Steven Costiou March 12, 2024

March 12, 2024

CALL FOR STUDENT VOLUNTEERS, ESUG 2024, 8-11 JULY, LILLE, FRANCE Student volunteers help the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. PAY ATTENTION: the places are limited so do not wait till the last minute to apply. CONFERENCE DETAILS: Send an email to volunteers-esug24(a)inria.fr. * title: [ESUG 2024 Student] * name, gender, university/school, country, email address * short description of you and why you are interested in participating Accommodation is covered from Sunday 7 July until 8 Thursday July 2024 (including nights from Sunday to Monday and from Thursday to Friday). Students will be hosted in student rooms. ESUG additionally covers for the lunches during the week and one dinner. Travel costs are *not* covered by the student volunteers program. Duties include handling registration as people arrive at the conference, filling coffee machines, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time and doesn't significantly interfere with enjoying and learning from the conference. Please note, this role requires discipline and constant attention to all attendees.

1 0

please unsubscribe me
by Rui Viana Pereira March 11, 2024

March 11, 2024

Thank you *Rui Viana Pereira*

2 1

This week (10/2024) on the Pharo Issue Tracker
by Marcus Denker March 11, 2024

March 11, 2024

# Pharo 10 - Fix for: UFFI/TFFI call for WebBrowser with specific URL length adds strange characters to the URL #15980 #16253 https://github.com/pharo-project/pharo/pull/16253 # Pharo 11 - Fix for: UFFI/TFFI call for WebBrowser with specific URL length adds strange characters to the URL #15980 #16284 https://github.com/pharo-project/pharo/pull/16284 # Fixes - do not spam selectPage: #1528 https://github.com/pharo-spec/Spec/pull/1528 - Restore original message String #16274 https://github.com/pharo-project/pharo/pull/16274 - Fix Method name editor dialog up/down buttons #16273 https://github.com/pharo-project/pharo/pull/16273 - Fix Bug: OrderedDictionary>>#at:at:put: not updating ordered keys #16260 https://github.com/pharo-project/pharo/pull/16260 - Minor improvement in TF test class #16257 https://github.com/pharo-project/pharo/pull/16257 - Fix #magnifyBy:smoothing: on OSSDL2ExternalForm #16225 https://github.com/pharo-project/pharo/pull/16225 - fix a failing test #714 https://github.com/pharo-spec/NewTools/pull/714 # Improvements - Make #reportTestCase:runBlock: on HDTestReport print the test run time on the progress log stream #16266 https://github.com/pharo-project/pharo/pull/16266 # Refactoring Engine - Fix: rename method shortcut #16251 https://github.com/pharo-project/pharo/pull/16251 - Remove unused instance variable in #ReRenameMethodRefactoring #16279 https://github.com/pharo-project/pharo/pull/16279 - Fix: rename method preconditions fail with DNU #16270 https://github.com/pharo-project/pharo/pull/16270 - Test: rename method driver #16269 https://github.com/pharo-project/pharo/pull/16269 - Cleanup: rename method refactoring driver to new architecture with breaking choices #16258 https://github.com/pharo-project/pharo/pull/16258 # Cleanups - Refactor various âworldMenuâ registration methods to use #iconName: instead of #icon: #711 https://github.com/pharo-spec/NewTools/pull/711 - Updated baseline of Dependency analyzer #16278 https://github.com/pharo-project/pharo/pull/16278 - 16246-CI-Failing-test-SystemDependenciesTesttestExternalIDEDependencies #16264 https://github.com/pharo-project/pharo/pull/16264

1 0

Finding references to non existent classes in Pharo
by Tim Mackinnon March 11, 2024

March 11, 2024

Hi - I was convinced in earlier Pharoâs, if you had a code reference to a non existent class you could find it by searching for references to its symbol name eg #MyMissingClass allReferences (or find references in the UI). This doesnât seem to work in Pharo 11? I loaded a package with a missing class, and when running something it complained about the missing class (it was an announcement), but I couldn't find an easy way to find it in my code to correct it? I ended up creating the fake class to then find references to it (as I then had a class), which seems way over the top? I haven't had a chance to try this in Pharo 12, but shouldn't what I have done work? Or is there some new way to do this? I asked on Discord users, but didn't get a reply other than it rang a bell. I know there has been a lot of work in the area of how things are represented and I wonder if something has got broken by mistake? Tim

5 4

PharoFlipper
by Tim Mackinnon March 5, 2024

March 5, 2024

In case its useful to anyone - I got fed up with not having a ctrl-tab alternative in pharo (I find I frequently like to jump back to the last window/browser I was looking at - and used to love the Mirage utility which is sadly not broken and rather complicated to fix) - so I added a tiny little utility - PharoFlipper. It's not fancy, just does an LRU flip to previous windows via ctrl-1. It's a bit basic, in that the cycle reset is based on time, so you have to wait ~1s to reset the LRU cycle (vs. let go of the ctrl key) but it works well enough and might help others too. see: https://github.com/macta/PharoFlipper Tim

2 1

Smalltalk Meetup in Zurich, 26 April 2024
by Peter Ursprung March 4, 2024

March 4, 2024

Hi all, We are organizing the next Smalltalk Meetup in Zurich, Switzerland. It will be on Friday, 26 April 2024, starting at 18:00. We will meet in a meeting room where we will have short Smalltalk talks, afterwards we will go to a restaurant nearby. If you are interested, please register until Friday, 19 April 2024 on this website: https://zurich.smalltalk.world <https://zurich.smalltalk.world> We are still looking for presentations: if you have something interesting to show, please contact us or mention it in the registration. Regards, Peter

1 0

This week (09/2024) on the Pharo Issue Tracker
by Marcus Denker March 1, 2024

March 1, 2024

# Features - integrating Debug Points model into Pharo #16177 https://github.com/pharo-project/pharo/pull/16177 # Fixes - add back isGlobalClassNameBinding #16035 https://github.com/pharo-project/pharo/pull/16035 - FFIUnsupportedUntypedLiteral when using WebBrowser classes on Windows #16262 https://github.com/pharo-project/pharo/pull/16262 - Fix adding slots in Ring #16247 https://github.com/pharo-project/pharo/pull/16247 - use the correct integration branch for iceberg and Pharo #16244 https://github.com/pharo-project/pharo/pull/16244 - fixing reflectivity bug that executes a #before metalink twice if an #after metalink is installed #16236 https://github.com/pharo-project/pharo/pull/16236 - MCWorkingCopy class>>#infoFromDictionary:cache: sends a deprecated method #16231 https://github.com/pharo-project/pharo/pull/16231 - 16204-RubPluggableTextFieldMorph-does-not-open-drop-list #16205 https://github.com/pharo-project/pharo/pull/16205 - Bug fix: Context menu item âRevert to selected versionâ in recent versions of a method does not revert #710 https://github.com/pharo-spec/NewTools/pull/710 - ExpressionFinder - matches browser now knows the method that is showing #709 https://github.com/pharo-spec/NewTools/pull/709 # Graphics / Rendering / UI - Make EpEntryItem use FormSet for the icons #16240 https://github.com/pharo-project/pharo/pull/16240 - Fix #freshLogFromSelection: on EpUnifiedBrowserPresenter to map trigger references #16239 https://github.com/pharo-project/pharo/pull/16239 - Refactor various âworldMenuâ registration methods to use #iconName: instead of #icon: #16237 https://github.com/pharo-project/pharo/pull/16237 # Refactoring Engine - Fix: use new API for getting the package name in CopyClassRegexRefactoring #16256 https://github.com/pharo-project/pharo/pull/16256 - Fix: multiple exceptions when executing a rb move class transformation #16250 https://github.com/pharo-project/pharo/pull/16250 - Fix: #16209: [RB] Insert superclass refactoring breaks class side hierarchy #16234 https://github.com/pharo-project/pharo/pull/16234 # Cleanup - Removed CursorWithAlpha as is not used #16229 https://github.com/pharo-project/pharo/pull/16229 - [Cleanup] #notNil to #isNotNil in Spec #1527 https://github.com/pharo-spec/Spec/pull/1527 # Documentation - In TerseGuide fix documentation #16228 https://github.com/pharo-project/pharo/pull/16228

1 0