- Pharo-users - lists.pharo.org

Re: remove breakpoint ?

by stephane ducasse

Hi arnoldo Sorry for the inconvenience often I edit and recompile the method to remove a breakpoint. In P12 we redid all this part. this is the first time I see this. Which version of pharo are you using? - Did you see the vides in the first week of the mooc? because they explain the IDE. http://mooc.pharo.org - You can have support if you ask in the discord channel https://discord.gg/QewZMZa - for Bloc there is separate mailing-list lse-openbloc <lse-openbloc(a)inria.fr> you can register at http://sympa.inria.fr > On 5 Apr 2024, at 11:16, Haroldo Stenger <haroldo.stenger(a)gmail.com> wrote: > > hi nice pharo people > > I'm doing my very initial attempts in Pharo. Having read something > here and there. > Now I've put myself to subclass BlElement in order to add a method of > myself to this subclass. > The subclass got named 'Circulo'. Then I had a hard time trying to > create a protocol to 'host' it, but finally it got created as protocol > 'a'. Initially it got created in the third pane in the browser, below > without any apparent 'breakpoint hierarchy'. However, as soon as I > wrote the method and got to save/accept it, something strange > happened, namely, 'brakepoint' protocol was created out of nothing , > and my 'a' protocol was put under it. The method itself in the fourth > pane, has a red ! sign. If I right click on the method, and try to > remove the breakpoint, it does nothing. What happens this and how can > I have a normal situation , since I did not put breakpoints ? Thanks > for your kind help ï¿¼ 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 7, 2024

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

by Marcus Denker

# Fixes - Provide a default String for settings without #default: sends. #16400 https://github.com/pharo-project/pharo/pull/16400 - 16356-Rename-class-refactoring-popup-does-not-have-default-button #16392 https://github.com/pharo-project/pharo/pull/16392 - Small fixes pre release #16381 https://github.com/pharo-project/pharo/pull/16381 - Revert comment change from commit f5df5966bd73d05bc04806d2f8735baa4b1783cb #16376 https://github.com/pharo-project/pharo/pull/16376 - Fix function signature in #getVolumeInfo:into:size: for StWin32Info #730 https://github.com/pharo-spec/NewTools/pull/730 - Adapt #getVolumeInfo:into:size: for StWin32Info to strict FFI #729 https://github.com/pharo-spec/NewTools/pull/729 - Change #getTempPath:buffer: on WinPlatform to use âGetTempPathWâ instead of âGetTempPath2Wâ #16342 https://github.com/pharo-project/pharo/pull/16342 - latest changes #1532 https://github.com/pharo-spec/Spec/pull/1532 # UI/Tools Fixes - improve/spRequiestDialog-issue-16356 #1531 https://github.com/pharo-spec/Spec/pull/1531 - Remove Monticello shortcut references #16388 https://github.com/pharo-project/pharo/pull/16388 - remaining morphic dialogs: aligning the default option to right #16352 https://github.com/pharo-project/pharo/pull/16352 - 16363-Improve-Expand-menu-for-class-definition #16371 https://github.com/pharo-project/pharo/pull/16371 - New tools parent menu entry #16379 https://github.com/pharo-project/pharo/pull/16379 - Open Calpyso with 915px wide such that the entire toolbar is visible #16380 https://github.com/pharo-project/pharo/pull/16380 - Make #cascadeFor:initialExtent:world: for RealEstateAgent use integral positions when using the worldâs center #16390 https://github.com/pharo-project/pharo/pull/16390 - Fix issue while trying to display file setting items #736 https://github.com/pharo-spec/NewTools/pull/736 - Remove async playground doits #735 https://github.com/pharo-spec/NewTools/pull/735 - Fix Preview Settings Browser: does not open when a custom setting is used #734 https://github.com/pharo-spec/NewTools/pull/734 - Fix "Open terminal here" in new File browser #732 https://github.com/pharo-spec/NewTools/pull/732 - Add 3 new entries to easily access the new tools from the System menu. #731 https://github.com/pharo-spec/NewTools/pull/731 # Cleanups - Deprecate #newMethod:header: with rewritting to #basicNew:header: #16375 https://github.com/pharo-project/pharo/pull/16375 - Remove StWindowsExtensionsTest #728 https://github.com/pharo-spec/NewTools/pull/728 - Remove old backward compatibility code from FFILibrary #16349 https://github.com/pharo-project/pharo/pull/16349

