- Pharo-dev - lists.pharo.org

Pharo needs you! Call to save the Pharo UI
by stephane ducasse Nov. 23, 2023

Nov. 23, 2023

Hello people If you want that Pharo just do not endlessly stay with such a crappy UI we all know, please consider joining the effort. We should make sure that as a general principle, a model MUST not refer to a UI. So that we can change the UI. We are working on it. But we need help. We should (1) Migrate last cool Morphic-based tools such as Finder, Settings to Spec2, FileList to Spec (2) Remove dependencies from Domain objects to Morphic (obviously) - remove to UIManager first from code outside Morphic. As a general principle please watch http://rmod-pharo-mooc.lille.inria.fr/AdvancedDesignMooc/Videos/M03_S5.mp4 http://rmod-pharo-mooc.lille.inria.fr/AdvancedDesignMooc/Videos/M09_S4.mp4 It looks basic but it is so true. Current status (1) Hernan started to work on the Setting Browser I know someone started to work on Finder but I think the effort was stalled. We need help there. (2) We started to clean the refactorings and we are making progress but this is slow. I started to remove references to UIManager because it should go away. In Spec we introduced dialog, check the examples in subclasses of SpDialogPresenter In addition, an application is able to create some default dialog check ui - dialogs in SpApplication I introduced a simple notification center that should play a kind of growl. The inform: calls should be redirected to notify: because inform: was in P11 not blocking and now in P12 there are. I created special issues about the references to UIManager I opened issues with a special tag https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%… The analysis is here https://github.com/pharo-project/pharo/issues/14174 <https://github.com/pharo-project/pharo/issues/14174> Here are some scripts. # Here we see the dependencies from Spec to UIManager | allSpec results | results := Dictionary new. allSpec := SpPresenter withAllSubclasses. UIManager selectors do: [ :sel | | size | size := ((SystemNavigation default allCallsOn: sel ) select: [ :mth | allSpec includes: mth methodClass ]) size. size isZero ifFalse: [ results at: sel put: size]]. String streamContents: [ :s | results keys sorted do: [ :k | s nextPutAll: k , ' -> ', (results at: k) asString. s cr. ]] # The following script shows the callers that are not in Spec nor in Morphic | allSpec results allMorphs | results := Dictionary new. allSpec := SpPresenter withAllSubclasses. allMorphs := Morph withAllSubclasses. allClasses := Smalltalk allClasses. allClasses := allClasses reject: [ :c | allSpec includes: c ]. allClasses := allClasses reject: [ :c | allMorphs includes: c ]. UIManager selectors sorted do: [ :sel | | size | size := ((SystemNavigation default allCallsOn: sel ) select: [ :mth | allClasses includes: mth methodClass ]) size. size isZero ifFalse: [ results at: sel put: size]]. String streamContents: [ :s | results keys sorted do: [ :k | s nextPutAll: k , ' -> ', (results at: k) asString. s cr. ]] abort: -> 1 abort:title: -> 5 activate -> 15 alert: -> 4 alert:title: -> 4 alert:title:configure: -> 2 beDefault -> 2 chooseDirectory -> 1 chooseDirectory: -> 1 chooseDirectory:from: -> 2 chooseDirectoryFrom: -> 1 chooseFrom: -> 2 chooseFrom:lines: -> 2 chooseFrom:lines:message: -> 1 chooseFrom:lines:message:title: -> 2 chooseFrom:lines:title: -> 8 chooseFrom:title: -> 5 chooseFrom:values: -> 5 chooseFrom:values:lines: -> 1 chooseFrom:values:lines:message: -> 1 chooseFrom:values:lines:message:title: -> 3 chooseFrom:values:lines:title: -> 4 chooseFrom:values:message:title: -> 4 chooseFrom:values:title: -> 8 chooseFullFileNameMatching: -> 1 chooseFullFileNameMatching:label: -> 1 chooseOrRequestFrom:values:lines:title: -> 3 confirm: -> 47 confirm:label: -> 5 confirm:label:trueChoice:falseChoice:cancelChoice:default: -> 1 confirm:orCancel: -> 1 confirm:trueChoice:falseChoice: -> 2 confirm:trueChoice:falseChoice:cancelChoice:default: -> 6 deactivate -> 5 debugProcess:context:label:fullView:notification: -> 1 defer: -> 24 deny: -> 2565 deny:title: -> 2 displayProgress:from:to:during: -> 4 edit:label: -> 4 edit:label:accept: -> 3 fileExistsDefaultAction: -> 1 handleDebugRequest:fromDebuggerSystem: -> 1 handleError: -> 2 handleError:log: -> 2 handleWarningDebugRequest:fromDebuggerSystem: -> 1 inform: -> 98 inform:actionOnClick: -> 1 informUser:during: -> 13 informUserDuring: -> 5 logError: -> 2 lowSpaceWatcherDefaultAction: -> 1 merge:informing: -> 2 multiLineRequest:initialAnswer:answerHeight: -> 5 newDisplayDepthNoRestore: -> 1 newMenuIn:for: -> 15 onPrimitiveError: -> 1 proceed:title: -> 2 question:title: -> 2 questionWithoutCancel: -> 1 questionWithoutCancel:title: -> 2 request: -> 13 request:initialAnswer: -> 19 request:initialAnswer:entryCompletion: -> 1 request:initialAnswer:title: -> 13 request:initialAnswer:title:entryCompletion: -> 6 requestDebuggerOpeningFor: -> 1 requestDebuggerOpeningForProcess:named:inContext: -> 1 requestDebuggerOpeningForWarning: -> 1 requestDebuggerOpeningNamed:inContext: -> 1 requestPassword: -> 3 restoreDisplay -> 3 restoreDisplayAfter: -> 1 spawnNewProcess -> 4 systemNotificationDefaultAction: -> 1 terminateUIProcess -> 1 textEntry: -> 2 textEntry:title: -> 2 textEntry:title:entryText: -> 2 unhandledErrorDefaultAction: -> 3 warningDefaultAction: -> 1 -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 2

