February 2023 - Pharo-users

UK Smalltalk User Group Meeting - 22 February 2023

by Giovanni Corriga

WebAssembly (WASM - https://wikiwand.com/en/Webassembly ) is an instruction format for portable high-performance code, run by a stack-based virtual machine. To Smalltalkers, this sounds very familiar. WASM is supported by the three most popular web browsers, and by other host platforms as well. Perhaps we can translate certain Smalltalk compiled methods to WASM, augmenting our support for physical processors and for livecoding the Web. For our February meeting, Craig Latta will describe his initial experiments, using the Epigram compilation framework ( https://thiscontext.com/epigram ). Craig Latta ( https://thiscontext.com/ ) is a research computer scientist in Berkeley and Amsterdam, with interests including livecoding, music performance, and interactive visualization. The discovery of a mysteriously-placed copy of the Blue Book at university led to stints at several exploratory labs, and a pursuit of improvisation wherever code is found. 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/291365015/ ) to receive the meeting details.

Feb. 14, 2023

ESUG 2023 Call for participation

by stephane ducasse

ESUG 2023 Call for Presentations 28.8.2023 to 01.9.2023 Lyon France https://esug.github.io https://esug.github.io/2023-Conference/conf2023.html ESUG is the premium and fun conference around smalltalk technologies. 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, a software or a paper to one of the events. See below. - 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 into 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 New this year!!! We added two types of sessions in addition to the regular talks and show us your projects sessions. Show your business 10 min session (Get prepared!!) Teaching pearls : we want some session 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 min sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2023-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr] Title: [ESUG 2023] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: ## Call for Student Volunteers Student volunteers help keep 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 stephane.ducasse at inria.fr and Oleksandr Zaitsev <olk.zaytsev(a)gmail.com> with: Title: [ESUG 2023 Student] name, gender, university/school, country, email address short description of you and why you are interested in participating For which period is accommodation covered? Accommodation is covered from Sunday 27.8.2023 to 01.9.2023 (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. 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. Information about hotel Student Volunteer rooms are booked at (to be announced). If you are student volunteer, do not book yourself, we have arranged the booking already!

Feb. 11, 2023

This week (6/2023) on the Pharo Issue Tracker

by Marcus Denker

We merged 60 PRs, closed 76 issues Features ======== - Add #ensureOpen to Trascript to not open multiple transcripts while sâ¦ #12588 https://github.com/pharo-project/pharo/pull/12588 - Improve ReImplementedNotSentRule to ignore self calls + add tests #12585 https://github.com/pharo-project/pharo/pull/12585 - Adding an accessor for the root nodes of the settings browser #12521 https://github.com/pharo-project/pharo/pull/12521 Speed ===== - Disable setting formatIncompleteIdentifiers by default #12475 https://github.com/pharo-project/pharo/pull/12475 Fixes ===== - 12418-MCMethodDefinition-asSymbol-error-when-catString-isNil-loading-BaselineOf #12589 https://github.com/pharo-project/pharo/pull/12589 - Improve robustess of DependencyAnalyzer #12581 https://github.com/pharo-project/pharo/pull/12581 - 12518-ImageCleaner-shareLiterals-shouldnt-consider-Strings-and-Symbols-the-same #12529 https://github.com/pharo-project/pharo/pull/12529 - fix #12573: Error due to deprecated wantsStepsIn: on "senders of" #12574 https://github.com/pharo-project/pharo/pull/12574 - Fix DrTest UI when plugin selection change #12468 https://github.com/pharo-project/pharo/pull/12468 - Fix #12408, remove containerTabs from the notebook and not from the owner submorphs #12464 https://github.com/pharo-project/pharo/pull/12464 - Extract set up now classify setUp in #running #12512 https://github.com/pharo-project/pharo/pull/12512 Compiler ======== - Compiler: enable optionInlineTimesRepeat and optionInlineRepeat by default #12604 https://github.com/pharo-project/pharo/pull/12604 - add a "parse plugin" mechanism to OpalCompiler #12429 https://github.com/pharo-project/pharo/pull/12429 Refactoring Engine ================== - FindAndReplaceRefactoring is a transformation #12495 https://github.com/pharo-project/pharo/pull/12495 - Cleanup unused refactorings #12531 https://github.com/pharo-project/pharo/pull/12531 Tools ===== - Use the list of VM parameters from the pharo image. #448 https://github.com/pharo-spec/NewTools/pull/448 - Improved debugger symbol diff in failing tests #462 https://github.com/pharo-spec/NewTools/pull/462 - fix test of Sindarin when timesRepeat: is optimized #461 https://github.com/pharo-spec/NewTools/pull/461 - Integrating JumpToCaret command from Sindarin to the advanced step menu in the debugger toolbar #428 https://github.com/pharo-spec/NewTools/pull/428 - 377-Uncategorised-method-in-StDebuggerCommandtransform #433 https://github.com/pharo-spec/NewTools/pull/433 - Double click on the debugger stack browse the method #460 https://github.com/pharo-spec/NewTools/pull/460 - Spotter Insert selection setting #454 https://github.com/pharo-spec/NewTools/pull/454 - Fix spotter bug while clicking a header #455 https://github.com/pharo-spec/NewTools/pull/455 - Simplifying code in settings commands #459 https://github.com/pharo-spec/NewTools/pull/459 - Debugger-Actions are legacy code from the previous debugger. #458 https://github.com/pharo-spec/NewTools/pull/458 CI related ========== - fix transcript output testIgnoreDeprecationWarnings #12603 https://github.com/pharo-project/pharo/pull/12603 - skip the test testNewProcessTaskRunnerRunsInNewProcessEveryTime on the CI #12530 https://github.com/pharo-project/pharo/pull/12530 Documentation ============= - 12498-Documentation-fix-for-Dictionary--keysAndValuesDo #12580 https://github.com/pharo-project/pharo/pull/12580 - add block ast node stats code as class comment #12606 https://github.com/pharo-project/pharo/pull/12606 - comment to explicit class size initialize behavior #12463 https://github.com/pharo-project/pharo/pull/12463 Cleanup ======= - Remove debugger actions #12515 https://github.com/pharo-project/pharo/pull/12515 - 5500-Ban-rule-on-testReadComputedSlotCompiled #12523 https://github.com/pharo-project/pharo/pull/12523 - 11142-TestRunner--classNamesNotUnderTest-is-sent-but-not-implemented #12525 https://github.com/pharo-project/pharo/pull/12525 - Remove SourceCodeFont setting that has no effect #12522 https://github.com/pharo-project/pharo/pull/12522 - Stepping mecanisme should be used by model and morph. But it is curreâ¦ #12510 https://github.com/pharo-project/pharo/pull/12510 - 12080-Dead-code-viewContentsInWorkspace #12524 https://github.com/pharo-project/pharo/pull/12524 - remove dead code with wikiStyleHelp: pragma #12582 https://github.com/pharo-project/pharo/pull/12582 - Add <ignoreForCoverage> to methods generated by the manifest builder #12583 https://github.com/pharo-project/pharo/pull/12583 - Rename PlatformIndependentEnvironment into NullOSEnvironment #12520 https://github.com/pharo-project/pharo/pull/12520 - extract return from ifTrueifFalse expression #12561 https://github.com/pharo-project/pharo/pull/12561 - 22 x cleanups of the kind Cleanup: Condense Reflectivity packages #12601 https://github.com/pharo-project/pharo/pull/12601 - Remove use of deprecated classes #1351 https://github.com/pharo-spec/Spec/pull/1351 - Remove use of deprecated classes #1351 https://github.com/pharo-spec/Spec/pull/1351

Feb. 10, 2023

[ANN] Bell v1.0.0 [First version] released!

by Buenos Aires Smalltalk

Feb. 7, 2023

Re: Call for project ideas: Google Summer of Code 2023

by Pierre Misse Chanabier

Hi, What is the deadline please ? Pierre On 2/1/2023 9:18 PM, Sebastian Jordan Montano wrote: > > Hello all, > > > As Pharo community we are postulating to Google Summer of Code 2023. > We would like to have new brand ideas for this new edition! We would > like to know if there are people in the community that have some cool > project ideas :) > > > If you have an idea.s, donât hesitate to share it/them with us. If you > have an idea but you donât have the time to be a mentor for it, it is > not a problem! We can find other mentors. And if you have an idea and > you are willing to be a mentor that would be even better! Being a > mentor only requires you to have a weekly 30 min meeting with your > student to supervise that the work is going in the desired direction. > > > You will need to provide: > > a) a project title b) detailed description of the project (2-5 > sentences) c) expected outcomes d) skills required/preferred > (optional) f) expected size of project medium or large. > > > You can reply to this email or send me another email to my private > email address sebastian.jordan(a)inria.fr <mailto:sebastian.jordan@inria.fr> > > > Cheers, > > Sebastian Jordan on behalf of the Pharo Consortium > >

