- Pharo-dev - lists.pharo.org

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

Re: [ANN] New UI renderer with Hi-DPI support (Beta testing)

by Guillermo Polito

The slides are here, I donât know about any recordings, maybe Ronie will repeat it and a record it later? http://rmod-files.lille.inria.fr/Team/Presentations/2020-form-scene-graph-S… > El 30 nov 2020, a las 11:09, Ben Coman <btc(a)openinworld.com> escribiÃ³: > > Was there any recording? > > On Thu, 26 Nov 2020 at 21:47, Ronie Salgado <roniesalg(a)gmail.com <mailto:roniesalg@gmail.com>> wrote: > Hello, > > Today I am giving a talk about this at 4 pm, Paris time through the Discord. > > > Best regards, > Ronie > > El miÃ©, 25 nov 2020 a las 16:11, Ronie Salgado (<roniesalg(a)gmail.com <mailto:roniesalg@gmail.com>>) escribiÃ³: > Hello, > > The last months I have been working in a new UI rendering framework for Pharo based on adding an intermediate scene graph with the purpose of improving rendering speed, and with the side effect of making the whole UI scalable and adding support for Hi-DPI rendering. > > We would appreciate that people could start testing this so that we can find bugs and stabilize it. For using this the latest Pharo 9 image and headless vm is required. > > Form Scene Graph repo, installation and settings repository: https://github.com/ronsaldo/form-scene-graph <https://github.com/ronsaldo/form-scene-graph> > > Known issues: > - Iceberg is hanging on fetches and pushes only when using the Athens backend. No segmentation fault or debugger is being launched here so this is difficult to fix. When having to deal with this issue we recommend using the OSWindowGenericRenderer backend (SDL2). > > Best regards, > Ronie >

Nov. 30, 2020

Re: [ANN] New UI renderer with Hi-DPI support (Beta testing)

by Ben Coman

Was there any recording? On Thu, 26 Nov 2020 at 21:47, Ronie Salgado <roniesalg(a)gmail.com> wrote: > Hello, > > Today I am giving a talk about this at 4 pm, Paris time through the > Discord. > > > Best regards, > Ronie > > El miÃ©, 25 nov 2020 a las 16:11, Ronie Salgado (<roniesalg(a)gmail.com>) > escribiÃ³: > >> Hello, >> >> The last months I have been working in a new UI rendering framework for >> Pharo based on adding an intermediate scene graph with the purpose of >> improving rendering speed, and with the side effect of making the whole UI >> scalable and adding support for Hi-DPI rendering. >> >> We would appreciate that people could start testing this so that we can >> find bugs and stabilize it. For using this the latest Pharo 9 image and >> headless vm is required. >> >> Form Scene Graph repo, installation and settings repository: >> https://github.com/ronsaldo/form-scene-graph >> >> Known issues: >> - Iceberg is hanging on fetches and pushes only when using the Athens >> backend. No segmentation fault or debugger is being launched here so this >> is difficult to fix. When having to deal with this issue we recommend using >> the OSWindowGenericRenderer backend (SDL2). >> >> Best regards, >> Ronie >> >>

Nov. 30, 2020

Re: [ANN] New Pharo VM released (v8.6.1)

by Martin McClure