Open Call: Object-Centric Breakpoints experiment
by Steven Costiou Nov. 21, 2023

Nov. 21, 2023

Dear Community, 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 0

This week (46/2023) on the Pharo Issue Tracker
by Marcus Denker Nov. 17, 2023

Nov. 17, 2023

# Pharo 11 Backports - backport: Guard RubAbstractTextArea>>#recomputeSelection for empty paragraphs #15140 #15375 https://github.com/pharo-project/pharo/pull/15375 - backport "Defer change list update to avoid a race condition" #14853 #15374 https://github.com/pharo-project/pharo/pull/15374 - 15372-backport-Pharo11-safer-morph-access-in-NECMenuMorphmouseDown-14356 #15373 https://github.com/pharo-project/pharo/pull/15373 # Fixes - Fix scaling of #blankIcon and #notFoundIcon on ThemeIcons #15399 https://github.com/pharo-project/pharo/pull/15399 - 15299-UFFI-should-release-pointers-allocated-for-packing-for-arity #15300 https://github.com/pharo-project/pharo/pull/15300 - 15302-FreeTypeFonts-should-not-use-autorelease-of-ExternalAddresses #15303 https://github.com/pharo-project/pharo/pull/15303 - Calypso: Fix display of extended classes in project view #15314 https://github.com/pharo-project/pharo/pull/15314 - Fix imageCleaner concurrency issue when unifying literals #15385 https://github.com/pharo-project/pharo/pull/15385 - Do not log recompilation in the source file #15398 https://github.com/pharo-project/pharo/pull/15398 - Guard removals of morphs in layouts #1467 https://github.com/pharo-spec/Spec/pull/1467 # Features - Extend ThemeIcons to load the icons for all scales in the icon pack #15323 https://github.com/pharo-project/pharo/pull/15323 - Auto completion should propose globals #15392 https://github.com/pharo-project/pharo/pull/15392 - Calypso: Show content of projects #15315 https://github.com/pharo-project/pharo/pull/15315 # Package Model Cleanup - Packages: Fix missing extensions after class recompiling #15326 https://github.com/pharo-project/pharo/pull/15326 - Introduce a method to get the meta model announcer #15310 https://github.com/pharo-project/pharo/pull/15310 - Packages: Remove #definedSelectors cache #15278 https://github.com/pharo-project/pharo/pull/15278 - Packages: Removing more references to #category #15320 https://github.com/pharo-project/pharo/pull/15320 - RPackage: Deprecate #includesDefinedSelector:ofClass: #15214 https://github.com/pharo-project/pharo/pull/15214 - Package: Move extension methods of RPackage #15346 https://github.com/pharo-project/pharo/pull/15346 - Rename RPackageOrganizer into PackageOrganizer #15360 https://github.com/pharo-project/pharo/pull/15360 - Monticello: Remove usage of RPackageSet #15363 https://github.com/pharo-project/pharo/pull/15363 - Update RPackage dependencies #15393 https://github.com/pharo-project/pharo/pull/15393 - DependencyAnalyzer: Remove usage of RPackageSet #15368 https://github.com/pharo-project/pharo/pull/15368 # Monticello - Remove MCPatchBrowser #15376 https://github.com/pharo-project/pharo/pull/15376 - Monticello: Introduce Monticello-Model #15350 https://github.com/pharo-project/pharo/pull/15350 - Monticello: Simplify method loading #15292 https://github.com/pharo-project/pharo/pull/15292 - Monticello: Remove dead code #15351 https://github.com/pharo-project/pharo/pull/15351 - Monticello: Move mocks to mock package #15361 https://github.com/pharo-project/pharo/pull/15361 - Remove WorkingCopy spotter entries #610 https://github.com/pharo-spec/NewTools/pull/610 # MetaCello - Cleanup metacello #15287 https://github.com/pharo-project/pharo/pull/15287 - Metacello: New cleaning pass #15312 https://github.com/pharo-project/pharo/pull/15312 - Add missing methods for SmalltalkCI #15339 https://github.com/pharo-project/pharo/pull/15339 - Fixes #15342: Monticello: GitHub CI fails with DNU #15344 https://github.com/pharo-project/pharo/pull/15344 - Metacello: fix block evaluation #15362 https://github.com/pharo-project/pharo/pull/15362 # Kernel - Allow to create anonymous classes in a specific environment #15309 https://github.com/pharo-project/pharo/pull/15309 - Fix bug in remake of anonymous classes #15343 https://github.com/pharo-project/pharo/pull/15343 - Undeclared: declare:from: cleanup, first step #15290 https://github.com/pharo-project/pharo/pull/15290 - Remove private system announcer #15355 https://github.com/pharo-project/pharo/pull/15355 - do not hardcode global environment in #removeFromSystem: #15357 https://github.com/pharo-project/pharo/pull/15357 - Add binary selector alias for #newFromArray: for Collection #15316 https://github.com/pharo-project/pharo/pull/15316 # Traits - Traits: Fix bug in dictionary rebuild #15353 https://github.com/pharo-project/pharo/pull/15353 - Speedup #explicitRequirement #15322 https://github.com/pharo-project/pharo/pull/15322 - Traits: Speedup #isFromTrait #15318 https://github.com/pharo-project/pharo/pull/15318 - Rename TraitsV2 into Traits #15319 https://github.com/pharo-project/pharo/pull/15319 - Traits: Do a new cleaning pass over the traits tests and fix file out bug #15304 https://github.com/pharo-project/pharo/pull/15304 - Remove TraitsV2-Compatibility #15325 https://github.com/pharo-project/pharo/pull/15325 # Refactoring Engine - Migrate rename class to driver #15394 https://github.com/pharo-project/pharo/pull/15394 - remove deadcode from driver package #15390 https://github.com/pharo-project/pharo/pull/15390 - RB: A simple fix for abstract methods. No brainer. #15331 https://github.com/pharo-project/pharo/pull/15331 - Remove unused SycRemoveMethodCommand #15337 https://github.com/pharo-project/pharo/pull/15337 - Refactorings: Follow package name convention #15340 https://github.com/pharo-project/pharo/pull/15340 # Tests - Fix #testUndeclared in case of failure #15356 https://github.com/pharo-project/pharo/pull/15356 - Release tests: Improve testNoSentButNotImplementedSelectors #15341 https://github.com/pharo-project/pharo/pull/15341 - Use a test resource for SystemDependenciesTest #15308 https://github.com/pharo-project/pharo/pull/15308 # Cleanup - Some cleanup of CodeExport #15380 https://github.com/pharo-project/pharo/pull/15380 - Deprecate gofer command line #15347 https://github.com/pharo-project/pharo/pull/15347 - Clean AST-Core #15358 https://github.com/pharo-project/pharo/pull/15358 - Remove #isUnitTest #15349 https://github.com/pharo-project/pharo/pull/15349 - Manifest builder should not rely on categories #15324 https://github.com/pharo-project/pharo/pull/15324 - Remove workspace #15284 https://github.com/pharo-project/pharo/pull/15284 - Deprecate TRBProgramNodeVisitor #15305 https://github.com/pharo-project/pharo/pull/15305 - Refactor #inspectionIcons on ThemeIcons to use the #icons accessor #609 https://github.com/pharo-spec/NewTools/pull/609 # Cleanup Trivail - fix icons #15371 https://github.com/pharo-project/pharo/pull/15371 - use allButFirst and simplify expression #15382 https://github.com/pharo-project/pharo/pull/15382 - use allButFirst instead of copyFrom:to: #15369 https://github.com/pharo-project/pharo/pull/15369 - use allButFirst instead of copyFrom:to: #15366 https://github.com/pharo-project/pharo/pull/15366 - Remove deprecated calls #15354 https://github.com/pharo-project/pharo/pull/15354 - Cleanup: usage of notNil in Text-Scanning, Rubric, HeuristicCompletion, NECCompletion, Growl, Regex #15296 https://github.com/pharo-project/pharo/pull/15296 - Cleanup: usage of notNil in Calypse, Microdown, System-Changes, STON, System-Settings #15297 https://github.com/pharo-project/pharo/pull/15297 - Cleanup: Usage of "notNil" and "isEmpty not" in Zinc / Zodiac #15253 https://github.com/pharo-project/pharo/pull/15253

