December 2020 - Pharo-dev - lists.pharo.org

Re: Progress Report -> Refactoring Project - (November 30 - December 4)

by Sean P. DeNigris

Sounds great! Thanks for the update :) Keep us posted... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 9, 2020

Pharo 8 Image blows up after restart

by Sabine Manaa

Hi, I have the following problem: sometimes, after restarting my Pharo 8 image on mac, it is not responsive and it blows up the memory. I tried with commandline handler eval "self halt" and with Smalltalk addToStartUpList: but both is too late - the Image starts and blows up and is not responsive. I can not interrupt it and it grows to several GB memory (eg after 20 seconds 10 GigaByte! ) and I have to kill it. Anyone having an idea what I can do to find the reason for this? Sabine -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 8, 2020

New version of FFICHeaderExtractor v1.0.2 and OSubprocess v1.3.0

by StÃ©phane Ducasse

Hi Some news since StandardFileStream got deprecated in Pharo 80, we removed it form Pharo 90. We updated - FFICHeaderExtractor now version v1.0.2 got migrated to Tonel and pharo-contributions + github actions https://github.com/pharo-contributions/OSSubprocess - OSSubprocess version v1.3.0 is out https://github.com/pharo-contributions/OSSubprocess Stef -------------------------------------------- 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

Dec. 7, 2020

Re: This week (49/2020) on the Issue Tracker

by Esteban Lorenzano

On Dec 7 2020, at 5:22 pm, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > El 7 dic 2020, a las 17:02, Sean P. DeNigris <sean(a)clipperadams.com> escribiÃ³: > > > > Wow! Impressive list :) > > > > > > Marcus Denker-4 wrote > >> - Activation in single click (which triggers column expansion) is now > >> default for inspections (it was double click, but it felt weird). > > > > -1 on this. The problem with single click is that it adds a column even when > > you don't want it to. This was very annoying. IMO after using the > > double-click for a few months (it took that long to get used to it), the > > extra click is significantly less disruptive than the unnecessary column > > adding. > > > +1 on this. > That is why I made double click by default when I first implemented it. > Every time you click on glamour everything shifts, rotates, moves, it is super disrupting when you **just want to click**. > > The single click should not shuffle the UI, or the UI should provide a way to âclickâ on something without moving everything around. that's why it was double click first and is a setting now. I preferred the other way too, but people complained so I added a setting. we are still trying so we can revert the default. but there is a bug around I want to fix: default activation event is double click or enter, and that's not how it works now (easy to fix, though). Esteban

Dec. 7, 2020

Progress Report -> Refactoring Project - (November 30 - December 4)

by EVELYN CUSI LOPEZ

Hi everyone, Last week I did these tasks: - Review refactoring metamodel - Check if all tests passed and if these have sense - Refactor some tests - Add tests (https://github.com/pharo-project/pharo/pull/7965) - Do report if refactorings has or not UI command, if work or not work, if need add more tests. You can see this report in: https://github.com/Lin777/PharoRefactorings Tasks for this week: - Review commander2: http://books.pharo.org/booklet-Commander/pdf/2020-11-30-booklet-Commander20… - Review refactoring2, and compare with refactoring. Show pros and cons - Fix issues of Extract method: - https://github.com/pharo-project/pharo/issues/4429 - https://github.com/pharo-project/pharo/issues/5269 - https://github.com/pharo-project/pharo/issues/4973 - Fix issues Undo refactoring: - https://github.com/pharo-project/pharo/issues/5010 Cheers, Evelyn

Dec. 7, 2020

Re: This week (49/2020) on the Issue Tracker

by Guillermo Polito

> El 7 dic 2020, a las 17:02, Sean P. DeNigris <sean(a)clipperadams.com> escribiÃ³: > > Wow! Impressive list :) > > > Marcus Denker-4 wrote >> - Activation in single click (which triggers column expansion) is now >> default for inspections (it was double click, but it felt weird). > > -1 on this. The problem with single click is that it adds a column even when > you don't want it to. This was very annoying. IMO after using the > double-click for a few months (it took that long to get used to it), the > extra click is significantly less disruptive than the unnecessary column > adding. +1 on this. That is why I made double click by default when I first implemented it. Every time you click on glamour everything shifts, rotates, moves, it is super disrupting when you **just want to click**. The single click should not shuffle the UI, or the UI should provide a way to âclickâ on something without moving everything around. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 7, 2020

Re: This week (49/2020) on the Issue Tracker

by Sean P. DeNigris