Thanks Pablo, that makes sense. Regards, -Martin On 11/27/20 4:52 AM, tesonep(a)gmail.com wrote: > Hi Martin, yes, it is true. I have to rollback the change because it > was a compatibility issue with Debian 9.11, and this version is the > one used by Jenkins docker images. > I will do a release as soon as I can fix it. I want to push OBS to the > last step to be productive. There is a lot of work on that and we need > to profit it. > The headless VM in Linux has been updated to the latest and that one > has not been rollbacked. > > On Fri, Nov 27, 2020 at 5:48 AM Martin McClure <martin(a)hand2mouse.com> wrote: >> Is this new VM available for Linux? I only see Windows and Mac VMs that >> are dated 2020-11-02. >> In the launcher (launcher 2.2, still the latest AFAICT) refreshing the >> 90-x64 VM just re-downloads the one from 2020-02-11. >> >> Thanks, >> -Martin >> >> On 11/2/20 7:48 AM, tesonep(a)gmail.com wrote: >>> Hi, >>> this is an announcement of a new release of the Pharo VM. This >>> new version is available to be downloaded through get-pharo scripts >>> and through the Pharo Launcher. From the Pharo Launcher, remember to >>> update the VM from the VM manager window. >>> >>> This version includes a series of improvements: >>> >>> - Unification of code base with the headless VM >>> - Preparation for supporting HDPI displays. >>> - Improvements in the speed of Threaded FFI (40x times faster in >>> SameThread runner and 2x in Threaded worker). >>> - Better handling of semaphores >>> - Improvements in the loading of large images (better buffering) >>> - Better support for headless execution on non-main thread >>> >>> Please let me know if you find any issues. >>> >>> Cheers, Pablo >>> >

Nov. 27, 2020

Re: [ANN] New Pharo VM released (v8.6.1)

by tesonep＠gmail.com

Hi Martin, yes, it is true. I have to rollback the change because it was a compatibility issue with Debian 9.11, and this version is the one used by Jenkins docker images. I will do a release as soon as I can fix it. I want to push OBS to the last step to be productive. There is a lot of work on that and we need to profit it. The headless VM in Linux has been updated to the latest and that one has not been rollbacked. On Fri, Nov 27, 2020 at 5:48 AM Martin McClure <martin(a)hand2mouse.com> wrote: > > Is this new VM available for Linux? I only see Windows and Mac VMs that > are dated 2020-11-02. > In the launcher (launcher 2.2, still the latest AFAICT) refreshing the > 90-x64 VM just re-downloads the one from 2020-02-11. > > Thanks, > -Martin > > On 11/2/20 7:48 AM, tesonep(a)gmail.com wrote: > > Hi, > > this is an announcement of a new release of the Pharo VM. This > > new version is available to be downloaded through get-pharo scripts > > and through the Pharo Launcher. From the Pharo Launcher, remember to > > update the VM from the VM manager window. > > > > This version includes a series of improvements: > > > > - Unification of code base with the headless VM > > - Preparation for supporting HDPI displays. > > - Improvements in the speed of Threaded FFI (40x times faster in > > SameThread runner and 2x in Threaded worker). > > - Better handling of semaphores > > - Improvements in the loading of large images (better buffering) > > - Better support for headless execution on non-main thread > > > > Please let me know if you find any issues. > > > > Cheers, Pablo > > > -- Pablo Tesone. tesonep(a)gmail.com

Nov. 27, 2020

This week (48/2020) on the Issue Tracker

by Marcus Denker

