- Pharo-dev - lists.pharo.org

EU Citizen Initiative for consumers to have access to apps they purchased

by David Mason

There is currently a citizen initiative to get a law in place that makers of software must not make the software become unusable after they end support. While this is directly about games, it has implications for things like cars, tractors, medical devices, and anything that has a significant software component. I encourage my EU friends and colleagues to consider signing and explaining to their friends why it's important for them to sign even if they don't play games. Here's a video that explains it: https://www.youtube.com/watch?v=mkMe9MxxZiI Here's tha petition: https://www.stopkillinggames.com/ Sorry this is a bit off-topic, but I think it's important to the entire software industry. ../Dave

Aug. 3, 2024

This week (30/2024) on the Pharo Issue Tracker

by Marcus Denker

The most important not obvious news of the week: We managed to get the CI in a good shape again! Test are now green for all three platforms. This is one of these aspects of development that are easily overlooked: Just keeping the CI green and running is far more work in a real project than you would naively think. Summer break: the weekly mails (but not the improvements to Pharo!) will take a break. In the week of 26/08 we post the weeksly logs for weeka 31-34. # Pharo 12 Backports - Automatically type 'NULL' arguments in FFI (backport to P12) #16926 https://github.com/pharo-project/pharo/pull/16926 - [Backport] Update FormSet to not recompute each scalling all the time #16887 https://github.com/pharo-project/pharo/pull/16887 # Fixes - Fix bug in protocol management of Traits #16936 https://github.com/pharo-project/pharo/pull/16936 - Instance of NullWorldRenderer did not understand #fullscreenMode: when run headless / in CI #16925 https://github.com/pharo-project/pharo/pull/16925 - Catch CmCommandAborted in Calypso #16920 https://github.com/pharo-project/pharo/pull/16920 - Fixes icon for packages drop list in StRequestClassPresenter #16856 https://github.com/pharo-project/pharo/pull/16856 - Handles permission problems on FileBrowser #813 https://github.com/pharo-spec/NewTools/pull/813 - Use equality to compare file references in file navigation system #811 https://github.com/pharo-spec/NewTools/pull/811 # Improvements - Enable specification of a comparison strategy to compare list items #1573 https://github.com/pharo-spec/Spec/pull/1573 - Improve IconStyler highlight to be base on theme #16943 https://github.com/pharo-project/pharo/pull/16943 - Add isPackage #16935 https://github.com/pharo-project/pharo/pull/16935 # Rules - improve ReCollectionProtocolRule #16918 https://github.com/pharo-project/pharo/pull/16918 - Deprecated package #16931 https://github.com/pharo-project/pharo/pull/16931 - change rules description UI #16929 https://github.com/pharo-project/pharo/pull/16929 # Cleanup - ListView-Tests should depends on Tests #1576 https://github.com/pharo-spec/Spec/pull/1576 - ListView adapters should be close to morphic adapters #1575 https://github.com/pharo-spec/Spec/pull/1575 - Fix dependency test #806 https://github.com/pharo-spec/NewTools/pull/806 - Remove MCMergeBrowser #16950 https://github.com/pharo-project/pharo/pull/16950 - Monticello: remove dead code and some Morphic UI #16949 https://github.com/pharo-project/pharo/pull/16949 - Move UndefinedClassVariable out of the Kernel #16947 https://github.com/pharo-project/pharo/pull/16947 - Remove useless method: CompiledMethod >> argumentNames #16937 https://github.com/pharo-project/pharo/pull/16937

July 26, 2024

