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

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

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

by Ronie Salgado

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. 25, 2020

[ANN] Next Pharo Sprint: Nov 27

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Nov 27 (this Friday) Goals of this sprint: - Fix issues from tracker https://github.com/pharo-project/pharo/issues This is a Remote Sprint, it happens on Discord. http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

Nov. 23, 2020

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

by Marcus Denker

> On 21 Nov 2020, at 10:14, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Indeed, posting these emails is useful. It helps keeping us posted about the ongoing progress of Pharo. > > I like they are grouped by topic, so it makes easier to get what it's about. Sean's suggestion would indeed understand more. Though I expect it will require more time/effort to write. Moreover, these emails are already long. I'm affraid they'll become way too long. > > A solution that mixes both might be posting more often updates. But, again I expect it to be time consuming. > Yes, writing for real takes effortâ¦ E.g. last week I did a trivial PR after I got annoyed about seeing too many ivars tat are not used and did a first step (mostly a skipped test): Cleanup-Unused-Ivars #7780 https://github.com/pharo-project/pharo/pull/7780 But then I realised that the core of the test: variables := Smalltalk globals allBehaviors flatCollect: [ :each | each instanceVariables ]. variables := variables reject: [ :each | each isReferenced ]. variables := variables collect: [ :each | each definingClass ] as: Set. actually is more interesting then being just a trivial test for a trivial cleanupâ¦ In the end it is trivial, but it is as an example for why things like turning variables into objects is interesting: ======= As you might be aware, we added to Pharo the concept of âFirsts class Variablesâ that is, there is a meta object for every variable in the system. Historically, even though you might think that âeverything is an Objectâ in Smalltalk, the memory constraints that existed when ST80 was created did not make reifying everything possible. Even today, this has to be done with care: for example, instances of TempVariable are only created on demand in Pharo. As for ST80: Instance Variables are one example of things that are not Objects: The only thing that we have are the names (that is, strings) of the instance variables defined by a class. The order is fixed so that the offset of the variables in the list of all instance variable of the class hierarchy actually is the offset that the bytecode uses to access this variable. Thus all code dealing with Variables tend to be formulated quite âlow levelâ. It exposes a lot of implementation details: you need to find names, then the offset, then use a low level bytecode scanning method to check if a method accesses this offset. So how do âFirst Classâ Variables improve the situation? Letâs see what we have to do to find all classes that define an instance variable that is not accessed. Read more: https://blog.marcusdenker.de/finding-unused-variables-an-example-for-first-…

Nov. 23, 2020