That was a busy week.. we merged 50 Pull requests the last 7 days. And no, not only trivialities! Graphics ======== Add the missing implementation of OSSDL2GLRenderer >> #pixelExtent #7786 https://github.com/pharo-project/pharo/pull/7786 Clean the OSWindowGenericRenderer texture APIs for properly implementing a text renderer #7836 https://github.com/pharo-project/pharo/pull/7836 Fluid Class Definition ======================= Cleanupsâ¦ Fixes: #7816 this is what is breaking #7774 #7817 https://github.com/pharo-project/pharo/pull/7817 - 7820 class description contains dead code related to slots printing #7828 https://github.com/pharo-project/pharo/pull/7828 - Trait was missing the #named:package: instance creation method #7837 https://github.com/pharo-project/pharo/pull/7837 - Origin/7770 cleaning old definition printer #7845 https://github.com/pharo-project/pharo/pull/7845 FFI === - Cleanup UnifiedFFI packages #7793 https://github.com/pharo-project/pharo/pull/7793 - Extracting FFI backend #7834 https://github.com/pharo-project/pharo/pull/7834 Variables/Compiler ================== - MetaLinks-Cleanup-Variables2 #7742 Instead of names, use Variables! More to come. https://github.com/pharo-project/pharo/pull/7742 - SemanticAnalysis-Args-are-read #7844 Arguments are now correctly tagged as #read im semantic analysis https://github.com/pharo-project/pharo/pull/7844 - Compilerbased-meta-data-tagging #7779 We now tag methods with #halt calls during compilation instead of scanning bytecode slowly later. https://github.com/pharo-project/pharo/pull/7779 Speed Improvements =================== speedup #hasProperty: a little by using includesProperty: instead of #propertyAt:ifAbsent: - CompiledMethod-hasProperty-use-includesProperty #7854 https://github.com/pharo-project/pharo/pull/7854 This lead to a Proposal: Simplify How Pragmas are stored (feedback wanted!) - https://github.com/pharo-project/pharo/issues/7871 Bug Fixes ============ - Fix side-effect in MCOrganizationDefinition #7815 https://github.com/pharo-project/pharo/pull/7815 - #ensureCreateDirectory` Shouldn't Resolve #7833 https://github.com/pharo-project/pharo/pull/7833 - fixing-title-in-osx #7843 Blog post: https://thepharo.dev/2020/11/25/a-vm-bug-no-an-image-one/ https://github.com/pharo-project/pharo/pull/7843 - Fixing dependencies error. #7856 https://github.com/pharo-project/pharo/pull/7856 - 7862-Cleaning-finder-code-glicthes #7864 https://github.com/pharo-project/pharo/pull/7864 Small Improvements ================== - 7755 re excessive arguments rule should exclude ffi callouts #7757 https://github.com/pharo-project/pharo/pull/7757 - 7777-Could-we-have-isTestMethod-on-Symbol-too #7785 https://github.com/pharo-project/pharo/pull/7785 - 7347 improve exception description api #7661 https://github.com/pharo-project/pharo/pull/7661 - Accessor generator should create formatted version #7853 https://github.com/pharo-project/pharo/pull/7853 - Add additional linux platform checking #7803 https://github.com/pharo-project/pharo/pull/7803 Unused Varianbles Cleanup ========================= I wrote about this: https://blog.marcusdenker.de/finding-unused-variables-an-example-for-first-… The tests are for now on âself skipâ until we clean the unused vars. - Cleanup-Unused-Ivars #7780 https://github.com/pharo-project/pharo/pull/7780 - add testNoUnusedClassVariablesLeft (skipped for now) #7784 https://github.com/pharo-project/pharo/pull/7784 Lot of activity to clean it up: - Remove unused var in SycMethodNameEditorTest #7799 https://github.com/pharo-project/pharo/pull/7799 - Var cleanup in DependencyAnalyser #7791 https://github.com/pharo-project/pharo/pull/7791 - Care on unused ivars in Renraku #7811 https://github.com/pharo-project/pharo/pull/7811 - Unused ivar MorphicTabManagerAdapter #7809 https://github.com/pharo-project/pharo/pull/7809 - Care on unsued ivars in Calypso #7814 https://github.com/pharo-project/pharo/pull/7814 - Unused ivar in Reflectivity-Tools-Tests #7824 https://github.com/pharo-project/pharo/pull/7824 - Unused ivar in Clap #7822 https://github.com/pharo-project/pharo/pull/7822 - Remove unused trait users #7797 https://github.com/pharo-project/pharo/pull/7797 - Unused ivars in UDPSocketTest #7849 https://github.com/pharo-project/pharo/pull/7849 Cleanups ======== Cleanups are those changes that do not have any immediate impact for the users. But they prepare the future: they make code simpler, remove dead code, add documentation, fix typos... - Move ReAsClassRule to GeneralRules #7759 https://github.com/pharo-project/pharo/pull/7759 - Rule based cleanup for RBCompositeRefactoryChange #7776 https://github.com/pharo-project/pharo/pull/7776 - Simplify ReExcessiveArgumentsRule>>#basicCheck: #7789 https://github.com/pharo-project/pharo/pull/7789 - remove-halt-visitEnglobingErrorNode #7801 https://github.com/pharo-project/pharo/pull/7801 - Fulfil ClassTestCase>>#classToBeTested subclass reponsibility #7805 https://github.com/pharo-project/pharo/pull/7805 - Cleanup and extend Dr. Test #7807 https://github.com/pharo-project/pharo/pull/7807 - Cleanup DrTest - pass #2 #7819 https://github.com/pharo-project/pharo/pull/7819 - Remove FFITutorial #7795 https://github.com/pharo-project/pharo/pull/7795 - Merge-MethodNameEditor-RBMethodNameEditor #7775 https://github.com/pharo-project/pharo/pull/7775 - PharoDocComment : remove a direct reference to RBParser #7781 https://github.com/pharo-project/pharo/pull/7781 - PharoDoc-pass2 #7829 https://github.com/pharo-project/pharo/pull/7829 - [Code cleaning] Replaced 'Character tab asString' to 'String tab' #7835 https://github.com/pharo-project/pharo/pull/7835 - Clean up Base64MimeConverterTest #7851 https://github.com/pharo-project/pharo/pull/7851 - reduce-ASTCache-reset #7783 https://github.com/pharo-project/pharo/pull/7783 - 7857-Cleaning-ends-of-class-names-in-Calypso #7858 https://github.com/pharo-project/pharo/pull/7858 - 7859-CalypsoContextPartTwo #7861 https://github.com/pharo-project/pharo/pull/7861 - Small typo in ExtendedDatePrinter>>#printDate:format:on: #7870 https://github.com/pharo-project/pharo/pull/7870 - Ban rule "class not referenced" for WebBrowser subclasses #7847 https://github.com/pharo-project/pharo/pull/7847