April 5, 2024

remove breakpoint ?

by Haroldo Stenger

hi nice pharo people I'm doing my very initial attempts in Pharo. Having read something here and there. Now I've put myself to subclass BlElement in order to add a method of myself to this subclass. The subclass got named 'Circulo'. Then I had a hard time trying to create a protocol to 'host' it, but finally it got created as protocol 'a'. Initially it got created in the third pane in the browser, below without any apparent 'breakpoint hierarchy'. However, as soon as I wrote the method and got to save/accept it, something strange happened, namely, 'brakepoint' protocol was created out of nothing , and my 'a' protocol was put under it. The method itself in the fourth pane, has a red ! sign. If I right click on the method, and try to remove the breakpoint, it does nothing. What happens this and how can I have a normal situation , since I did not put breakpoints ? Thanks for your kind help

April 5, 2024

Call for Presentations @ ESUG 2024

by stephane ducasse

Dear Friends The deadline for the presentation proposal was 1st of April. We extended it until 8th of April. You are probably busy but we the organisers deserve consideration too. ESUG 2024 Call for Presentations from 8 to 11 July 2024 Lille France https://esug.github.io <https://esug.github.io/> https://esug.github.io/2024-Conference/conf2024.html You can support the ESUG conference in many different ways: - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ - Submit a talk, software to the award competition, or a paper to IWST http://https://esug.github.io/2024-Conference/IWST2024.html - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! - Students can get free registration and hosting if they enroll in the the Student Volunteers program. See below. ## Developers Forum: International Smalltalk Developers Conference We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. The list of topics for the normal talks and tutorials includes, but is not limited to the following: - XP practices, Development tools, Experience reports - Model-driven development, Web development, Team management - Meta-Modeling, Security, New libraries & frameworks - Educational material, Embedded systems and robotics - SOA and Web services, Interaction with other programming languages - Teaching Pearls and Show us Your Business We added two types of sessions in addition to the regular talks and ''Show us your project'' sessions. - Show your business in a 10-minute session (Get prepared!!) - Teaching pearls: we want some sessions on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15-minute sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2024-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>] Title: [ESUG 2024] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio:

April 4, 2024

Re: Books about Pharo

by stephane ducasse