1 0

Stack overflow support?
by Guillermo Polito Nov. 15, 2023

Nov. 15, 2023

Hi all, We started (with many interruptions over the last months) working a bit with Stephane on understanding what is the (positive and negative) impact of stack-overflow support in Pharo. The key idea is that if a process consumes too much stack (potentially because of an infinite recursion) then the process should stop with an exception. ## Why we want better stack consumption control This idea comes up to solve issues that are pretty common and hit especially newbies. For example, imagine you accidentally write an accessor such as ``` A >> foo ^ self foo ``` Students do this all the time, and Iâve also seen it in experienced people who go too fast :). More importantly, such recursions could happen also with not-so-obvious indirect recursions (a sends b, b sends c, c sends a), and these could hit anybody. This is aggravated because the current execution model allows us to have infinite stacks âmeaning: limited by available memory only. This is indeed a nice feature for many use cases but it has its own drawbacks when one of these kind of recursions are hit: - code just loops forever taking space in the stack - when there is no more stack space, context objects are created and moved to the heap - but those contexts are strongly held, so they are never GCed and take up extra space - even worse! they are there adding more work to the GC every time and making the GC run more often looking for space that is not there ## Why Ctrl-dot does not always work Of course, super users know there is this âCtrl dotâ hidden feature that should help you recover from this. First, let's take out of the equation that this is only known by super users. Now, in this situation, when Ctrl-dot is hit it will trigger a handler that suspends the problematic process and opens a debugger on it. But it could happen that, - the stack is so big that the debugger is very sluggish (best-case scenario) - the VM is just flooded doing GCs so maybe the Ctrl dot event does not even arrive at Pharo or the trigger - if the recursion is hit when printing an object (which is more common than you could imagine), opening the debugger could trigger a new recursion and never give back the control to the user ## What are we working on The main idea here is: Can we have a simple and efficient way to prevent such kinds of situations? After many discussions around detecting recursion, we kinda arrived at the simple solution of just detecting a stack overflow. The solution is easy to understand (because itâs like other languages work) and easy to implement because there is already support for that. But this leaves open two questions: - what happens when people want to use the âinfinite stackâ feature? - when should a process stack overflow? What is a sensitive default value? Our draft implementation here https://github.com/pharo-project/pharo-vm/pull/710 <https://github.com/pharo-project/pharo-vm/pull/710> does the following to cope with this: - we can now parametrize the size of the stack (of each stack page to be more accurate) when the VM starts up - the stack overflow check can be disabled per process We also are running experiments to see what could be a sensitive stack size for our normal usages. Here, for example, we ran almost all test cases in Pharo separately (one suite per line below), and we observed how many tests broke (x-axis) with different stack sizes (y-axis). Here we see that most test suites require at least 20-24k to run properly, some go up to 36k of stack before converging (i.e., the number of broken tests does not change). Youâll notice in the graph that There are some scenarios that break all the time. This is because exception handling itself is recursive and may produce more stack overflows depending on the size of the stack between the exception and the exception handler. So some more work is still required, mostly changing Pharo libraries to properly support this. For example: - should tests run in a fresh process with a fresh stack? - should the exception mechanism use less recursion? - resumable exceptions add stack pressure because they do not âunstackâ until the exception is finally handled, meaning that the stack used by exception handling just adds up to the stack of the original code, can we do better here? Probably there are more interesting questions here, thatâs the âwhy" behind this email. Iâm interested in opinions and scenarios you may come up with that should be taken into account. Cheers, Guille