Nov. 27, 2020

Re: [ANN] New Pharo VM released (v8.6.1)

by Martin McClure

Is this new VM available for Linux? I only see Windows and Mac VMs that are dated 2020-11-02. In the launcher (launcher 2.2, still the latest AFAICT) refreshing the 90-x64 VM just re-downloads the one from 2020-02-11. Thanks, -Martin On 11/2/20 7:48 AM, tesonep(a)gmail.com wrote: > Hi, > this is an announcement of a new release of the Pharo VM. This > new version is available to be downloaded through get-pharo scripts > and through the Pharo Launcher. From the Pharo Launcher, remember to > update the VM from the VM manager window. > > This version includes a series of improvements: > > - Unification of code base with the headless VM > - Preparation for supporting HDPI displays. > - Improvements in the speed of Threaded FFI (40x times faster in > SameThread runner and 2x in Threaded worker). > - Better handling of semaphores > - Improvements in the loading of large images (better buffering) > - Better support for headless execution on non-main thread > > Please let me know if you find any issues. > > Cheers, Pablo >

Nov. 27, 2020

Re: [ANN] New UI renderer with Hi-DPI support (Beta testing)

by Ronie Salgado

Hello, Today I am giving a talk about this at 4 pm, Paris time through the Discord. Best regards, Ronie El miÃ©, 25 nov 2020 a las 16:11, Ronie Salgado (<roniesalg(a)gmail.com>) escribiÃ³: > Hello, > > The last months I have been working in a new UI rendering framework for > Pharo based on adding an intermediate scene graph with the purpose of > improving rendering speed, and with the side effect of making the whole UI > scalable and adding support for Hi-DPI rendering. > > We would appreciate that people could start testing this so that we can > find bugs and stabilize it. For using this the latest Pharo 9 image and > headless vm is required. > > Form Scene Graph repo, installation and settings repository: > https://github.com/ronsaldo/form-scene-graph > > Known issues: > - Iceberg is hanging on fetches and pushes only when using the Athens > backend. No segmentation fault or debugger is being launched here so this > is difficult to fix. When having to deal with this issue we recommend using > the OSWindowGenericRenderer backend (SDL2). > > Best regards, > Ronie > >

Nov. 26, 2020