Thanks for the pointer!!! For me Iâm lacking time to improve Microdown, so I will focus on the features I have on my todo - > support - $ $ and $$ - I got some ideas about a nice extension mechanism :) quite cool in fact Doing a parser is not that simple. In microdown dev I integrated the latest version of the paragraph parser made by Kasper and now I will check it for real. I briefly checked it and :) well microdown is much much simpler and also more powerful when it is related to environment arguments (quite cool to have reference to figs, math expressions, extensibility). Now I will review it carefully and pick what I find useful. I will start to improve the readme because microdown is quite sexy at the end and all the books Iâm producing are done with it. S > On 31 Mar 2024, at 20:22, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > On the next iteration for Microdown you may find Djot [1] interesting, as it is also trying to be familiar to Markdown users, while fixing the several of its shortcomings and making parsers easier to build, by having a clearer non-ambiguous syntax, that doesn't require look ahead mechanisms. I think that Djot may share the Microdow design principles stated at [2] regarding [2a] familiarity to Markdown [2b] Small uniform core and [2c] extensibility. Umm... I wonder, given that one of the selling points of Djot is the easiness of implementing parsers, how difficult could be to implement a Djot parser and connect it to the Pillar infrastructure? > > Following the idea quoted at the beginning blog post at [3] trying to " to create a light markup syntax that keeps what is good about Markdown, while revising some of the features that have led to bloat and complexity" and finding the sweet spot between popular options and added value, without being tied by popularity or the past, is a worth exploration. It help us, as a community, to reach the people where they are. Even more considering how Markdown is a popular but clumsy standard de facto (<flame> kind of the Git/GitHub of the light Markup languages, promoted greatly by its GitHub usage </flame>). > > In my case, given the constrains in computer labs where installing Pandoc can be cumbersome, using Markdeep has been an important time saver, even if we need to fork[4] its main repository to document publicly its possibilities and shortcomings. A natively fully supported and well defined light format in Pharo, like Microdown or Djot, could help us a lot in our documentation workflows, given our limited resources[^a]. And, because of the shared design sensibilities behind both formats, I would like to have Microdown more inspired in Djot than in "wild Markdown". The efforts in having a "popular alike" format totally supported in the image are greatly appreciated. > > Cheers, > > Offray > > == Links and footnotes > > [1] https://djot.net/ > [2] https://rmod-files.lille.inria.fr/Team/Texts/Papers/Duca20a-Microdown-IWST.… > [3] https://www.jonashietala.se/blog/2024/02/02/blogging_in_djot_instead_of_mar… > [4] https://github.com/ruidajo/markdeep/ > > [^a]: I'm half of the population of the two active Smalltalkers/Pharoers in my country, working in the language part time. We need to cleverly combine resources with a low complexity/expressivity ratio, that's where our combination of tools like Pharo/GT, Fossil, Markdeep, Pandoc comes from. > > On 27/03/24 2:48, stephane ducasse wrote: >> I released yesterday the version 9.0.1 of pillar for Pharo 11. >> And I will restart a new iteration on Microdown. >> - better support for math >> - introducing > >> and more as time allows. >> >> S >> >>> On 27 Mar 2024, at 01:25, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> <mailto:offray.luna@mutabit.com> wrote: >>> >>> Pretty cool! >>> >>> One of my ideas with Grafoscopio was to be able to read interactive documentation inside Pharo, which was obtained in a pretty primitive way. Now I have moved to Lepiter as a GUI of our documentation workflows and Markdeep as a default format for storage and web rendering. But seeing the advances in Microdown and its interactive viewer is pretty inspiring. I hope to check some Pharo books prepackaged with upcoming releases. >>> >>> Keep the good work, >>> >>> Offray >>> >>> On 14/03/24 9:40, stephane ducasse wrote: >>>> Hi Richard >>>> >>>> I did not see your original post because I messed up with my account. >>>> But thanks for your email :) >>>> >>>> Now the cool stuff if that we can also read the books from within Pharo. >>>> We should improve the Microdown renderer and suddenly we will get shiny cool >>>> documentation. >>>> >>>> S >>>> >>>> >>>> >>>>> This is a new thread because it's not limited to any specific topic. >>>>> >>>>> If you have questions about Pharo, especially "how do I do <this> in >>>>> Pharo", you can always ask in this mailing list. You can, if you like >>>>> playing Russian Roulette, ask a Large Language Model "AI". >>>>> >>>>> But there is an amazing resource you should really trye. >>>>> >>>>> books.pharo.org >>>>> >>>>> Did you ever wonder where the manual for Pharo was? >>>>> That's where. The site lists a bunch of Pharo books and booklets, >>>>> all of which have free PDFs except for two of the books. >>>>> In particular, you'll always want the most recent edition of >>>>> "Pharo by Example" handy. >>>>> >>>>> These books are really useful. They are written by people know know >>>>> their material thoroughly and do a good job of explaining it. If you >>>>> want to make any serious use of Pharo, or even to have more happiness >>>>> than headaches just playing with it, you owe it to yourself to get the >>>>> free PDFs What do we owe the authors? Well, if you're not trying to >>>>> make one pension support four people, you owe them the purchase of >>>>> some of the books. Me, I'm giving them thanks, praise, and a >>>>> heartfelt recommendation. >>>>> >>>>> Seriously, these books represent a HUGE amount of work and "you are a >>>>> fool to yourself and a burden to others" if you don't take advantage >>>>> of this great resource. >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr <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 >> >> >> >> >> 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 3, 2024

Re: Books about Pharo

by Offray Vladimir Luna CÃ¡rdenas