7 9

New blog post on all:objects all: theTime
by Koen De Hondt Nov. 15, 2023

Nov. 15, 2023

Dear Pharo users and developers, After my presentation at ESUGâ23, which has been added to my blog <https://all-objects-all-the-time.st/#/blog/posts/4> too, I wrote an evaluation of Calypso <https://all-objects-all-the-time.st/#/blog/posts/5>, in which I refer to results of the Pharo Browser Survey that I presented at ESUGâ23. It is a long post. It will be the basis for more posts on browsers in Pharo. My blog does not support commenting. If you have any feedback or comment, please feel free to send me a message. Happy reading! Ciao, Koen

2 1

This week (45/2023) on the Pharo Issue Tracker
by Marcus Denker Nov. 10, 2023

Nov. 10, 2023

# Feature - Proposal: new message browser layout #15229 https://github.com/pharo-project/pharo/pull/15229 # Fixes - Calypso: Fix refresh of project view #15281 https://github.com/pharo-project/pharo/pull/15281 - Stay in calypso project view when selecting a class #15247 https://github.com/pharo-project/pharo/pull/15247 - Shout: Fix styling of symbols representing a deprecated global variable #15274 https://github.com/pharo-project/pharo/pull/15274 - Calypso: Add Undefined project #15246 https://github.com/pharo-project/pharo/pull/15246 - Fix clean blocks with dead context on debugger #15153 https://github.com/pharo-project/pharo/pull/15153 - Fix âspanâ in BalloonEngine not being wider than the âdestFormâ #15236 https://github.com/pharo-project/pharo/pull/15236 - Calypso: Fix taskbar label #15226 https://github.com/pharo-project/pharo/pull/15226 # Refactoring Engine - Feat: Add Override method transformation #15225 https://github.com/pharo-project/pharo/pull/15225 # RPackage - Rpackage: Extension methods should know their package #15212 https://github.com/pharo-project/pharo/pull/15212 - Introduce Behavior>>#definedSelectors and #definedMethods and add tests #15264 https://github.com/pharo-project/pharo/pull/15264 - Simplify ClassRemoved and MethodRemoved now that packages are preserved #15262 https://github.com/pharo-project/pharo/pull/15262 - Make class know its package tag instead of its category #15239 https://github.com/pharo-project/pharo/pull/15239 - Ring-Definitions: Remove concept of categories #15235 https://github.com/pharo-project/pharo/pull/15235 - Deprecate Class>>#category: and ShiftClassBuilder>>#category(:) #15237 https://github.com/pharo-project/pharo/pull/15237 - Packages: Do some cleanings #15219 https://github.com/pharo-project/pharo/pull/15219 # Fluid Class Definitions - Fix more deprecated messages in traits #15275 https://github.com/pharo-project/pharo/pull/15275 # Compiler - Opal: Add concept of prior methods #15291 https://github.com/pharo-project/pharo/pull/15291 - Fix trait method recompilation and clean #15263 https://github.com/pharo-project/pharo/pull/15263 - Opal: Make plugins no-op to not crash during the loading #15289 https://github.com/pharo-project/pharo/pull/15289 # Undeclared - Introduce a specific collection for undeclareds #15271 https://github.com/pharo-project/pharo/pull/15271 - Ensure no association is added to the system dictionary #15241 https://github.com/pharo-project/pharo/pull/15241 # Tests - Clean traits tests #15243 https://github.com/pharo-project/pharo/pull/15243 - Release test: Add test that all packages are defined in a baseline #15273 https://github.com/pharo-project/pharo/pull/15273 - updates the #manuallyResolvedDependencies #15286 https://github.com/pharo-project/pharo/pull/15286 - Remove some classes generated by tests #15272 https://github.com/pharo-project/pharo/pull/15272 - Fix one more test cleanup #15248 https://github.com/pharo-project/pharo/pull/15248 - Improve cleanups of tests #15244 https://github.com/pharo-project/pharo/pull/15244 - Improve tests logs #15242 https://github.com/pharo-project/pharo/pull/15242 - Improve logs while running tests #15217 https://github.com/pharo-project/pharo/pull/15217 # Cleanup - Ring: Simplify Ring-Definitions/Ring-Definitions-Containers #15230 https://github.com/pharo-project/pharo/pull/15230 - add trace to #iconNamed:ifNone: to log all old names #15200 https://github.com/pharo-project/pharo/pull/15200 - Fix some icon references #15276 https://github.com/pharo-project/pharo/pull/15276 - Remove unused Calypso-SystemPlugins-Monticello-Queries #15270 https://github.com/pharo-project/pharo/pull/15270 - Merge Metacello-PharoExtensions into Metacello-Base #15215 https://github.com/pharo-project/pharo/pull/15215 - Calypso: Simplify ClyExtendingPackagesQuery adn clean package API #15221 https://github.com/pharo-project/pharo/pull/15221 # Trivial - Fix some deprecations #15238 https://github.com/pharo-project/pharo/pull/15238 - Cleanup: do not use notNil in Ring #15250 https://github.com/pharo-project/pharo/pull/15250 - Cleanup: usage of #notNil in Morphic #15260 https://github.com/pharo-project/pharo/pull/15260 - Cleanup: usage of #notNil in UnifiedFFI #15256 https://github.com/pharo-project/pharo/pull/15256 - Cleanup: Usage of notNil in Kernel #15269 https://github.com/pharo-project/pharo/pull/15269 - Cleanup: usage of #notNil in Athens, Graphics, Polymorph, FreeType, EmbeddedFreeType and FormCanvas #15267 https://github.com/pharo-project/pharo/pull/15267