Feb. 3, 2023

Re: Call for project ideas: Google Summer of Code 2023

by Sebastian Jordan Montano

Hello Vince, Thank you for your suggestion. But unfortunately the project seems complex enough to be picked up by someone who does not have experience in the subject. Sebastian > De: vinref(a)gmail.com > Ã: "pharo-users" <pharo-users(a)lists.pharo.org> > EnvoyÃ©: Jeudi 2 FÃ©vrier 2023 06:25:49 > Objet: [Pharo-users] Re: Call for project ideas: Google Summer of Code 2023 > Hi Sebastian > I myself have been mulling for a long time porting Swish > (https://github.com/becls/swish) to Pharo. I do not have the time or energy > though. Maybe someone else can pick it up and run with it. > Vince

Feb. 3, 2023

This week (4/2023) on the Pharo Issue Tracker

by Marcus Denker

We merged 39 PRs and closed 77 issues. If you want to help, there are 29 PRs: https://github.com/pharo-project/pharo/pulls Features ======== - Introduce new string comparison primitive #12504 https://github.com/pharo-project/pharo/pull/12504 - Profiler: simplify world menu #12501 https://github.com/pharo-project/pharo/pull/12501 - ReSentNotImplementedRule: take Pragma into account #12295 https://github.com/pharo-project/pharo/pull/12295 - 12431 Better user experience for final dot critique and cleaning #12455 https://github.com/pharo-project/pharo/pull/12455 - Fix #3067: Float>>#closeTo: does not use Float>>epsilon as default precision #12451 https://github.com/pharo-project/pharo/pull/12451 - Fix #3332: New package committed by Iceberg is always dirty #12453 https://github.com/pharo-project/pharo/pull/12453 - Fix #12287 adding group model to parent window #12446 https://github.com/pharo-project/pharo/pull/12446 - Improving the ChangesBrowser presenter #12438 https://github.com/pharo-project/pharo/pull/12438 - [improvement] better default hierarchy display #11053 https://github.com/pharo-project/pharo/pull/11053 - Complete symbols #11918 https://github.com/pharo-project/pharo/pull/11918 - convert numpad keys with NumLock turned off #12258 https://github.com/pharo-project/pharo/pull/12258 Speed ===== - 12128-Poor-performance-with-large-WriteStreams #12205 https://github.com/pharo-project/pharo/pull/12205 Fixes ===== - Honor theme changed events #12473 https://github.com/pharo-project/pharo/pull/12473 - fix: DeprecateClassCommand DNU #12494 https://github.com/pharo-project/pharo/pull/12494 - Fix conflict between formatter and rules: spaces before new lines #12448 https://github.com/pharo-project/pharo/pull/12448 - 11968-Clean-Blocks-Jobowner-assumes-valid-outerContext #12055 https://github.com/pharo-project/pharo/pull/12055 - Re-introduce list morph shortcuts using keydown #12386 https://github.com/pharo-project/pharo/pull/12386 CI related ========== - 12508-CI-failing-test-RBReplaceSubtreeTransformationTesttestTransformOneOfManyStatements #12509 https://github.com/pharo-project/pharo/pull/12509 - 12440-CI-failing-test-testClassSideInitializeMethodNeedsToBeInClassInitializationProtocol #12442 https://github.com/pharo-project/pharo/pull/12442 - Fix dependencies tests #12449 https://github.com/pharo-project/pharo/pull/12449 Cleanups ======== - Fix #3172: parseTreeFor: asymbol should be renamed parseTreeOfMethodNamed: aSymbol #3172 #12452 https://github.com/pharo-project/pharo/pull/12452 - Removed duplicated line form RubSmalltalkEditor>>tallySelection #12437 https://github.com/pharo-project/pharo/pull/12437 - Extracting the logic of screenshot and selection #11254 https://github.com/pharo-project/pharo/pull/11254 - Review if #scanToken: in RBScanner is still needed #11554 https://github.com/pharo-project/pharo/pull/11554 - Clean some duplication logic by extracting Smalltalk tools into a sepâ¦ #12085 https://github.com/pharo-project/pharo/pull/12085 - move emit from Announcement to Object #12266 https://github.com/pharo-project/pharo/pull/12266 Trivial Cleanups ================ - 9 x cleanups of the kind Cleanup: Condense NECompletion packages #12485 https://github.com/pharo-project/pharo/pull/12485 - 2x cleanups of the kind extract return from ifTrue: ifFalse: and remove white spaces #12476 https://github.com/pharo-project/pharo/pull/12476

Feb. 3, 2023

Re: Call for project ideas: Google Summer of Code 2023

by vinref＠gmail.com

Hi Sebastian I myself have been mulling for a long time porting Swish (https://github.com/becls/swish) to Pharo. I do not have the time or energy though. Maybe someone else can pick it up and run with it. Vince

Feb. 2, 2023

Call for project ideas: Google Summer of Code 2023

by Sebastian Jordan Montano

Hello all, As Pharo community we are postulating to Google Summer of Code 2023. We would like to have new brand ideas for this new edition! We would like to know if there are people in the community that have some cool project ideas :) If you have an idea.s, donât hesitate to share it/them with us. If you have an idea but you donât have the time to be a mentor for it, it is not a problem! We can find other mentors. And if you have an idea and you are willing to be a mentor that would be even better! Being a mentor only requires you to have a weekly 30 min meeting with your student to supervise that the work is going in the desired direction. You will need to provide: a) a project title b) detailed description of the project (2-5 sentences) c) expected outcomes d) skills required/preferred (optional) f) expected size of project medium or large. You can reply to this email or send me another email to my private email address [ mailto:sebastian.jordan@inria.fr | sebastian.jordan(a)inria.fr ] Cheers, Sebastian Jordan on behalf of the Pharo Consortium

Feb. 1, 2023