Wow! Impressive list :) Marcus Denker-4 wrote > - Activation in single click (which triggers column expansion) is now > default for inspections (it was double click, but it felt weird). -1 on this. The problem with single click is that it adds a column even when you don't want it to. This was very annoying. IMO after using the double-click for a few months (it took that long to get used to it), the extra click is significantly less disruptive than the unnecessary column adding. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 7, 2020

This week (49/2020) on the Issue Tracker

by Marcus Denker

Spec v0.5 ========== New Inspector is now default in Pharo! - Inspector Introduces concept of "inspection concept" which allows to configure how the presentation will be show (and if it will be shown). For now it does not do much, but potential is huge. - Inspector uses SpMillerPaginatorPresenter. - Inspector uses popover to allow command expansion in the toolbar (otherwise is too big). - Inspector panes are closeable now. - Inspector, Playground now understand <meta+g> command - Playground pages now can "open in new page". - Activation in single click (which triggers column expansion) is now default for inspections (it was double click, but it felt weird). - Added several inspections (extensions to objects) to match what we had before. - Most commands now delegate its behavior to their contexts to allow better handling of them. - Introduce "icon providers" to handle how icons are provided in applications. - Refactor the way icons are used in StPharoApplication to allow switching of icon sets and the gradual transition from current naming to a better, semantic way of name icons. - Fixes #128 - Fixes pharo-project/pharo#7700 - Fixes #123 - Several bugfixes. Small Speed Improvements ======== Some tiny improvements, but the morph related code (like #hasDropShadow) is called in the main rendering loop. - optimize-hasDropShadow #7917 https://github.com/pharo-project/pharo/pull/7917 - Cleanup code for Morph properties #7903 https://github.com/pharo-project/pharo/pull/7903 - Do not allocate a block when executing #isInstalled #7936 https://github.com/pharo-project/pharo/pull/7936 Fixes ===== - Fix #7898 #7918 https://github.com/pharo-project/pharo/pull/7918 - Fix infinite recursion upon send of not-understood message to nil #7902 https://github.com/pharo-project/pharo/pull/7902 - [fix] fixes selector extraction when asking for it at the first charaâ¦ #7881 https://github.com/pharo-project/pharo/pull/7881 Improvements / New Features =========================== - Improve-isHaltNode #7919 It was detecting all sends to Halt, now it filters for selectors in the right category there. https://github.com/pharo-project/pharo/pull/7919 - Implementing hasProperty in Behavior and RPackage. #7875 https://github.com/pharo-project/pharo/pull/7875 - Add ExternalAddress class>>#allocate:bytesDuring: #7727 https://github.com/pharo-project/pharo/pull/7727 - No "inconsistent method classification" for methods in deprecated method category #7868 https://github.com/pharo-project/pharo/pull/7868 Cleaning unused Variables ========================= After all vars are cleaned, we will add a ReleaseTest so this can never happen again. - Remove unused ivars from HeuristicCompletion packages #7943 https://github.com/pharo-project/pharo/pull/7943 - Care on unreferenced variables in OpalCompiler packages #7944 https://github.com/pharo-project/pharo/pull/7944 - Remove unused environment ivar from BuilderManifestTest #7940 https://github.com/pharo-project/pharo/pull/7940 - Removed unused instance variable traitDefinition in CDTraitParserTest #7886 https://github.com/pharo-project/pharo/pull/7886 Halt Cleanups ============= There should be no #halt (and similar) sends in the code, Iif it is used for testing, this should be tagged. The goal then is to add a ReleaseTest to make sure the code stays clean. This makes the "Browse Breakpointsâ feature more usable, too - tag more tests with <haltOrBreakpointForTesting> #7926 https://github.com/pharo-project/pharo/pull/7926 - 7927-halt-left-in-OmBlockrefreshIfNeededStartingAtsince #7931 https://github.com/pharo-project/pharo/pull/7931 Cleanups: remove Code ====================== - 7830-DummyFindReplaceService-not-documented-not-used-Can-be-removed #7891 https://github.com/pharo-project/pharo/pull/7891 - Remove DeprecatedFileStream package #7885 https://github.com/pharo-project/pharo/pull/7885 - shouldDisplayOnTopContext-seems-to-be-not-needed #7873 https://github.com/pharo-project/pharo/pull/7873 Cleanups ======== And again lots of small cleanupsâ¦ think about them not as how important one of them is. This about what happens if you do 10.000 of those. - 7914-Fluid-builder-should-encapsulate-call-to-install-the-class #7921 https://github.com/pharo-project/pharo/pull/7921 - on local variable, we had #isUnused, while on Behavior is was #isUsed #7887 https://github.com/pharo-project/pharo/pull/7887 - RBPragmaNode-accessor-simpler #7950 https://github.com/pharo-project/pharo/pull/7950 - Cleanup tests and mock package of DrTest (Second attempt) #7933 https://github.com/pharo-project/pharo/pull/7933 - Tag classes in DrTests-CommentsToTests #7913 https://github.com/pharo-project/pharo/pull/7913 - Tag classes in DrTests-TestsRunner #7910 https://github.com/pharo-project/pharo/pull/7910 - Typo in DTStatusUpdate class comment #7911 https://github.com/pharo-project/pharo/pull/7911 - 7904-Improve-comment-of--methods #7905 https://github.com/pharo-project/pharo/pull/7905 - Fixed #7840. Deprecating hasPropertyNamed: #7880 https://github.com/pharo-project/pharo/pull/7880 - Cleanup CompiledMethodTest #7874 https://github.com/pharo-project/pharo/pull/7874 - Creating abstract method byteAt: in Integer #7883 https://github.com/pharo-project/pharo/pull/7883 - Deprecated Behavior methods should go to Deprecated Behavior methods â¦ #7866 https://github.com/pharo-project/pharo/pull/7866