On the next iteration for Microdown you may find Djot [1] interesting, as it is also trying to be familiar to Markdown users, while fixing the several of its shortcomings and making parsers easier to build, by having a clearer non-ambiguous syntax, that doesn't require look ahead mechanisms. I think that Djot may share the Microdow design principles stated at [2] regarding [2a] familiarity to Markdown [2b] Small uniform core and [2c] extensibility. Umm... I wonder, given that one of the selling points of Djot is the easiness of implementing parsers, how difficult could be to implement a Djot parser and connect it to the Pillar infrastructure? Following the idea quoted at the beginning blog post at [3] trying to " to create a light markup syntax that keeps what is good about Markdown, while revising some of the features that have led to bloat and complexity" and finding the sweet spot between popular options and added value, without being tied by popularity or the past, is a worth exploration. It help us, as a community, to reach the people where they are. Even more considering how Markdown is a popular but clumsy standard de facto (<flame> kind of the Git/GitHub of the light Markup languages,Â promoted greatly by its GitHub usage </flame>). In my case, given the constrains in computer labs where installing Pandoc can be cumbersome, using Markdeep has been an important time saver, even if we need to fork[4] its main repository to document publicly its possibilities and shortcomings. A natively fully supported and well defined light format in Pharo, like Microdown or Djot, could help us a lot in our documentation workflows, given our limited resources[^a]. And, because of the shared design sensibilities behind both formats, I would like to have Microdown more inspired in Djot than in "wild Markdown". The efforts in having a "popular alike" format totally supported in the image are greatly appreciated. Cheers, Offray == Links and footnotes [1] https://djot.net/ [2] https://rmod-files.lille.inria.fr/Team/Texts/Papers/Duca20a-Microdown-IWST.… [3] https://www.jonashietala.se/blog/2024/02/02/blogging_in_djot_instead_of_mar… [4] https://github.com/ruidajo/markdeep/ [^a]: I'm half of the population of the two active Smalltalkers/Pharoers in my country, working in the language part time. We need to cleverly combine resources with a low complexity/expressivity ratio, that's where our combination of tools like Pharo/GT, Fossil, Markdeep, Pandoc comes from. On 27/03/24 2:48, stephane ducasse wrote: > I released yesterday the version 9.0.1 of pillar for Pharo 11. > And I will restart a new iteration on Microdown. > - better support for math > - introducing > > and more as time allows. > > S > >> On 27 Mar 2024, at 01:25, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com> wrote: >> >> Pretty cool! >> >> One of my ideas with Grafoscopio was to be able to read interactive >> documentation inside Pharo, which was obtained in a pretty primitive >> way. Now I have moved to Lepiter as a GUI of our documentation >> workflows and Markdeep as a default format for storage and web >> rendering. But seeing the advances in Microdown and its interactive >> viewer is pretty inspiring. I hope to check some Pharo books >> prepackaged with upcoming releases. >> >> Keep the good work, >> >> Offray >> >> On 14/03/24 9:40, stephane ducasse wrote: >>> Hi Richard >>> >>> I did not see your original post because I messed up with my account. >>> But thanks for your email :) >>> >>> Now the cool stuff if that we can also read the books from within Pharo. >>> We should improve the Microdown renderer and suddenly we will get >>> shiny cool >>> documentation. >>> >>> S >>> >>> >>> >>>> This is a new thread because it's not limited to any specific topic. >>>> >>>> If you have questions about Pharo, especially "how do I do <this> in >>>> Pharo", you can always ask in this mailing list. Â You can, if you like >>>> playing Russian Roulette, ask a Large Language Model "AI". >>>> >>>> But there is an amazing resource you should really trye. >>>> >>>> books.pharo.org >>>> >>>> Did you ever wonder where the manual for Pharo was? >>>> That's where. Â The site lists a bunch of Pharo books and booklets, >>>> all of which have free PDFs except for two of the books. >>>> In particular, you'll always want the most recent edition of >>>> "Pharo by Example" handy. >>>> >>>> These books are really useful. Â They are written by people know know >>>> their material thoroughly and do a good job of explaining it. Â If you >>>> want to make any serious use of Pharo, or even to have more happiness >>>> than headaches just playing with it, you owe it to yourself to get the >>>> free PDFs Â What do we owe the authors? Â Well, if you're not trying to >>>> make one pension support four people, you owe them the purchase of >>>> some of the books. Â Me, I'm giving them thanks, praise, and a >>>> heartfelt recommendation. >>>> >>>> Seriously, these books represent a HUGE amount of work and "you are a >>>> fool to yourself and a burden to others" if you don't take advantage >>>> of this great resource. > > 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 > > > > >

March 31, 2024

# This week (13/2024) on the Pharo Issue Tracker

by Marcus Denker

