- Pharo-dev - lists.pharo.org

[ANN] Pharo 12 Release !

by Esteban Lorenzano

Dear Pharo users and dynamic language lovers: We have released Pharo <https://pharo.org/> version 12! What is Pharo? Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. * Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. * Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! * Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! * Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. * Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> ... more on the Pharo Features page <http://www.pharo.org/features>. In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo120Chang…> Some highlights of this amazing version: Highlights New breakpoint system The debug point system is a breakpoint model that supersedes the previous implementation of breakpoints and watchpoints. They are configurable, composable, and extensible. The traditional breakpoints remain available, including conditional breakpoints, one-time breakpoints, and object-centric breakpoints. Additionally, there are new types of breakpoints, such as chained-breakpoints, which condition the activation of certain breakpoints on the triggering of others (e.g., breakpoint B only activates if breakpoint A is hit first). Debug points also feature a dedicated browser and integration options. Tools * Scalable fluid class syntax is now the default one * Preparing the introduction of the Bloc graphic system by migrating more tools to Spec2 widgets * Spec2 UI framework enhancements to support GTK 4 * Leaner version of the Metacello package manager * More robust and strict mode for FFI System * New architecture for refactorings and domain specific transformations * Code loading speed improvement * Fast browsing via fully optimized package tags * Optmized memory usage via optimized method protocols * Compiler simplifications and improvements Virtual machine * Massive image support with permanent space * String/ByteArray comparison speed up Development Effort This new version is the result of 1895 Pull Requests integrated just in the Pharo repository. We have closed 865 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: * http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> * http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> * http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> * http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> * http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> * http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> * http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> * http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> Contributors We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 12.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. The Pharo Team Discover Pharo: https://pharo.org/features Try Pharo: http://pharo.org/download <https://pharo.org/download> Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation>

April 26, 2024

Re: [ANN] Soil release v1

by Norbert Hartl

April 24, 2024

Re: [ANN] Soil release v1

by Miloslav.Raus＠cuzk.cz

Wonderful to hear. Unless mistaken, SOIL should support multiple open databases , so unless you expect intra-database consistency,since "you'll get an object back", it should "just work" for objects possibly instantiated from different DB's ? From: Norbert Hartl <norbert(a)hartl.name> Sent: Wednesday, April 24, 2024 1:53 PM To: Pharo users users <pharo-users(a)lists.pharo.org>; Pharo Dev <pharo-dev(a)lists.pharo.org>; ESUG <esug-list(a)lists.esug.org> Subject: [Pharo-dev] [ANN] Soil release v1 ...we said at last ESUG that there will be a release soonish but as usual it doesn't go that fast. But now we are very happy to announce that Soil has a first public release v1. So what is soil? Soil is an object oriented database in pharo<http://pharo.org/>. It is transaction based having ACID transactions. It has binary search capabilities with SkipList and BTree+ indexes. It aims to be a simple yet powerful database making it easy to develop with, easy to debug with, easy to inspect, ... More details at https://github.com/ApptiveGrid/Soil This release is still considered early stage because * although in ApptiveGrid there are over 4000 instances of it and there are other users there isn't a wider range of use cases, yet. So it is not fully battle tested. This just as reminder when you start compaining I need somewhere to point my finger to and say "I told you!" ;) * there are few things missing that you might expect like garbage collection, etc. So but it is definetely usable and awaiting the brave ones of you to try. Hopy you enjoy it! Norbert & Marcus

April 24, 2024

Re: [Esug-list] [ANN] Soil release v1

by Tim Mackinnon

That's really exciting news... appreciate you sharing it with the wider community (I know when you mentioned its existence a while back I went and watched the Esug recordings to get more info, and looked at some of the extensive test cases to get a feel on what it looked like - its neat). Having multiple options for persisting data (from simple Fuel up to Soil and Glorp and Gemstone) is very useful. Tim On Wed, 24 Apr 2024, at 12:52 PM, Norbert Hartl wrote: > ...we said at last ESUG that there will be a release soonish but as usual it doesn't go that fast. > > But now we are very happy to announce that Soil has a first public release v1. So what is soil? > > Soil is an object oriented database in pharo <http://pharo.org/>. It is transaction based having ACID transactions. It has binary search capabilities with SkipList and BTree+ indexes. It aims to be a simple yet powerful database making it easy to develop with, easy to debug with, easy to inspect, ... > > More details at https://github.com/ApptiveGrid/Soil > > This release is still considered early stage because > > â¢ although in ApptiveGrid there are over 4000 instances of it and there are other users there isn't a wider range of use cases, yet. So it is not fully battle tested. This just as reminder when you start compaining I need somewhere to point my finger to and say "I told you!" ;) > â¢ there are few things missing that you might expect like garbage collection, etc. > > So but it is definetely usable and awaiting the brave ones of you to try. > > Hopy you enjoy it! > > Norbert & Marcus > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org >

April 24, 2024

[ANN] Soil release v1

by Norbert Hartl

...we said at last ESUG that there will be a release soonish but as usual it doesn't go that fast. But now we are very happy to announce that Soil has a first public release v1. So what is soil? Soil is an object oriented database in pharo <http://pharo.org/>. It is transaction based having ACID transactions. It has binary search capabilities with SkipList and BTree+ indexes. It aims to be a simple yet powerful database making it easy to develop with, easy to debug with, easy to inspect, ... More details at https://github.com/ApptiveGrid/Soil This release is still considered early stage because although in ApptiveGrid there are over 4000 instances of it and there are other users there isn't a wider range of use cases, yet. So it is not fully battle tested. This just as reminder when you start compaining I need somewhere to point my finger to and say "I told you!" ;) there are few things missing that you might expect like garbage collection, etc. So but it is definetely usable and awaiting the brave ones of you to try. Hopy you enjoy it! Norbert & Marcus