1 0

Last week (44/2023) on the Pharo Issue Tracker
by Marcus Denker Nov. 6, 2023

Nov. 6, 2023

# Pharo 11 - Backport Pharo11: Optimize Dictionary>>unreferencedKeys #15196 https://github.com/pharo-project/pharo/pull/15196 # External Packages - Update roassal v1.05b #15159 https://github.com/pharo-project/pharo/pull/15159 # Features - Calypso: Introduce a project view based on baselines in the image #15155 https://github.com/pharo-project/pharo/pull/15155 https://github.com/pharo-project/pharo/pull/15176 # Fixes - Spotter not opening minimized window (issue #603) #604 https://github.com/pharo-spec/NewTools/pull/604 - Following symbolic links when canonicalising FileReferences. #14773 https://github.com/pharo-project/pharo/pull/14773 - fix 13709: Code Completion: completion sometimes has its window in a â¦ #15151 https://github.com/pharo-project/pharo/pull/15151 - Fix moving classes in tags #15146 https://github.com/pharo-project/pharo/pull/15146 - Force rescheduling of inactive process when changing its priority (fixes #14701) #14905 https://github.com/pharo-project/pharo/pull/14905 - Replacing the use of species new with copyEmpty. #15150 https://github.com/pharo-project/pharo/pull/15150 - Fix depth conversion in #image:size: on AlphaImageMorph to use the original Formâs extent #15170 https://github.com/pharo-project/pharo/pull/15170 - Fix random bug in auto completion #15175 https://github.com/pharo-project/pharo/pull/15175 - Inlining select:thenCollect: and reject:thenCollect: to not do two iterations on the same collection #15149 https://github.com/pharo-project/pharo/pull/15149 - Replace extracted expression only in containing scope (fixes #14771) #14906 https://github.com/pharo-project/pharo/pull/14906 - Calypso: Fix regression in taskbar label #15220 https://github.com/pharo-project/pharo/pull/15220 - Refactor AlphaImageMorph to replace âcachedFormâ by âcachedFormSetâ #15189 https://github.com/pharo-project/pharo/pull/15189 # RPackage - RPackage: Remove last listeners to SystemAnnouncer #15208 https://github.com/pharo-project/pharo/pull/15208 - RPackage: Do not register to MethodAdded #15180 https://github.com/pharo-project/pharo/pull/15180 - Calypso:â¯Improve some namings on package tags #15179 https://github.com/pharo-project/pharo/pull/15179 - RPackage: Clean protocols management #15132 https://github.com/pharo-project/pharo/pull/15132 # Fluid ClassDefs / ClassBuilder - Reduce usage of category for protocol #15166 https://github.com/pharo-project/pharo/pull/15166 - Remove more old class creation API #15165 https://github.com/pharo-project/pharo/pull/15165 - Do a pass on shift after recent improvements #15187 https://github.com/pharo-project/pharo/pull/15187 - Deprecate ClassRenamed>>category #15186 https://github.com/pharo-project/pharo/pull/15186 - Simplify ChunkImportTestCase #15181 https://github.com/pharo-project/pharo/pull/15181 # Monticello / Metacello - Monticello: Fix loading of erroneous methods #15203 https://github.com/pharo-project/pharo/pull/15203 - Monticello: Fix problem in package loading logic #15207 https://github.com/pharo-project/pharo/pull/15207 - Monticello: Multiple MethodAddition cleanings (announce protocol changes, compile before installing, cleanup) #15172 https://github.com/pharo-project/pharo/pull/15172 - Metacello: Clean the way to create a class #15188 https://github.com/pharo-project/pharo/pull/15188 # Package Dependencies - Cut dependency from AST-Core-Tests to SystemCommands-SourceCodeCommands #15141 https://github.com/pharo-project/pharo/pull/15141 - Split finalization registry from WeakArray and sort dependencies #15139 https://github.com/pharo-project/pharo/pull/15139 - Fix cyclic dependencies between compiler and ASTs/parser and their tests #15144 https://github.com/pharo-project/pharo/pull/15144 - Update dependencies to Roassal and Array2D #15148 https://github.com/pharo-project/pharo/pull/15148 - Pusing down dependencies of Collection-Abstract #15138 https://github.com/pharo-project/pharo/pull/15138 - Move critics UI methods to critic UI package #15184 https://github.com/pharo-project/pharo/pull/15184 # Variables / Undeclared - Another pass on #usingMethods for UndeclaredVariable: filter for installed methods #15190 https://github.com/pharo-project/pharo/pull/15190 - SystemDictionary>>declare:from: should not be an extension #15197 https://github.com/pharo-project/pharo/pull/15197 # CI / Tests - tiny speedup for testNoShadowedVariablesInMethods #15173 https://github.com/pharo-project/pharo/pull/15173 - Guard RubAbstractTextArea>>#recomputeSelection for empty paragraphs #15140 https://github.com/pharo-project/pharo/pull/15140 - Improve ClassFactoryForTestCase #15185 https://github.com/pharo-project/pharo/pull/15185 # Cleanup - Remove #acceptsLoggingOfCompilation #15182 https://github.com/pharo-project/pharo/pull/15182 - Bootstrap: Remove dead code #15195 https://github.com/pharo-project/pharo/pull/15195 - Fix DateParser comment #15174 https://github.com/pharo-project/pharo/pull/15174