# Fixes - Adapt #getVolumeInfo:into:size: for StWin32Info to strict FFI #729 https://github.com/pharo-spec/NewTools/pull/729 - Take the selector into account in #AdditionalMethodState>>#analogousCodeTo: #16302 https://github.com/pharo-project/pharo/pull/16302 - Add override for #drawPolygon:fillStyle:borderWidth:borderColor: on ScalingCanvas to avoid conversion of the second argument to a Color #16304 https://github.com/pharo-project/pharo/pull/16305 - Make #contentsMenu: on WorldMorph use the FormSet for each of the icons #16317 https://github.com/pharo-project/pharo/pull/16317 - Change â./$0â to â$0â in recursive retry command in script âgetPharoVM.shâ #16337 https://github.com/pharo-project/pharo/pull/16337 - ZnHeaders does not understand isNotEmpty #16339 https://github.com/pharo-project/pharo/pull/16339 - Move archival of â*.xmlâ and â*.fuelâ files in âJenkinsfileâ to the âfinallyâ block #16341 https://github.com/pharo-project/pharo/pull/16341 - remaining morphic dialogs: aligning the default option to right #16352 https://github.com/pharo-project/pharo/pull/16352 # Tools - fixes #16315 dependency browser layout feels wrong #16343 https://github.com/pharo-project/pharo/pull/16343 - enable / disable syntax highlight in code presenter of critics browser. #727 https://github.com/pharo-spec/NewTools/pull/727 # Cleanup - Remove StWindowsExtensionsTest #728 https://github.com/pharo-spec/NewTools/pull/728 - Remove #createTab from ClyBrowserToolMorph #16318 https://github.com/pharo-project/pharo/pull/16318 - Remove old backward compatibility code from FFILibrary #16349 https://github.com/pharo-project/pharo/pull/16349

March 29, 2024

Re: Books about Pharo

by stephane ducasse

I released yesterday the version 9.0.1 of pillar for Pharo 11. And I will restart a new iteration on Microdown. - better support for math - introducing > and more as time allows. S > On 27 Mar 2024, at 01:25, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Pretty cool! > > One of my ideas with Grafoscopio was to be able to read interactive documentation inside Pharo, which was obtained in a pretty primitive way. Now I have moved to Lepiter as a GUI of our documentation workflows and Markdeep as a default format for storage and web rendering. But seeing the advances in Microdown and its interactive viewer is pretty inspiring. I hope to check some Pharo books prepackaged with upcoming releases. > > Keep the good work, > > Offray > > On 14/03/24 9:40, stephane ducasse wrote: >> Hi Richard >> >> I did not see your original post because I messed up with my account. >> But thanks for your email :) >> >> Now the cool stuff if that we can also read the books from within Pharo. >> We should improve the Microdown renderer and suddenly we will get shiny cool >> documentation. >> >> S >> >> >> >>> This is a new thread because it's not limited to any specific topic. >>> >>> If you have questions about Pharo, especially "how do I do <this> in >>> Pharo", you can always ask in this mailing list. You can, if you like >>> playing Russian Roulette, ask a Large Language Model "AI". >>> >>> But there is an amazing resource you should really trye. >>> >>> books.pharo.org >>> >>> Did you ever wonder where the manual for Pharo was? >>> That's where. The site lists a bunch of Pharo books and booklets, >>> all of which have free PDFs except for two of the books. >>> In particular, you'll always want the most recent edition of >>> "Pharo by Example" handy. >>> >>> These books are really useful. They are written by people know know >>> their material thoroughly and do a good job of explaining it. If you >>> want to make any serious use of Pharo, or even to have more happiness >>> than headaches just playing with it, you owe it to yourself to get the >>> free PDFs What do we owe the authors? Well, if you're not trying to >>> make one pension support four people, you owe them the purchase of >>> some of the books. Me, I'm giving them thanks, praise, and a >>> heartfelt recommendation. >>> >>> Seriously, these books represent a HUGE amount of work and "you are a >>> fool to yourself and a burden to others" if you don't take advantage >>> of this great resource. 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

March 27, 2024

Re: Books about Pharo

by Offray Vladimir Luna CÃ¡rdenas