Dec. 4, 2020

Re: [ANN] New inspector as default in your Pharo9 image!

by Tudor Girba

Congratulations! It so cool to see that you preserved moldability. Even more exciting is to see the object breakpoints working. This will make such a difference. Awesome work. Cheers, Doru > On Dec 3, 2020, at 4:57 PM, Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > > Hi all, > > Today we are introducing our new inspector based on NewTools. > This is part of our effort to replace all old tools (some based on Glamour, some based on Spec1 and some others in plain Morphic) to meet same design guidelines and prepare them for the future of the Pharo IDE. > Next weeks we will integrate the new Spotter, which will be the end of the Glamour migration effort. Some work on migrating Iceberg and other Spec1 tools are on its way (and they will be merged as soon as work reach beta status) > > The most important changes for the new inspector are the inclusion of object-centric breakpoints, that apply only for the inspected object: > > - Right click on any instance variable in the raw view shows a menu to install a breakpoint on accesses to that variable: the execution will break whenever this variable is read, written or both (this is configurable) but only for the inspected object. > - Right click on any method in the "Meta" view shows a menu to install a breakpoint on that method: the execution will break when that method is called but only for the inspected object. > - The toolbar shows a button to configure a breakpoint on state access for the inspected object: the execution will break whenever any instance variable of the object is accessed (read, write or both and configurable) but only for the inspected object. > - The breakpoint pane shows all breakpoints installed for the inspected object and for all other instances of the object's class. Use this pane to deactivate or to uninstall object-centric breakpoints. > > Cheers! > Esteban > > ps: Yes, there will be bugs (maybe a lot) and missing inspector extensions. I'm counting on you to report (or/and helping implement it) -- feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

Dec. 3, 2020

[ANN] New inspector as default in your Pharo9 image!

by Esteban Lorenzano

Hi all, Today we are introducing our new inspector based on NewTools. This is part of our effort to replace all old tools (some based on Glamour, some based on Spec1 and some others in plain Morphic) to meet same design guidelines and prepare them for the future of the Pharo IDE. Next weeks we will integrate the new Spotter, which will be the end of the Glamour migration effort. Some work on migrating Iceberg and other Spec1 tools are on its way (and they will be merged as soon as work reach beta status) The most important changes for the new inspector are the inclusion of object-centric breakpoints, that apply only for the inspected object: - Right click on any instance variable in the raw view shows a menu to install a breakpoint on accesses to that variable: the execution will break whenever this variable is read, written or both (this is configurable) but only for the inspected object. - Right click on any method in the "Meta" view shows a menu to install a breakpoint on that method: the execution will break when that method is called but only for the inspected object. - The toolbar shows a button to configure a breakpoint on state access for the inspected object: the execution will break whenever any instance variable of the object is accessed (read, write or both and configurable) but only for the inspected object. - The breakpoint pane shows all breakpoints installed for the inspected object and for all other instances of the object's class. Use this pane to deactivate or to uninstall object-centric breakpoints. Cheers! Esteban ps: Yes, there will be bugs (maybe a lot) and missing inspector extensions. I'm counting on you to report (or/and helping implement it)

Dec. 3, 2020