April 24, 2024

Re: [P12 nearing realease] dark theme problems (wrt. code snippets)

by Miloslav.Raus＠cuzk.cz

Hi, Sadly no, as I refuse to use tracking apps as means to âtwo-factor authenticateâ to github (besides other reasons not to use github for my work). If there is a possibility, Iâd love to. M.R. From: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Friday, April 19, 2024 9:16 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Cc: RauÅ¡ Miloslav <Miloslav.Raus(a)cuzk.cz>; Esteban Lorenzano <esteban.lorenzano(a)inria.fr> Subject: [Pharo-dev] Re: [P12 nearing realease] dark theme problems (wrt. code snippets) Thanks for the feedback. Could you open an issue on the pharo bug tracker? S On 18 Apr 2024, at 13:42, Miloslav.Raus--- via Pharo-dev <pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org>> wrote: Hi, Currently, if you use dark theme, for example the Welcome or Documentation apps show dark code on dark background. I know itâs pretty late, but perhaps an easy fix would be possible (?themed regions for code? or something) ? Cheers, M.R. 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

April 23, 2024

Re: P12 vs P11 difference: Class side trait composition

by Noury Bouraqadi

Thank you ! On Apr 23 2024, at 11:01 am, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hello, > > This is fixed with merging > > https://github.com/pharo-project/pharo/pull/16487 > > > > On 17 Apr 2024, at 18:36, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Hi, > > Why is the handling of empty trait compositions is different for class side? > > Suppose we have trait T used by class A. > > Consider B a subclass of A. > > > > B traitComposition ---> TaEmptyTraitComposition "Same for P11 and P12" > > B class trait "Difference !!!" > > ---> TaEmptyTraitComposition "in P11" > > ---> TaSequence {TaEmptyTraitComposition. TraitedClass} "in P12" > > > > Noury > > > > Noury

April 23, 2024

Re: P12 vs P11 difference: Class side trait composition

by Marcus Denker

Hello, This is fixed with merging https://github.com/pharo-project/pharo/pull/16487 > On 17 Apr 2024, at 18:36, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Hi, > > Why is the handling of empty trait compositions is different for class side? > > Suppose we have trait T used by class A. > Consider B a subclass of A. > > B traitComposition ---> TaEmptyTraitComposition "Same for P11 and P12" > > B class trait "Difference !!!" > ---> TaEmptyTraitComposition "in P11" > ---> TaSequence {TaEmptyTraitComposition. TraitedClass} "in P12" > > Noury > > > Noury > >

April 23, 2024

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

by Marcus Denker

# Bugs - Fix bug while adding a trait to a class without trait #16473 https://github.com/pharo-project/pharo/pull/16473 - Restore fileIn button in File Browser #16470 https://github.com/pharo-project/pharo/pull/16470 - Do not select the # in symbol selection #16469 https://github.com/pharo-project/pharo/pull/16469 - 16447-Dropping-window-outside-of-Pharo-window-borders-closes-the-window #16467 https://github.com/pharo-project/pharo/pull/16467 - 16355-Wrong-class-definition-creates-strange-DNUs #16466 https://github.com/pharo-project/pharo/pull/16466 - Fix: PullUpClassVar was not checking breaking change preconditions #16464 https://github.com/pharo-project/pharo/pull/16464 - fix access to false positive in Renraku #16457 https://github.com/pharo-project/pharo/pull/16457 - Fix #visitBehaviorRepackagedChange: on EpHasImpactVisitor to send #not instead of #y #16449 https://github.com/pharo-project/pharo/pull/16449 - 16365 Add subclass can create trait subclasses #16442 https://github.com/pharo-project/pharo/pull/16442 - Clean package generation of "Jump to test class" #16434 https://github.com/pharo-project/pharo/pull/16434 - Add LibTTY providing access to the VM library for spawning a process connected to a pseudo-terminal #16427 https://github.com/pharo-project/pharo/pull/16427 - fix: Socket>>#waitForSendDoneFor: does not return a boolean (but ZdcSocketStream expects it to) #16425 https://github.com/pharo-project/pharo/pull/16425 - Update the Playground shortcut #16422 https://github.com/pharo-project/pharo/pull/16422 - Fix code highlighting in debug points browser, for debug points set on AST node #726 https://github.com/pharo-spec/NewTools/pull/726 - fix layouts #1539 https://github.com/pharo-spec/Spec/pull/1539 - Adding textChanged notification to SpStringTableColumn #1360 https://github.com/pharo-spec/Spec/pull/1360 # Cleanup - Removing old object-centric breakpoint's integration to the inspector #733 https://github.com/pharo-spec/NewTools/pull/733 - Changed protocol for displayStringOn: to displaying #737 https://github.com/pharo-spec/NewTools/pull/737 - Change superclass of StDebuggerTest from TestCase to SpBaseTest #740 https://github.com/pharo-spec/NewTools/pull/740 - Removing old breakpoint system's integration to Calypso #16397 https://github.com/pharo-project/pharo/pull/16397 - reuse of #isFalsePositive:forRuleId:versionId: in #falsePositiveOf: #16475 https://github.com/pharo-project/pharo/pull/16475

April 23, 2024

Re: [P12 nearing realease] dark theme problems (wrt. code snippets)

by stephane ducasse

Thanks for the feedback. Could you open an issue on the pharo bug tracker? S > On 18 Apr 2024, at 13:42, Miloslav.Raus--- via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hi, > > Currently, if you use dark theme, for example the Welcome or Documentation apps show dark code on dark background. > > I know itâs pretty late, but perhaps an easy fix would be possible (?themed regions for code? or something) ? > > Cheers, > > M.R. 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

April 19, 2024