1 0

Pragma Improvements: Identity, sourceNode and Inspector
by Marcus Denker Oct. 30, 2023

Oct. 30, 2023

Last week we merged some improvements related to Pragma in Pharo12 1) Pragma will not be shalowCopied by AdditionalMethodState anymore when growing/shrinking This was a bit odd, but AdditionalMethodState was calling #shalowCopy on the pragmas (and Associations) that are contained in it. This was bad for many reasons: - makes it hard to e.g. cache Pragmas by Identity (we had a bug due to that) - lots of copies are created during creation of a CompiledMethod and usage of Method Properties see the two PRs: - 15074-Pragmas-lost-when-updating-methods #15087 https://github.com/pharo-project/pharo/pull/15087 - AdditionalMethodState: do not copy the Associations/Pragmas when growing or shrinking #15090 https://github.com/pharo-project/pharo/pull/15090 2) make sure to create the Pragma *once* from the RBPragmaNode If you look at the senders of #asPragma, there used to be more than one. To make sure that Identity is preserved (and simplify things), we now create the Pragma *once* during name analysis. In OCASTSemanticAnalyzer>>#visitPragmaNode:, the Pragma instance is now created and added to the RBPragmaNode (there is now a pragma instance variable with a getter). ``` visitPragmaNode: aPragmaNode | varNode | super visitPragmaNode: aPragmaNode. aPragmaNode pragma: aPragmaNode asPragma. aPragmaNode selector = #compilerOptions: ifTrue: [ aPragmaNode pragma sendTo: self compilationContext ]. ... ``` This means that we can now use it in OCASTTranslator >> visitPragmaNode: instead of calling #asPragma: ``` visitPragmaNode: aPragmaNode | var | aPragmaNode isParseError ifTrue: [ ^self ]. methodBuilder addPragma: aPragmaNode pragma. ... ``` This should make it easier to (in the future) experiment with the idea to use subclasses of Pragma. 3) add #sourceNode We never added #sourceNode on Pragma... now we have it. This uses the idea that the order is the same of Pragmas on the CompiledMethod and RBPragmaNodes on the RBMethodNode: sourceNode [ | index | index := method pragmas identityIndexOf: self. ^ method ast pragmas at: index see PR #15092 for both 2 and 3: https://github.com/pharo-project/pharo/pull/15092 4) with #sourceNode implemented, we can improve the source view of the inspector (the default view). See PR https://github.com/pharo-spec/NewTools/pull/602