Pretty cool! One of my ideas with Grafoscopio was to be able to read interactive documentation inside Pharo, which was obtained in a pretty primitive way. Now I have moved to Lepiter as a GUI of our documentation workflows and Markdeep as a default format for storage and web rendering. But seeing the advances in Microdown and its interactive viewer is pretty inspiring. I hope to check some Pharo books prepackaged with upcoming releases. Keep the good work, Offray On 14/03/24 9:40, stephane ducasse wrote: > Hi Richard > > I did not see your original post because I messed up with my account. > But thanks for your email :) > > Now the cool stuff if that we can also read the books from within Pharo. > We should improve the Microdown renderer and suddenly we will get shiny cool > documentation. > > S > > > >> This is a new thread because it's not limited to any specific topic. >> >> If you have questions about Pharo, especially "how do I do <this> in >> Pharo", you can always ask in this mailing list. You can, if you like >> playing Russian Roulette, ask a Large Language Model "AI". >> >> But there is an amazing resource you should really trye. >> >> books.pharo.org >> >> Did you ever wonder where the manual for Pharo was? >> That's where. The site lists a bunch of Pharo books and booklets, >> all of which have free PDFs except for two of the books. >> In particular, you'll always want the most recent edition of >> "Pharo by Example" handy. >> >> These books are really useful. They are written by people know know >> their material thoroughly and do a good job of explaining it. If you >> want to make any serious use of Pharo, or even to have more happiness >> than headaches just playing with it, you owe it to yourself to get the >> free PDFs What do we owe the authors? Well, if you're not trying to >> make one pension support four people, you owe them the purchase of >> some of the books. Me, I'm giving them thanks, praise, and a >> heartfelt recommendation. >> >> Seriously, these books represent a HUGE amount of work and "you are a >> fool to yourself and a burden to others" if you don't take advantage >> of this great resource.

March 27, 2024

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

by Marcus Denker

# Features - Adding tests for debug points + integrating debug points to Calypso Browser #16268 https://github.com/pharo-project/pharo/pull/16268 - add uFFI convenience methods #16320 https://github.com/pharo-project/pharo/pull/16320 # Fixes - 16321-Method-with-an-highlighted-warning-or-error-is-kept-when-deleting-the-offending-text #16322 https://github.com/pharo-project/pharo/pull/16322 - Protect with a mutex the transcript update #16311 https://github.com/pharo-project/pharo/pull/16311 - 15841-ZeroDivide-when-selecting-idea11-icons #16309 https://github.com/pharo-project/pharo/pull/16309 - 14700-Shortcut-text-is-not-displayed-correctly-on-a-Mac #16307 https://github.com/pharo-project/pharo/pull/16307 - Fix parsing twice per keystroke in Calypso #16306 https://github.com/pharo-project/pharo/pull/16306 - NativeBrowserOpenVisitor requires typing for strict FFI #16325 https://github.com/pharo-project/pharo/pull/16325 - 15564-No-menubar-in-Mac-OS-Sonoma #16297 https://github.com/pharo-project/pharo/pull/16297 - Refactor RubTextSegmentMorph to support use of a FormSet #16323 https://github.com/pharo-project/pharo/pull/16323 - Make #taskbarButtonMenu: on SystemWindow and MorphicNativeWindow use the FormSet for each of the icons #16296 https://github.com/pharo-project/pharo/pull/16296 - Make #initializeFor: on TaskbarItemMorph use the FormSet for the icon #16316 https://github.com/pharo-project/pharo/pull/16316 - 16332-Bug-in-Transcript #16334 https://github.com/pharo-project/pharo/pull/16334 - Change #transformBy:clippingTo:during:smoothing: on FormCanvas to use BitBlt combination rule 34 instead of 24 #16303 https://github.com/pharo-project/pharo/pull/16303 - remove wrong name #16331 https://github.com/pharo-project/pharo/pull/16331/files - Add pre-filling the name text presenter in file dialogs #717 https://github.com/pharo-spec/NewTools/pull/717 - Allowing to use Texts as HelpText of Presenters #1529 https://github.com/pharo-spec/Spec/pull/1529 # Tools - fix-critics-browser-issue #724 https://github.com/pharo-spec/NewTools/pull/724 - Fixing Version Browser Presenter #721 https://github.com/pharo-spec/NewTools/pull/721 - Showing CMD character in OSX in Spotter #720 https://github.com/pharo-spec/NewTools/pull/720 - Improvements to the Scopes Editor and integration with Pharo #718 https://github.com/pharo-spec/NewTools/pull/718 # Breakpoints - Debug Point Browser integration #697 https://github.com/pharo-spec/NewTools/pull/697 # Refactoring Engine - 16326-Realize-class-menu-option-throws-error-on-any-class #16333 https://github.com/pharo-project/pharo/pull/16333 - Makes user defined scopes available in Refactoring User Interfaces #15918 https://github.com/pharo-project/pharo/pull/15918 - Fix: remove extract method transformation from UI #16301 https://github.com/pharo-project/pharo/pull/16301

March 25, 2024