This week (29/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 12 - Use identity comparisons when looking for elements in a list #1568 https://github.com/pharo-spec/Spec/pull/1568 - [P12][Backport] adding test to ensure it is possible to recompile code within a bloc with a dead home context twice #785 https://github.com/pharo-spec/NewTools/pull/785 # VM - Improving log of old space limit error reporting #833 https://github.com/pharo-project/pharo-vm/pull/833 # Fixes - 16897-Deprecation--messageText-results-in-MNU #16908 https://github.com/pharo-project/pharo/pull/16908 - Forward port https://github.com/pharo-spec/Spec/pull/1568 #1569 https://github.com/pharo-spec/Spec/pull/1569 - add error handler for latin1 encoding failure #796 https://github.com/pharo-spec/NewTools/pull/796 # Speed - Update FormSet to not recompute each scalling all the time #16886 https://github.com/pharo-project/pharo/pull/16886 # Rules - improve ReCollectionAtCollectionSizeRule #16916 https://github.com/pharo-project/pharo/pull/16916 - Delete ReDeprecateWithFirstCharacterDownshiftedRule and his test #16901 https://github.com/pharo-project/pharo/pull/16901 - tests for rules from style category #16896 https://github.com/pharo-project/pharo/pull/16896 - Small PR to add support to set class rules in the Smallint checker #16864 https://github.com/pharo-project/pharo/pull/16864 - Cyclomatic complexity rule #16851 https://github.com/pharo-project/pharo/pull/16851 - Fixes critics browser problems #797 https://github.com/pharo-spec/NewTools/pull/797 - Add critics on class option #794 https://github.com/pharo-spec/NewTools/pull/794 # Towards a green CI - StClassCritiqueBrowserPresenter: Remove method with Undeclared #799 https://github.com/pharo-spec/NewTools/pull/799 - Fix failing tests making CI to fail #16868 https://github.com/pharo-project/pharo/pull/16868 - fix testThatThereAreNoSelectorsRemainingThatAreSentButNotImplemented #16906 https://github.com/pharo-project/pharo/pull/16906 - Move UnifiedDiffJoinSection to Pharo #16915 https://github.com/pharo-project/pharo/pull/16915 - Move unified diff Morph to Tool-Diff #16909

July 22, 2024

Re: [ANN] Pharo Launcher 3.2 released!

by Tim Mackinnon

Just to add to what others have said - the presentation at Esug on 3.2 was very cool. You raised some very interesting use-cases that the command line gives (like using $vars to help manage consistent project naming). So thanks for pushing on this. Tim On Wed, 10 Jul 2024, at 6:45 PM, Christophe Demarey wrote: > Hi all, > > Pharo Launcher 3.2 has just been released! It is available from http://pharo.org/download. > > > Pharo Launcher now comes with a command-line version that you can use from a terminal! > You can check the documentation of commands at https://pharo-project.github.io/pharo-launcher/commands-cmd-line/ as well as instructions to make pharo-launcher available on command line: https://pharo-project.github.io/pharo-launcher/installation/. > This nice feature is now available thanks to the contributions of Axel Marlard, David Bajger and I as well as the support of Damien Pollet for the Clap library. > > New features: > > â¢ Command Line support > > â¢ all commands available in the UI version of Pharo Launcher are supported > â¢ new commands > â¢ create an image from a Pull Request number (from Pharo repository) > â¢ create an image from a build number, a SHA > â¢ create an image and import your code from a repository > â¢ share easily an image (zip file with the Pharo image, the VM to run it and a launch script) > â¢ find easily the Pharo version where a bug was introduced with image *bisect* algorithm > â¢ launch an image with a script > â¢ list running Pharo processes > â¢ When creating an image, the image is now launched automatically > > â¢ CI moved to Github Actions > > Improvements: > > â¢ Better Mac Os system menu > â¢ Do not try to guess anymore the version of a Pharo image if information not available but rather ask the user > â¢ When deleting more than 1 image at a time the message is not clear #594 <https://github.com/pharo-project/pharo-launcher/issues/594> > Bug fixes: > > â¢ Pharo 12.0 build list incomplete #667 <https://github.com/pharo-project/pharo-launcher/issues/667> > â¢ Use "Show" when no image is downloaded yet gives error #570 <https://github.com/pharo-project/pharo-launcher/issues/570> (thanks to @astares <https://github.com/astares>) > â¢ Development mode does not close pharoLauncher application #548 <https://github.com/pharo-project/pharo-launcher/issues/548> > â¢ Using "Show in folder" gives DNU #568 <https://github.com/pharo-project/pharo-launcher/issues/568> (thanks to @astares <https://github.com/astares>) > â¢ Launcher cannot launch Pharo-4.0 image #585 <https://github.com/pharo-project/pharo-launcher/issues/585> > > > Regards, > The Pharo team.

July 14, 2024

Re: This week (28/2024) on the Pharo Issue Tracker

by Noury Bouraqadi

Thank you Marcus for all the time and the good energy you put into both Pharo and ESUG! Noury On Jul 12 2024, at 12:20 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > This week we reached 10.000 closed pull requests on the main repository (see https://github.com/pharo-project/pharo/pulls) > The week did not see many changes merged due to many contributors attending (and giving talks at) this years ESUG conference. > > # Pharo 12 Backports > - [P12] Fix MetacelloRepositoryGroup with duplicated repository #16859 > https://github.com/pharo-project/pharo/pull/16859 > > # Fixes > - Fix: deprecate method refactoring to applicability preconditions as list #16867 > https://github.com/pharo-project/pharo/pull/16867 > > - Fix multiple tests with refactoring driver for duplicate class. #16853 > https://github.com/pharo-project/pharo/pull/16853 > > - [P13] Fix MetacelloRepositoryGroup with duplicated repository #1686 > https://github.com/pharo-project/pharo/pull/16860 > > - ffi: add a cache for array types of same type and size #16877 > https://github.com/pharo-project/pharo/pull/16877 > > # Cleanup > - Update transmissionBlock: -> transmits: #793 > https://github.com/pharo-spec/NewTools/pull/793 >

July 12, 2024

Looking for new adventures

by Koen De Hondt

Dear Pharo Community, As you may have read on my blog <https://all-objects-all-the-time.st/#/blog/posts/1> or heard during my ESUGâ23 presentation, eighteen months ago I entered the Pharo scene after being away from the Smalltalk community for 20 years. For the last one and a half years, I have been a member of a team using Pharo and GemStone. I attended almost all Pharo Sprints in Lille (every last Friday of the month). In this channel, I have informed you about my intention to build a new browser based on Spec. That development has been on the back burner for the last five months because I have been working hard with StÃ©phane Ducasse to finish the book âApplication Building with Spec 2.0â. I have presented at ESUGâ23, and I am sad that I could not attend ESUGâ24 this week. >From the above, my contribution to the Pharo community is clear, and I think my drive to contribute more is also clear. In a few months, I will leave the team I am working with now. Therefore, I am looking for new adventures. If you are looking for a seasoned software developer who likes working in Smalltalk/Pharo very much, please send me a message, and I will be in touch rapidly. Please find more details on my career history on LinkedIn <https://www.linkedin.com/in/koendehondt/>. Best regards, Koen

July 12, 2024

This week (28/2024) on the Pharo Issue Tracker

by Marcus Denker

This week we reached 10.000 closed pull requests on the main repository (see https://github.com/pharo-project/pharo/pulls) The week did not see many changes merged due to many contributors attending (and giving talks at) this years ESUG conference. # Pharo 12 Backports - [P12] Fix MetacelloRepositoryGroup with duplicated repository #16859 https://github.com/pharo-project/pharo/pull/16859 # Fixes - Fix: deprecate method refactoring to applicability preconditions as list #16867 https://github.com/pharo-project/pharo/pull/16867 - Fix multiple tests with refactoring driver for duplicate class. #16853 https://github.com/pharo-project/pharo/pull/16853 - [P13] Fix MetacelloRepositoryGroup with duplicated repository #1686 https://github.com/pharo-project/pharo/pull/16860 - ffi: add a cache for array types of same type and size #16877 https://github.com/pharo-project/pharo/pull/16877 # Cleanup - Update transmissionBlock: -> transmits: #793 https://github.com/pharo-spec/NewTools/pull/793

July 12, 2024

[ANN] Pharo Launcher 3.2 released!

by Christophe Demarey

Hi all, Pharo Launcher 3.2 has just been released! It is available from http://pharo.org/download. Pharo Launcher now comes with a command-line version that you can use from a terminal! You can check the documentation of commands at https://pharo-project.github.io/pharo-launcher/commands-cmd-line/ as well as instructions to make pharo-launcher available on command line: https://pharo-project.github.io/pharo-launcher/installation/. This nice feature is now available thanks to the contributions of Axel Marlard, David Bajger and I as well as the support of Damien Pollet for the Clap library. New features: Command Line support all commands available in the UI version of Pharo Launcher are supported new commands create an image from a Pull Request number (from Pharo repository) create an image from a build number, a SHA create an image and import your code from a repository share easily an image (zip file with the Pharo image, the VM to run it and a launch script) find easily the Pharo version where a bug was introduced with image bisect algorithm launch an image with a script list running Pharo processes When creating an image, the image is now launched automatically CI moved to Github Actions Improvements: Better Mac Os system menu Do not try to guess anymore the version of a Pharo image if information not available but rather ask the user When deleting more than 1 image at a time the message is not clear #594 <https://github.com/pharo-project/pharo-launcher/issues/594> Bug fixes: Pharo 12.0 build list incomplete #667 <https://github.com/pharo-project/pharo-launcher/issues/667> Use "Show" when no image is downloaded yet gives error #570 <https://github.com/pharo-project/pharo-launcher/issues/570> (thanks to @astares <https://github.com/astares>) Development mode does not close pharoLauncher application #548 <https://github.com/pharo-project/pharo-launcher/issues/548> Using "Show in folder" gives DNU #568 <https://github.com/pharo-project/pharo-launcher/issues/568> (thanks to @astares <https://github.com/astares>) Launcher cannot launch Pharo-4.0 image #585 <https://github.com/pharo-project/pharo-launcher/issues/585> Regards, The Pharo team.

July 10, 2024

This week (27/2024) on the Pharo Issue Tracker

by Marcus Denker

Main work this week happend on the CI infrastruture (and getting the test green for Pharo13 again), we did not merge lots of PRs due to that. # Pharo 12 - [P12][Backport] Fix recompilation of dead block twice in debugger #16784 https://github.com/pharo-project/pharo/pull/16784 # Fixes - Improve contrasts of DarkBlueTheme #16822 https://github.com/pharo-project/pharo/pull/16822 # Cleanup - Fixing issue#14145: ycAbstractAllInstVarAccessorsCommand >> variable never set #16820 https://github.com/pharo-project/pharo/pull/16820 - fix #15843: Reduce references to Transcript #16830 https://github.com/pharo-project/pharo/pull/16830 - fixed issue #15252: Cleanup: Small Lint issue in ZnImageExampleDelegate>>#handlePostRequest: #16815 https://github.com/pharo-project/pharo/pull/16815 # Documentation - Updated class comments of UUID and UUIDGenerator #16817 https://github.com/pharo-project/pharo/pull/16817

July 5, 2024

Re: [ANN] Soil release v1

by stephane ducasse

Hi norbert I love the idea behind soil :) That you keep pushing it is just great. I will start to play with it during holidays. S > On 30 Jun 2024, at 20:37, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 30.06.2024 um 05:41 schrieb sean(a)clipperadams.com: >> >> ï»¿ >> Thanks for this. Sounds really cool. >> >> One thing I keep wondering about is the comment at ESUG that the serializer had to be rewritten from the ground up (no pun intended ha ha) because Fuel is neither flexible nor fast. Fuel has become such an integral part of the ecosystem that it seems a shame it couldnât help here. Was there any thought about modifying Fuel to make it more flexible and/or fast? >> > The first version was using fuel because that was my initial plan not to waste time on developing something that is already there. > Iâm not sure I can recall precisely but it was really hard to get it doing what I want > > hooks / extension points > > We want to tell an object when it just has been materialized so it can take something like post-initialization and such. It was not easy to add that to fuel > > class management/lookup > > Soil has class versions (how could it work without?) So whenever you materialize something you need to be able to manage the description of a class and inject properly so that you can materialize and migrate old versions. > Migrations are the overall weak point of fuel and soil needs it badly > > general design > > Fuel does analysis steps and then writes a graph as a whole trying to optimize storage space and read performance. At least thatâs what I think were the rationales for doing that pickle format and class storage. But it does all of this in one stroke making fuel a good tool when you are only interested in the resulting blob. > In soil we want to have something like a streaming writer with a simple approach. Therefor the serializer is similar to the Omnibase one which simple, good and fast. I did not thoroughly test performance but the benchmarks Iâve did showed that fuel is not even faster. This might be wrong > > development > > The later changes on fuel are IMHO make fuel even less flexible and tend to be over-engineered (Max, that is my personal opinion and should not taken as a general statement) > > me > > It was an insane idea to start doing a database and expect to succeed with it in a short time frame. But I was forced to do it because I was migrating ApptiveGrid to OmniBase just to learn at a very late time that it is not open source because someone stupid just put intentionally an MIT license onto it after copying the source code to github. > So I was not tempted to have a lot of patience with something like fuel when it starts to block my way > > I hope this is a proper answer to that very good question > > Norbert > >> Thanks again, >> >> Sean >> StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

June 30, 2024