1 0

This week (43/2023) on the Pharo Issue Tracker
by Marcus Denker Oct. 30, 2023

Oct. 30, 2023

# Pharo 11 - [P11] Add Support for proxy in Iceberg #15099 https://github.com/pharo-project/pharo/pull/15099 - Make finalization registry a normal strong double linked list #15107 https://github.com/pharo-project/pharo/pull/15107 - [P11] Update document browser to 1.0.1 to 1.0.2, which depends on iceberg 2.2.2 #15130 https://github.com/pharo-project/pharo/pull/15130 - Honouring Proxy Settings in P11 #1750 https://github.com/pharo-vcs/iceberg/pull/1750 # Fixes - Make finalization registry a normal strong double linked list P12 #15108 https://github.com/pharo-project/pharo/pull/15108 - Fix Jump to test method from implementors view #15045 https://github.com/pharo-project/pharo/pull/15045 - 15074-Pragmas-lost-when-updating-methods #15087 https://github.com/pharo-project/pharo/pull/15087 - AdditionalMethodState: do not copy the Associations/Pragmas when growing or shrinking #15090 https://github.com/pharo-project/pharo/pull/15090 # Features - Improve the inspector for Pragma to highlight the pragma in the source #602 https://github.com/pharo-spec/NewTools/pull/602 - Refactor ImageMorph to support more than one Form depicting the same image at different scales #14998 https://github.com/pharo-project/pharo/pull/14998 - Icenberg: Adding support for Proxy URL #1748 https://github.com/pharo-vcs/iceberg/pull/1748 # Packages Cleanup - RPackage: Create packages for extension protocols without announcements #14552 https://github.com/pharo-project/pharo/pull/14552 - Do not use categories in ShiftClassInstaller #15122 https://github.com/pharo-project/pharo/pull/15122 - Fix bug marking too many packages as dirty in Iceberg #15073 https://github.com/pharo-project/pharo/pull/15073 - Fix moving a class from a tag in Calypso #15077 https://github.com/pharo-project/pharo/pull/15077 - RPackage: Simplify protocol management #15080 https://github.com/pharo-project/pharo/pull/15080 - Improve ShiftClassBuilder>>category: #15094 https://github.com/pharo-project/pharo/pull/15094 - Deprecate ClassRecategorized #15127 https://github.com/pharo-project/pharo/pull/15127 - Do not announce method recategorization when removing a selector from a protocol #15133 https://github.com/pharo-project/pharo/pull/15133 - SpChangeSorterPresenter shouldnt use ClassRecategorized #601 https://github.com/pharo-spec/NewTools/pull/601 # Monticello - Monticello: Improve MCZ management #15114 https://github.com/pharo-project/pharo/pull/15114 - Introduce and use CategoryConverter #15102 https://github.com/pharo-project/pharo/pull/15102 - Improve MCSystemCategoryParser #15086 https://github.com/pharo-project/pharo/pull/15086 - Monticello: remove unused announcements #15082 https://github.com/pharo-project/pharo/pull/15082 - Monticello: Make MethodAddition closer to system behavior #15081 https://github.com/pharo-project/pharo/pull/15081 - Monticello: Class/Trait definition creation shouldnt use categories #15088 https://github.com/pharo-project/pharo/pull/15088 - Monticello: Add an option to read old format #15103 https://github.com/pharo-project/pharo/pull/15103 - Update location of setting the MCZ old format flag #15111 https://github.com/pharo-project/pharo/pull/15111 # Metacello - Deprecate MetacelloPlatfrom>>#authorName: #15079 https://github.com/pharo-project/pharo/pull/15079 - Simplify bootstraping of Metacello #15072 https://github.com/pharo-project/pharo/pull/15072 - Simplify Metacello platform code #15066 https://github.com/pharo-project/pharo/pull/15066 - Move regex core loading #15069 https://github.com/pharo-project/pharo/pull/15069 # Compiler - RBPragmaNode/Pragma: add #sourceNode, reduce #asPragma #15092 https://github.com/pharo-project/pharo/pull/15092 - Cleanup: #recompile and CompilerPlugin tests #15109 https://github.com/pharo-project/pharo/pull/15109 - Undeclared: keep weak reference to all methods using the Undeclared Variable #15100 https://github.com/pharo-project/pharo/pull/15100 - Add test: reading 'thisContext' in a DoIt #15117 https://github.com/pharo-project/pharo/pull/15117 - Merge OCPragmaTest into MethodPragmaTest #15113 https://github.com/pharo-project/pharo/pull/15113 - Fix testRecompileMethodToInBlockContext++ using clean blocks #605 https://github.com/pharo-spec/NewTools/pull/605 # Bootstrap - Remove BaselineOfTelePharoSupport #15119 https://github.com/pharo-project/pharo/pull/15119 - Improve the management of TTranscript #15116 https://github.com/pharo-project/pharo/pull/15116 # Refactoring Engine - Refactor: move precondition checking code to checkPreconditions #15078 https://github.com/pharo-project/pharo/pull/15078 # Cleanup - Deprecate old class creation methods #14837 https://github.com/pharo-project/pharo/pull/14837 - Move traceCr & co to non interactive transcript #15115 https://github.com/pharo-project/pharo/pull/15115 - Calypso: Remove duplicated registration of SycRemoveClassCommand #15084 https://github.com/pharo-project/pharo/pull/15084 - remove TextEditor #15064 https://github.com/pharo-project/pharo/pull/15064 - Cleanup Message Hierarchy #15095 https://github.com/pharo-project/pharo/pull/15095 # Trivial Cleanup - Cleanup: TIterateTest>>#testSumNumbers #15124 https://github.com/pharo-project/pharo/pull/15124 - Clean AthensFontDescription>>#asString #15123 https://github.com/pharo-project/pharo/pull/15123 - Small cleanup: use pragma, not #expectedFailures method #15112 https://github.com/pharo-project/pharo/pull/15112 - remove two duplicated methods #15097 https://github.com/pharo-project/pharo/pull/15097 - Rewrite == nil ifFalse: into ifNotNil: #15101 https://github.com/pharo-project/pharo/pull/15101 - Rewrite notNil ifTrue: into ifNotNil: in packages starting by M #15129 https://github.com/pharo-project/pharo/pull/15129 - Transform notNil ifFalse: into ifNil: #15128 https://github.com/pharo-project/pharo/pull/15128 - Rewrite = nil ifTrue: to ifNil: #15083 https://github.com/pharo-project/pharo/pull/15083 - Rewrite notNil ifTrue: into ifNotNil: #15135 https://github.com/pharo-project/pharo/pull/15135 - Rewrite == nil ifTrue: to ifNil: #15085 https://github.com/pharo-project/pharo/pull/15085 - Cleanup: CornerGripMorph should be abstract #15068 https://github.com/pharo-project/pharo/pull/15068

1 0

VM Release 10.0.8
by Guillermo Polito Oct. 23, 2023

Oct. 23, 2023

Hi all, TL;DR; update your launcher VMs and your download scripts! There is a new VM version: release 10.0.8 which fixes, among others, a performance regression that showed in some cases that overly relied on the interpreter. See below the changes log, and for those interested, the fix for the performance issue is here: https://github.com/pharo-project/pharo-vm/pull/705 <https://github.com/pharo-project/pharo-vm/pull/705> What's Changed Fixes #14768: File class>>primFileAttributesð· answers corrupted result by @akgrant43 <https://github.com/akgrant43> in #697 <https://github.com/pharo-project/pharo-vm/pull/697> Fix/speed regression by @tesonep <https://github.com/tesonep> in #705 <https://github.com/pharo-project/pharo-vm/pull/705> Full Changelog: v10.0.7...v10.0.8 <https://github.com/pharo-project/pharo-vm/compare/v10.0.7...v10.0.8>

2 1