[Pharo-dev] This week (17/2024) on the Pharo Issue Tracker

We finally released Pharo 12! Find the announcement here: https://www.pharo.org/news/2024-04-26-pharo12-released.html Last week we merged quite some fixes that where tagged as release critical. And of course some small cleanups. We have opened the Pharo 13 branch, new changes will from now on

[Pharo-dev] Re: P12 vs P11 difference: Class side trait composition

Hello, This is fixed with merging https://github.com/pharo-project/pharo/pull/16487 > On 17 Apr 2024, at 18:36, Noury Bouraqadi 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

[Pharo-dev] This week (16/2024) on the Pharo Issue Tracker

# 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

[Pharo-dev] This week (15/2024) on the Pharo Issue Tracker

# Speed - 16407-RBNodes-errorNotices-creates-unneeded-empty-collections #16408 https://github.com/pharo-project/pharo/pull/16408 # Bug Fixes - Fix Preview Settings Browser: does not open when a custom setting is used #734 https://github.com/pharo-spec/NewTools/pull/734 -

[Pharo-dev] This week (14/2024) on the Pharo Issue Tracker

# 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

[Pharo-dev] # This week (13/2024) on the Pharo Issue Tracker

# 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

[Pharo-dev] This week (12/2024) on the Pharo Issue Tracker

# 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 -

[Pharo-dev] This week (11/2024) on the Pharo Issue Tracker

With the freeze, we will see now less PRs being integrated, most of them fixes and tests. If you see bugs in Pharo 12, make sure to check that it is reported on the issue tracker! # Fixes - fix calypso close button #16295 https://github.com/pharo-project/pharo/pull/16295 -

[Pharo-dev] This week (10/2024) on the Pharo Issue Tracker

# Pharo 10 - Fix for: UFFI/TFFI call for WebBrowser with specific URL length adds strange characters to the URL #15980 #16253 https://github.com/pharo-project/pharo/pull/16253 # Pharo 11 - Fix for: UFFI/TFFI call for WebBrowser with specific URL length adds strange characters to the

[Pharo-dev] This week (09/2024) on the Pharo Issue Tracker

# Features - integrating Debug Points model into Pharo #16177 https://github.com/pharo-project/pharo/pull/16177 # Fixes - add back isGlobalClassNameBinding #16035 https://github.com/pharo-project/pharo/pull/16035 - FFIUnsupportedUntypedLiteral when using WebBrowser

[Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

Nice link: https://www.linkedin.com/company/pharoproject/ > On 27 Feb 2024, at 13:12, Marcus Denker wrote: > > Ah found it: > > I added a page: > > https://www.linkedin.com/company/102626671 > >> On 27 Feb 2024, at 12:52, Marcus Denker wrote: >> >&g

[Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

Ah found it: I added a page: https://www.linkedin.com/company/102626671 > On 27 Feb 2024, at 12:52, Marcus Denker wrote: > > Yes, that is a group. > > But I want to check how to post “as Pharo” and not with my private account.. > >> On 27 Feb 2024, at 12:32

[Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

Yes, that is a group. But I want to check how to post “as Pharo” and not with my private account.. > On 27 Feb 2024, at 12:32, Noury Bouraqadi wrote: > > There is already a LinkedIn account for Pharo > https://www.linkedin.com/groups/2558378/ > > On Feb 27 2024, at 11:38

[Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

> social media under the Pharo account. > Just put the link of the story on LinkedIn and share the link here so we can > like and share. > > Cheers, > Noury > On Feb 26 2024, at 5:49 pm, Marcus Denker wrote: > New Story posted on the Website: > > ApptiveGrid - Dig

[Pharo-dev] [Success Story] ApptiveGrid - Digitize and Automatize Business Processes

New Story posted on the Website: ApptiveGrid - Digitize and Automatize Business Processes https://www.pharo.org/success/ApptiveGrid.html Marcus

[Pharo-dev] This week (08/2024) on the Pharo Issue Tracker

# Fixes / Improvements - Implement Process>>state as the single source of truth for #isX methods (implements #14904) #16072 https://github.com/pharo-project/pharo/pull/16072 - Fix SDL2 class>>primCreateRGBSurfaceForCairoWidth:height: #16223

[Pharo-dev] This week (07/2024) on the Pharo Issue Tracker

# This week (07/2024) on the Pharo Issue Tracker # Fixes - Replace $r key combination in method editor pane #16168 https://github.com/pharo-project/pharo/pull/16168 - Fix SDL2 binding #16165 https://github.com/pharo-project/pharo/pull/16165 -

[Pharo-dev] This week (06/2024) on the Pharo Issue Tracker

# Pharo11 - Tolerate halt when handling a OSWindowEvent #16095 https://github.com/pharo-project/pharo/pull/16095 # Networking - Improved error handling around sending data in Socket/SocketStream (fixes #15614) #15984 https://github.com/pharo-project/pharo/pull/15984

[Pharo-dev] This week (05/2024) on the Pharo Issue Tracker

# Fixes - Fixes for browsing a package from a repository using Calypso #16009 https://github.com/pharo-project/pharo/pull/16009 - add a missing method ClyOldMessageBrowserAdapter #16083 https://github.com/pharo-project/pharo/pull/16083 - Fix String method causing

[Pharo-dev] Re: About removing class side initialization

For both #isAbstract and #initialize, one can understand both as cases where we have to use behavior for something that should actually be a kind o declarative property of the objects. - isAbstract This is a property of the class. - initialize This is a property of the Variable. It’s

[Pharo-dev] This week (04/2024) on the Pharo Issue Tracker

This week (04/2024) on the Pharo Issue Tracker # Pharo 11 - [Backport] Improve the way to know if a class includes a trait #15987 https://github.com/pharo-project/pharo/pull/15987 # Fixes - Fix: #16011 adding the lost return #16012

[Pharo-dev] This week (02/2024) on the Pharo Issue Tracker

# Fixes - 15941-WeakLayout--isWords-is-unknown-and-break-tests #15942 https://github.com/pharo-project/pharo/pull/15942 - Fix class and trait definition printing to consider package tags #15935 https://github.com/pharo-project/pharo/pull/15935 - Extend

[Pharo-dev] This week (01/2024) on the Pharo Issue Tracker

# Feature - Add Search filter to Epicea #15842 https://github.com/pharo-project/pharo/pull/15842 # Fixes - fix #15893 bad system commitish #15894 https://github.com/pharo-project/pharo/pull/15894 # Refactoring Engine - Fix order of rename. #15921

[Pharo-dev] This week (52/2023) on the Pharo Issue Tracker

# Fixes - Fix Enlumineur Pretty Printer "One line messages" setting not showing options #15819 https://github.com/pharo-project/pharo/pull/15819 - Restore #removeMethod:inClass: method #15889 https://github.com/pharo-project/pharo/pull/15889 - Explicitly set

[Pharo-dev] This week (51/2023) on the Pharo Issue Tracker

A little bit late... # Features - Implements hierarchical senders system command #15822 https://github.com/pharo-project/pharo/pull/15822 - Shuffle tests #15581 https://github.com/pharo-project/pharo/pull/15581 # Fixes - 15801-Cmd-B-on-Transcript-raises-an-error

[Pharo-dev] [ANN] New Success Story posted

There is a new “Success Story” posted on pharo.org : Casino - Revolutionizing Application Migration for Berger-Levrault https://www.pharo.org/success/BergerLevrault-Casino.html If you have an idea for something like that, you can do PRs for the site here:

[Pharo-dev] This week (03/2024) on the Pharo Issue Tracker

After a holiday break, we resume the weekly issue tracker report # Pharo 11 - Extend FFIExternalStructureReferenceHandle with tfPointerAddress #15951 https://github.com/pharo-project/pharo/pull/15951 # Bugs - Fix bug in integer vs float comparisons #15973

[Pharo-dev] [ANN] Pharo Consortium New Bronze Member: ApptiveGrid

The Pharo Consortium is very happy to announce that ApptiveGrid GmbH has joined the Consortium as a Bronze Member. About - ApptiveGrid: https://www.apptivegrid.de - Pharo Consortium: http://consortium.pharo.org ApptiveGrid is a SaaS tool to digitalize and automatize business

[Pharo-dev] About Undeclared

Hi, You might have seen that we have done some work related to Undeclared. I did some slides to explain how it worked / how it works now / what remaining problems are / next step. Undeclared.pdf Description: Adobe PDF document

[Pharo-dev] This week (50/2023) on the Pharo Issue Tracker

# Pharo 11 - 15769-Backport-15767--Pharo11-Fix-hasSameDefinitionAs-for-IndexedSlot #15785 https://github.com/pharo-project/pharo/pull/15785 - 15096-Backport-Pharo11-AdditionalMethodState-do-not-copy-the-AssociationsPragmas-when-growing-or-shrinking-15090 #15786

[Pharo-dev] This week (49/2023) on the Pharo Issue Tracker

# Features - Add class comment as tooltip in Calypso. #15660 https://github.com/pharo-project/pharo/pull/15660 - Add file out for Epicea entries #15644 https://github.com/pharo-project/pharo/pull/15644 - Debugger: Integrating assertion rewriting (2nd attempt)

[Pharo-dev] This week (48/2023) on the Pharo Issue Tracker

# Pharo 11 - Update spec to 1.2.5 #15575 https://github.com/pharo-project/pharo/pull/15575 # Features - 10612-Add-visitPragmasNodes-as-we-have-visitTemporaryNodes #15610 https://github.com/pharo-project/pharo/pull/15610 - Optimized ephemeron support for Fuel #15563

[Pharo-dev] This week (47/2023) on the Pharo Issue Tracker

Lots of PRs merged last week…. # Pharo 11 - fixes: SpStringTableColumn displayAlignment is not applied (for Pharo11) #1476 https://github.com/pharo-spec/Spec/pull/1476 # Website / github Readme - Update README.md with Discord and GH Activity #15516

[Pharo-dev] This week (46/2023) on the Pharo Issue Tracker

# Pharo 11 Backports - backport: Guard RubAbstractTextArea>>#recomputeSelection for empty paragraphs #15140 #15375 https://github.com/pharo-project/pharo/pull/15375 - backport "Defer change list update to avoid a race condition" #14853 #15374

[Pharo-dev] This week (45/2023) on the Pharo Issue Tracker

# Feature - Proposal: new message browser layout #15229 https://github.com/pharo-project/pharo/pull/15229 # Fixes - Calypso: Fix refresh of project view #15281 https://github.com/pharo-project/pharo/pull/15281 - Stay in calypso project view when selecting a class

[Pharo-dev] Last week (44/2023) on the Pharo Issue Tracker

# Pharo 11 - Backport Pharo11: Optimize Dictionary>>unreferencedKeys #15196 https://github.com/pharo-project/pharo/pull/15196 # External Packages - Update roassal v1.05b #15159 https://github.com/pharo-project/pharo/pull/15159 # Features - Calypso: Introduce a project view

[Pharo-dev] This week (43/2023) on the Pharo Issue Tracker

# Pharo 11 - [P11] Add Support for proxy in Iceberg #15099 https://github.com/pharo-project/pharo/pull/15099 - Make finalization registry a normal strong double linked list #15107 https://github.com/pharo-project/pharo/pull/15107 - [P11] Update document browser to

[Pharo-dev] This week (42/2023) on the Pharo Issue Tracker

# This week (42/2023) on the Pharo Issue Tracker # Feature - Adding debug test setup debug menu entry #14992 https://github.com/pharo-project/pharo/pull/14992 - Enhance System menu to browse image and VM folder #15043 https://github.com/pharo-project/pharo/pull/15043 -

[Pharo-dev] Re: Server down for https://consortium.pharo.org/

Hi, It is running again. > On 15 Oct 2023, at 11:01, Noury Bouraqadi wrote: > > > > Noury Bouraqadi

[Pharo-dev] This week (41/2023) on the Pharo Issue Tracker

# Pharo 11 - Fix unsubscriptions of WeakSubscriptions #14951 https://github.com/pharo-project/pharo/pull/14951 - [P11 Backport] Unsubscribe announcements from finalization registry #14938 https://github.com/pharo-project/pharo/pull/14938 # Fixes - Fix versioning error

[Pharo-dev] # This week (40/2023) on the Pharo Issue Tracker

# Fixes - Fix intersection of dictionaries #14812 https://github.com/pharo-project/pharo/pull/14812 - Fix announcements during class creation #14816 https://github.com/pharo-project/pharo/pull/14816 - Prevent SystemDictionary key to be something else than

[Pharo-dev] Re: [Issue tracker] Please check your issues on the issue tracker

Oct 5, 2023 at 10:49 AM Noury Bouraqadi <mailto:bouraq...@gmail.com>> wrote: >> Did a pass. Thank you for the reminder Marcus. >> >> Noury >> On Oct 5 2023, at 2:16 pm, Marcus Denker > <mailto:marcus.den...@inria.fr>> wrote: >> Hi, >> >>

[Pharo-dev] [Issue tracker] Please check your issues on the issue tracker

Hi, Please check the issue tracker. Often when a bug is fixed, you might even think “YES! the bug I reported is now fixed” and you naturally assume that your issue therefore was closed. But that is not always the case. - people forgot to link PRs to the issues - gitub in the

[Pharo-dev] This week (39/2023) on the Pharo Issue Tracker

We merged 55 PRs this week # Pharo 11 - Backport: Clean installation of MCClassTraitDefinition #14768 https://github.com/pharo-project/pharo/pull/14768 # Upstream Sync - Zinc synch #14814 https://github.com/pharo-project/pharo/pull/14814 - Zodiac synch #14815

[Pharo-dev] This week (38/2023) on the Pharo Issue Tracker

# Pharo 11 - Make finalization registry entry removal O(1) -- backport P11 #14655 https://github.com/pharo-project/pharo/pull/14655 # Fixes - Treat a second click within the double-click window but in a different location as a separate click (fixes #14474) #14476

[Pharo-dev] This week (37/2023) on the Pharo Issue Tracker

# Features - add support for libgit2 1.7 in Linux #14662 https://github.com/pharo-project/pharo/pull/14662 - Add SixtyFourBitRegister class #14616 https://github.com/pharo-project/pharo/pull/14616 - Add ‘scale’ for display of a Paragraph using a

[Pharo-dev] Re: Next Pharo sprints

Hi, The next dates are: 29/09 27/10 24/11 22/12 “Christmas Sprint” Marcus > On 14 Sep 2023, at 12:26, Noury Bouraqadi wrote: > > Hi, > > I'd like to attend. When is the next one ? > > Noury > > On Wed, Sep 13, 2023, 09:42 Guillermo Polito > wrote: > Hi all, > > For those

[Pharo-dev] This week (36/2023) on the Pharo Issue Tracker

# Features - Allow formatting the contents of a Playground #14602 https://github.com/pharo-project/pharo/pull/14602 - Search strings without symbols using RB pattern matcher #14604 https://github.com/pharo-project/pharo/pull/14604 - Make unwind more flexible #14610

[Pharo-dev] This week (35/2023) on the Pharo Issue Tracker

# Fonts - Extend FreeTypeCache to support different scales #14544 https://github.com/pharo-project/pharo/pull/14544 - Add ‘scale’ parameter for displaying strings using a StrikeFont, FixedFaceFont or LogicalFont #14563 https://github.com/pharo-project/pharo/pull/14563 -

[Pharo-dev] This week (34/2023) on the Pharo Issue Tracker

# This week (34/2023) on the Pharo Issue Tracker Due to Holiday season not much happend, but both the Refactorig and RPackage improvements continued to see some actions. # Refactoring Engine - Fix: enable push down method for concrete classes #14500

[Pharo-dev] This week (33/2023) on the Pharo Issue Tracker

# Pharo 11 - [P11] Adding a nice error for loadSymbol #14452 https://github.com/pharo-project/pharo/pull/14452 # Features - Add #enumerationsDo: and #enumerationsOfSize: #13952 https://github.com/pharo-project/pharo/pull/13952 # Fixes - Fix BrowseIt for

[Pharo-dev] This week (32/2023) on the Pharo Issue Tracker

# Pharo 11 - [P11] Traits has to install method when is generated code #14155 https://github.com/pharo-project/pharo/pull/14155 - [P11] Update Spec #14446 https://github.com/pharo-project/pharo/pull/14446 -

[Pharo-dev] This week (29-31/2023) on the Pharo Issue Tracker

# This week (29-31/2023) on the Pharo Issue Tracker This is one log for three weeks (29-31) # Pharo 11 - backport Pharo11: Fix doubleClick on tab and on text selection. #14287 https://github.com/pharo-project/pharo/pull/14287 - Backport fixed tests #14409

[Pharo-dev] This week (28/2023) on the Pharo Issue Tracker

# This week (28/2023) on the Pharo Issue Tracker Due to holiday season, the next weekly report will be done beginning of August. But activity does not stop! If you do not want to miss anything, consider watching the pharo github repo at https://github.com/pharo-project/pharo # Pharo11

[Pharo-dev] This week (27/2023) on the Pharo Issue Tracker

# Features - #14173 Introduce a nice command to spot the closest method overriden … #14183 https://github.com/pharo-project/pharo/pull/14183 - Update Fuel from upstream #14132 https://github.com/pharo-project/pharo/pull/14132 # Fixes - 14034 debugger does not evaluate in the

[Pharo-dev] Re: [Help needed] 160 method with "sent but not implemented" selectors

ikely) So yes, it is a good way to find methods to remove, but it can not be done automatically Marcus > On Fri, Jun 30, 2023 at 11:15 AM Marcus Denker <mailto:marcus.den...@inria.fr>> wrote: >> This is a not-that important cleanup: It would be nice if we would tag or

[Pharo-dev] [Help needed] 160 method with "sent but not implemented" selectors

This is a not-that important cleanup: It would be nice if we would tag or fix all methods with "sent but not implemented” selectors if you inspect: SystemNavigation new allSentNotImplementedSelectors you get 160 methods in Pharo12. - some are dead code -> we should remove

[Pharo-dev] This week (26/2023) on the Pharo Issue Tracker

This week (26/2023) on the Pharo Issue Tracker # Fixes - 4074-Transcript-should-be-able-to-clear-the-contents-of-the-transcript #14100 https://github.com/pharo-project/pharo/pull/14100 - Remove ReUtilityMethodsRule #13947

[Pharo-dev] This week (25/2023) on the Pharo Issue Tracker

# Misc / Fixes - 14089-problem-showing-dock-icon-for-some-compiler-warnings-eg-name-aready-defined #14090 https://github.com/pharo-project/pharo/pull/14090 - Updated version of graph algos to use the latest one #14103 https://github.com/pharo-project/pharo/pull/14103 -

[Pharo-dev] Fwd: [Pharo-users] Kind reminder: Survey on the usage of the system browser

> Begin forwarded message: > > From: Koen De Hondt > Subject: [Pharo-users] Kind reminder: Survey on the usage of the system > browser > Date: 20 June 2023 at 12:08:00 CEST > To: pharo-us...@lists.pharo.org > Reply-To: Any question about pharo is welcome > > Hi Pharo users, > > A few weeks

[Pharo-dev] This week (24/2023) on the Pharo Issue Tracker

This week (24/2023) on the Pharo Issue Tracker # Fixes - compilationContext is lazily initialise so the acessor should be used #13964 https://github.com/pharo-project/pharo/pull/13964 - [DrTest] removing a trace from within the presenter. #13997

[Pharo-dev] This week (23/2023) on the Pharo Issue Tracker

ClassOrganization is finally inlined into ClassDescription. Image size is now (with welcome window) below 53MB. We continued to improve the read of pseudo variables in the debugger, read about it here: - Improving reading self in the Debugger for Clean Blocks

[Pharo-dev] Reflectively reading "super"

After we improved how thisContext and self is read reflectively, we should look at “super”. Super is always interesting, as , at first, you think that it is some magic object “self but with the class of the superclass”, or something? Like a “perspective" on that object? But it is much more

[Pharo-dev] This week (22/2023) on the Pharo Issue Tracker.

ClassOrganization refactoring continues, ClassDescription soon can now be inlined (see https://github.com/pharo-project/pharo/pull/13861) One interesting improvement this week is that we fixed reading the pseudovarible "thisContext" in the debugger. Read about it here:

[Pharo-dev] Re: Reading "self" in the Debugger

.com/pharo-spec/NewTools/pull/542> > On 30 May 2023, at 17:29, Marcus Denker wrote: > > I did a PR: > > > https://github.com/pharo-project/pharo/pull/13855 > > > differences: > > - guard for nil in #readInContext > - two tests: > > SelfVariableTest &

[Pharo-dev] Re: Reading "self" in the Debugger

equals: nil ] > On 29 May 2023, at 10:48, Marcus Denker wrote: > > In the last post, we looked at reading the PseudoVariable thisContext in the > Debugger. A summary of that might be: inspecting a variable compiled a DoIt, > that DoIt it executed parametrised with the context

[Pharo-dev] This week (21/2023) on the Pharo Issue Tracker

# This week (21/2023) on the Pharo Issue Tracker. This we we merged all changes done during the last weeks in Pharo11 to Pharo12. ClassOrganization refactoring continues, we will soon be able to inline the class into ClassDescription. # Pharo 11 - Backport fix to calypso method search #13794

[Pharo-dev] About thisContext in the Debugger

# Improving thisContext in the Debugger using First Class Variables Have you ever tried to inspect a thisContext variable in the debugger? Just interrupt Pharo by "CMD-.", the debugger appears with the main UI loop waiting on a Semaphore ""[delaySemaphore wait] in Delay>>wait". So if I now

[Pharo-dev] Re: The curious case of constant blocks

will put this in the Queue for the Pharo Dev blog next. Marcus > On 20 May 2023, at 11:02, Marcus Denker wrote: > > You might have come across code like this: > > ``` > minHeight > "answer the receiver's minHeight" > ^ self >

[Pharo-dev] The curious case of constant blocks

You might have come across code like this: ``` minHeight "answer the receiver's minHeight" ^ self valueOfProperty: #minHeight ifAbsent: [2] ``` In the case the #minHeight property is not set, it returns 2. Code like this is quite common, another

[Pharo-dev] This week (20/2023) on the Pharo Issue Tracker.

This week, we continued the work on Pharo12. #Fixes - Drop use of Paragraph from #drawOn: in ToggleWithSymbolMenuItemShortcut to fix menu item alignment #13764 https://github.com/pharo-project/pharo/pull/13764 - 13657-With-CleanBlocks-enabled-tests-fail-when-trying-to-Fuel-out-stack

[Pharo-dev] Fun with CleanBlocks or: Speeding up Dictionary>>#at:

Dictionary lookup is used a lot. Let's look at Dictionary>>#at: at: key "Answer the value associated with the key." ^ self at: key ifAbsent: [self errorKeyNotFound: key] The method looks simple and at a first glance, there are no obvious problems. But if we look at it again,

[Pharo-dev] This week (19/2023) on the Pharo Issue Tracker

We released Pharo11 this week! see https://www.pharo.org/news/pharo11-released.html # Pharo 11 - Fix welcomebrowser version #13691 https://github.com/pharo-project/pharo/pull/13691 - Backport fixe #13663: Enabling the setting ‘Show lines numbers for all browsers #13665

[Pharo-dev] This week (18/2023) on the Pharo Issue Tracker

With some last fixes, Pharo11 now is ready for release, Pharo12 improvements continue, with a focus on Protocols/ClassOrganizer, Compiler, Code Completion and CompiledMethodTrailer/sourcePointer simplifications. For the later, these posts to the pharo-dev list have more details: [Pharo12]

[Pharo-dev] [Pharo12] commentSourcePointer and Metaclass

Hi, up to Pharo11, the commentSourcePointer that is used to read and write the class comments was in ClassOrganization. In Pharo 12, we moved the commentSourcePointer to Class, Metaclass therefore has no empty commentSourcePointer anymore via it’s organizer. PR is merged… these are of course

[Pharo-dev] Re: [Pharo12] Simplify CompiledMethod trailer: just support fixed sourcePointers

terals. [#+ senders] bench Pharo11 : "'3.891 per second'" Pharo12 : "'4.913 per second'" This is some 25% faster, due to not having to instantiate a CompiledMethodTrailer for #endPC. Marcus > On 28 Apr 2023, at 11:07, Marcus Denker wrote: > > Hi, > > We

[Pharo-dev] [Pharo12] Simpler sourcePointer encoding

Hi, After simplifying the CompiledMethodTrailer, let's look at what is stored there. It is an integer that encodes 1) which file? .sources or .changes ? and 2) the position in the file. So for two files we need one bit. So we could just shift the position by one and then use the last bit, if

[Pharo-dev] This week (17/2023) on the Pharo Issue Tracker

# Pharo 11 - Refactor block ensure during termination to allow override #13534 https://github.com/pharo-project/pharo/pull/13534 # Pharo 12 ## Small Improvements - Small cleanup #bitShift:, #<< and #<< #13523 https://github.com/pharo-project/pharo/pull/13523 - Clean info of

[Pharo-dev] [Pharo12] Simplify CompiledMethod trailer: just support fixed sourcePointers

Hi, We did (im Pharo12) a simplification of how method trailers are handled. Below is the class comment of the now Deprecated and empty class CompiledMethodTrailer. The issue https://github.com/pharo-project/pharo/issues/13512 has a list of all the intermediate steps done. ==

[Pharo-dev] This week (16/2023) on the Pharo Issue Tracker

We merged ~60 PRs this week. # Pharo 11 - Backport #13426: Make protocol of super method a priority in MethodClassifier #13432 https://github.com/pharo-project/pharo/pull/13432 - Use fixed spec version for Pharo 11 #13445 https://github.com/pharo-project/pharo/pull/13445

[Pharo-dev] This week (15/2023) on the Pharo Issue Tracker.

We merged ~ 80 PRs, closing 33 issues. # Pharo 11 Release is getting closer... - Use Microdown 2.4.0 and BeautifulComments 1.0.0 (preparing for release) #13388 https://github.com/pharo-project/pharo/pull/13388 - use fixed NewTools version #13412

[Pharo-dev] This week (13/2023) on the Pharo Issue Tracker

#This week (13/2023) on the Pharo Issue Tracker. We merged around 100 Pull Reuests this week (Pharo11 and Pharo12) To see the state of not yet merged PRs easier, we added a GitHub Board https://github.com/orgs/pharo-project/projects/34 To see what is happing in Pharo11 and

[Pharo-dev] Pharo 11 release soon: Please check Issue Tracker

Hi, Pharo11 us now frozen for a while, it seems we are on a good way to release soon. This is always a good time to clean up the issue tracker. Please check especially the issues you opend https://github.com/pharo-project/pharo/issues Github often fails to close the isssue even

[Pharo-dev] Github Project Kanban Board for the Pull Requests

Hi, Sometimes it is a bit hard to understand the status of the PRs. e.g. - “I just want to help and review one” - Why is my PR not yet merged? There is now a Board with all the PRs: https://github.com/orgs/pharo-project/projects/34 Everyone who is in the “Issue Tracker” group in the

[Pharo-dev] This week (13/2023) on the Pharo Issue Tracker

We again merged ~60 PRs. Pharo11 got some bugfixes and last improvements. In Pharo12, we continue the compiler refactoring and the cleanup of ClassOrganizer. Pharo11 === Last Improvements = - Add a way to know the real processor architecture #13124

[Pharo-dev] This week (12/2023) on the Pharo Issue Tracker. We merged >60 PRs

We merged >60 PRs Of those just 16 for Pharo11, the rest are major cleanups/fixes/speedups in Pharo12. Pharo11 === - Disable ReCompactSourceCodeRule for p11 #13075 https://github.com/pharo-project/pharo/pull/13075 - Setting image version in the header of the image file #12954

[Pharo-dev] This week (11/2023) on the Pharo Issue Tracker

This week Pharo11 was frozen. We will focus now on fixing the last remaining show stopping bugs. All non-fixes are now going to the new Pharo12 branch. We merged nearly 40 Pull requests: Pharo 11 Last Improvements === - New finalization #12042

[Pharo-dev] Kanban Board for PRs

Hi, We are experimenting with a Kanban board for all the open PRs: https://github.com/orgs/pharo-project/projects/34 This could make it clearer what kind if action is needed Marcus

[Pharo-dev] Pharo Issue tracker / github "projects" access

Hi, When we started with using github, real issue tracker use (e.g adding tags, closing issues if you are not the owner…) was only possible with write access to the repository. This new changed (I guess since a while) and we can now invite people to give you more access to make it easy to

[Pharo-dev] This week (10/2023) on the Pharo Issue Tracker

We merged 32 PRs this week: Bugs - InitializedSlot-check-default #12895 https://github.com/pharo-project/pharo/pull/12895 - correcting computation of sets of protocols to remove and add #12962 https://github.com/pharo-project/pharo/pull/12962 -

[Pharo-dev] This week (9/2023) on the Pharo Issue Tracker

We merged 58 PRs this week: Compiler - Improve faulty parsing of byte array literal (alternative version) #12818 https://github.com/pharo-project/pharo/pull/12818 - NumberParser: kill requestor #12835 https://github.com/pharo-project/pharo/pull/12835 -

[Pharo-dev] This week (8/2023) on the Pharo Issue Tracker

We merged 24 PRs this week: Compiler - Improve faulty parsing #12778 https://github.com/pharo-project/pharo/pull/12778 - Improve faulty parsing of cascades #12816 https://github.com/pharo-project/pharo/pull/12816 - Improve faulty parsing of assigments #12815

[Pharo-dev] Fwd: [Pharo-users] Pharo accepted to Google Summer of Code 2023

> Begin forwarded message: > > From: Sebastian Jordan Montano > Subject: [Pharo-users] Pharo accepted to Google Summer of Code 2023 > Date: 23 February 2023 at 16:53:22 CET > To: pharo-users > Reply-To: Any question about pharo is welcome > > Hello! > We are happy to announce that we got

[Pharo-dev] This week (7/2023) on the Pharo Issue Tracker

We merged 42 PRs and closed 66 issues Fixes = - Unnecessary characters rule should be an information and not a warning #12764 https://github.com/pharo-project/pharo/pull/12764 - FIx #wantsSteps deprecated calls #12782 https://github.com/pharo-project/pharo/pull/12782

[Pharo-dev] This week (6/2023) on the Pharo Issue Tracker

We merged 60 PRs, closed 76 issues Features - Add #ensureOpen to Trascript to not open multiple transcripts while s… #12588 https://github.com/pharo-project/pharo/pull/12588 - Improve ReImplementedNotSentRule to ignore self calls + add tests #12585

[Pharo-dev] [Help needed] Please check your old issue tracker entries!

Hi, We waste a lot of time with - turning prose descriptions of fixes into code - trying to fix bugs that are already fixed - trying to understand issues that have just not enough infos One thing that would help: If everyone would regularly check their old issue tracker

[Pharo-dev] This week (4/2023) on the Pharo Issue Tracker

We merged 39 PRs and closed 77 issues. If you want to help, there are 29 PRs: https://github.com/pharo-project/pharo/pulls Features - Introduce new string comparison primitive #12504 https://github.com/pharo-project/pharo/pull/12504 - Profiler: simplify world menu

[Pharo-dev] Re: Code quality: tagging unsent selectors (e.g. in tests)

onders of the image, there's something to be said for having a limited > set of concepts in a "dead text" format that fully describe everything about > the code—and if there are too many separate pieces of UI presenting > information, it's easy to forget that some of them e

[Pharo-dev] This week (4/2023) on the Pharo Issue Tracker

This week, we merged 28 Pull requests, fixing 31 issues Fixes = - Update BaselineOfPharo with Roassal3 version v0.9.9L #12430 https://github.com/pharo-project/pharo/pull/12430 - checkIfMustRefresh in OmBlockFileStore>>blockForLocalNameAsInteger: #12197

[Pharo-dev] Re: Code quality: tagging unsent selectors (e.g. in tests)

> On 26 Jan 2023, at 11:27, Marcus Denker wrote: > > > >> On 26 Jan 2023, at 11:21, Nicolas Anquetil wrote: >> >> correct me if I am wrong, but one can already deactivate a rule in Nautilus >> on a perpackage/class/method basis. >> >> So

  1   2   3   4   5   6   7   8   9   10   >