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

[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

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

[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

[Pharo-dev] Re: [ANN] Pharo Launcher 3.2 released!

[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 
> 
> Bug fixes:
> 
>  • Pharo 12.0 build list incomplete #667 
> 
>  • Use "Show" when no image is downloaded yet gives error #570 
>  (thanks to 
> @astares )
>  • Development mode does not close pharoLauncher application #548 
> 
>  • Using "Show in folder" gives DNU #568 
>  (thanks to 
> @astares )
>  • Launcher cannot launch Pharo-4.0 image #585 
> 
> 
> 
> Regards,
> The Pharo team.

[Pharo-dev] Re: This week (28/2024) on the Pharo Issue Tracker

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

[Pharo-dev] Looking for new adventures

[Koen De Hondt]

Dear Pharo Community,

As you may have read on my blog 
 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 .

Best regards,
Koen

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

[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

[Pharo-dev] [ANN] Pharo Launcher 3.2 released!

[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 

Bug fixes:

Pharo 12.0 build list incomplete #667 

Use "Show" when no image is downloaded yet gives error #570 
 (thanks to 
@astares )
Development mode does not close pharoLauncher application #548 

Using "Show in folder" gives DNU #568 
 (thanks to 
@astares )
Launcher cannot launch Pharo-4.0 image #585 



Regards,
The Pharo team.

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

[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

[Pharo-dev] Re: [ANN] Soil release v1

[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  wrote:
> 
> 
> 
>> Am 30.06.2024 um 05:41 schrieb s...@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

[Pharo-dev] Re: [ANN] Soil release v1

[Norbert Hartl]

> Am 30.06.2024 um 05:41 schrieb s...@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

[Pharo-dev] Re: [ANN] Soil release v1

[sean]

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?

Thanks again,

Sean

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

[Marcus Denker]

# Fixes

- Fix/Patch production build zip error #16806
https://github.com/pharo-project/pharo/pull/16806

- File Browser: Add "disable preview" #788
https://github.com/pharo-spec/NewTools/pull/788

- Add #restore to the SpWindowPresenter API #1563
https://github.com/pharo-spec/Spec/pull/1563


# Refactoring Engine / Rules

- Migrate Refactoring for Generating printOn: method #16789
https://github.com/pharo-project/pharo/pull/16789

- Add indentation rules #16785
https://github.com/pharo-project/pharo/pull/16785


# Cleanup

- Move #isRoot to fast table #16800
https://github.com/pharo-project/pharo/pull/16800

- Cut dependencies of Iceberg on UI #1829
https://github.com/pharo-vcs/iceberg/pull/1829


# Website

- Update 2024-06-07-MoocOO.md: make clear that Mooc Enrollment stays open #76
https://github.com/pharo-project/pharo-website/pull/76

[Pharo-dev] Object-centric breakpoint experiment during ESUG'24

[Steven Costiou]

Dear community, 
First, I would like to thanks again all the participants to our
experiment with object-centric breakpoints in Pharo. 
Many people participated, and we plan to present our results in an
informal manner at ESUG. 
However, from the scientifical point of view it would strenghten our
analysis if we had more participants. 
The more participants we have, the more we can trust our results and
take enlightened decisions about how to further develop the
object-centric debugger. 
Therefore, the experiment remains open until July 10th (included). 
If you're interested you can still do it, the instructions are here
https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd 
Many people also declined to participate because of a lack of time,
which we totally understand. 
This is why we also propose to you, if time is an issue, to participate
to the experiment during the first days of esug. 
We can find a calm room in which we can supervise the experiment and
collect your data (reminder: once in our server the data is anonymized).

Please let us know if you would be potentially interested to participate
in such setting during ESUG. 
Thanks in advance, 
Steven and Valentin, EVREF team. 

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

[Marcus Denker]

This week we backported some fixes to Pharo12, mostly related to high 
resolution rendering and Traits

# Pharo 12

- Backport change of default value for setting #autoSetCanvasScaleFactor to 
true #16783
https://github.com/pharo-project/pharo/pull/16783

- Remove (wrong) primitive usage #16781
https://github.com/pharo-project/pharo/pull/16781

- [Backport] Port fixes on traits and metaclasses to Pharo 12 #16776
https://github.com/pharo-project/pharo/pull/16776

- Backport use of FormSet for #withCloseBox and #withPinBox on MenuTitleMorph 
#16774
https://github.com/pharo-project/pharo/pull/16774

- Backport selective removal of entries in #shrinkTo: on FreeTypeCache #16773
https://github.com/pharo-project/pharo/pull/16773

- [P12][Backport] fix #needRequestorScope of StDebuggerContextInteractionModel 
so that its bindings can be used when evaluating code in the debugger #784
https://github.com/pharo-spec/NewTools/pull/784

# VM

- New harmonize rule #817
https://github.com/pharo-project/pharo-vm/pull/817

- Fixing warnings that are errors in newer versions of clang #813
https://github.com/pharo-project/pharo-vm/pull/813

- Adding an implementation of the aio.c using EPOLL in Linux. #805
https://github.com/pharo-project/pharo-vm/pull/805

- Ignoring EAGAIN in epoll_wait #818
https://github.com/pharo-project/pharo-vm/pull/818

# Features

- Update roassal to v1.06f #16770
https://github.com/pharo-project/pharo/pull/16770

- Propose a DarkBlueTheme #16777
https://github.com/pharo-project/pharo/pull/16777

- Make setting pages less dense without comments for each setting #772
https://github.com/pharo-spec/NewTools/pull/772

# Fixes

- test file dialogs returns the selected file #778
https://github.com/pharo-spec/NewTools/pull/778

- Revert "Use taskbar icon name for inspector and playground" #779
https://github.com/pharo-spec/NewTools/pull/779

- Fix issue when opening custom scope on calypso #783
https://github.com/pharo-spec/NewTools/pull/783

- Fix Open Playground menu item hanging the image #787
https://github.com/pharo-spec/NewTools/pull/787

- Add back old playground shortcut with deprecation #16788
https://github.com/pharo-project/pharo/pull/16788

- Remove (wrong) primitive usage #16780
https://github.com/pharo-project/pharo/pull/16780

- add missing accessor #1558
https://github.com/pharo-spec/Spec/pull/1558

- adding test to ensure it is possible to recompile code within a bloc with a 
dead home context twice #723
https://github.com/pharo-spec/NewTools/pull/723


# Refactoring Engine

- Migrate Refactoring for Generating Equal and Hash Methods #16786
https://github.com/pharo-project/pharo/pull/16786


# Cleanup

- Remove call to deprecated Author #83
https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/83

- Remove deprecated classes and methods #758
https://github.com/pharo-spec/NewTools/pull/758

- Removing UIMnagaer dependencies from the debugger infrastructure #16015
https://github.com/pharo-project/pharo/pull/16015

- The debugger now delegate UI decisions to the backend provided by its 
application #667
https://github.com/pharo-spec/NewTools/pull/667

- Fix deprecated usage of StInspector #16769
https://github.com/pharo-project/pharo/pull/16769

- taskbarIcon moved to SystemWindow #16792
https://github.com/pharo-project/pharo/pull/16792

- Rename RBNode into ASTNode #16596
https://github.com/pharo-project/pharo/pull/16596

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

[Marcus Denker]

# Pharo 12

- Fix Issue: Backport Pharo12: Wrong source for CompiledBlocks due to incorrect 
bytecode to AST nodes mapping #16756
https://github.com/pharo-project/pharo/pull/16756


# Improvemetns

- Adds a simple MoveTo taskbar menu item #16544
https://github.com/pharo-project/pharo/pull/16544

- replace JPEGReadWriter by PluginBasedJPEGReadWriter and deprecate the… #16535
https://github.com/pharo-project/pharo/pull/16535

- return the result of ok action and simplify file selection #776
https://github.com/pharo-spec/NewTools/pull/776

- withWindowDo: should return the result of the block #1555
https://github.com/pharo-spec/Spec/pull/1555

- Update after selection in Color Picker #766
https://github.com/pharo-spec/NewTools/pull/766

- New dialog to select multiple items using checkboxes #1548
https://github.com/pharo-spec/Spec/pull/1548


# Fixes

- fix preLoading.st #1557
https://github.com/pharo-spec/Spec/pull/1557

- fixing recompilation of bloc in the debugger with dead home context whose 
method has already been recompiled in the debugger before #16319
https://github.com/pharo-project/pharo/pull/16319

- Fix comparison of two Deprecation objects #16735
https://github.com/pharo-project/pharo/pull/16735

- Updated text to new shortcut #764
https://github.com/pharo-spec/NewTools/pull/764


# Tools

- Added new subclass with unified view based on SpDiffPresenter #1452
https://github.com/pharo-spec/Spec/pull/1452

- Add StProtocolNameChooserPresenter #759
https://github.com/pharo-spec/NewTools/pull/759

- Spotter split case #773
https://github.com/pharo-spec/NewTools/pull/773

- Use new StProtocolNameChooserPresenter to replace morphic tool #16690
https://github.com/pharo-project/pharo/pull/16690

- Icon for debugger in the toolbar #16661
https://github.com/pharo-project/pharo/pull/16661

- ProfilerUI: Added a warning when trying to compile and the variables are not 
declared #741
https://github.com/pharo-spec/NewTools/pull/741

- Update playground shortcut #738
https://github.com/pharo-spec/NewTools/pull/738


# Cleanups

- Remove deprecated code #1545
https://github.com/pharo-spec/Spec/pull/1545

- Remove references to SystemAnnouncer singleton #742
https://github.com/pharo-spec/NewTools/pull/742

- Move some debugger related code of Process to debugger packages #15799
https://github.com/pharo-project/pharo/pull/15799

- Moved pragma declaration to top of methods #16728
https://github.com/pharo-project/pharo/pull/16728

- Categorization rules tests #16767
https://github.com/pharo-project/pharo/pull/16767

[Pharo-dev] Re: [ANN] New MOOC "Advanced Object-Oriented Design"

[David Mason]

Great to see this!

I've forwarded it to all my students.

../Dave

On Mon, 10 Jun 2024 at 09:54, Noury Bouraqadi  wrote:

> Well done guys! 
> This Mooc is must!
> I liked the video and forwarded to some people that would benefit from the
> Mooc.
>
> On Jun 7 2024, at 10:23 am, Marcus Denker  wrote:
>
> [ANN] New MOOC "Advanced Object-Oriented Design”
>
>  English
>
>

[Pharo-dev] Re: [ANN] New MOOC "Advanced Object-Oriented Design"

[Noury Bouraqadi]

Well done guys! 
This Mooc is must!
I liked the video and forwarded to some people that would benefit from the Mooc.

On Jun 7 2024, at 10:23 am, Marcus Denker  wrote:
> [ANN] New MOOC "Advanced Object-Oriented Design”
>
> English

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

[Marcus Denker]

# Pharo 12

- Fix/Update Iceberg #16752
https://github.com/pharo-project/pharo/pull/16752

- 16733-Backport-Pharo12-DebugPoint-on-class-side-method-16682 #16734
https://github.com/pharo-project/pharo/pull/16734

- fix bad label before first progress event. #1551
https://github.com/pharo-spec/Spec/pull/1551

- Updating LibGit2 #1827
https://github.com/pharo-vcs/iceberg/pull/1827


# Features

- Add newTenured allocation methods #16729
https://github.com/pharo-project/pharo/pull/16729

- Fix ZnBufferedWriteStream does not support #reset #16727
https://github.com/pharo-project/pharo/pull/16727

- Primitive format #802
https://github.com/pharo-project/pharo-vm/pull/802

# Fixes

- fix bad label before first progress event. #1552
https://github.com/pharo-spec/Spec/pull/1552

- add missing code from P12 #763
https://github.com/pharo-spec/NewTools/pull/763

- 
16495-Wrong-source-for-CompiledBlocks-due-to-incorrect-bytecode-to-AST-nodes-mapping
 #16664
https://github.com/pharo-project/pharo/pull/16664

- Calypso cmd-v method versions shortcut #16742
https://github.com/pharo-project/pharo/pull/16742

- Fix Random seed with float value #16738
https://github.com/pharo-project/pharo/pull/16738

# Refactoring Engine

- Add subclass driver #16353
https://github.com/pharo-project/pharo/pull/16353

- Refactor: inline method cleaning #16745
https://github.com/pharo-project/pharo/pull/16745

# Rules

- Add setting rules feature #16750
https://github.com/pharo-project/pharo/pull/16750

- Move rules matadatas to class side #16705
https://github.com/pharo-project/pharo/pull/16705


# ClassBuilder / Traits

- Fix multiple bugs in metaclass management of ShiftClassBuilder #16722
https://github.com/pharo-project/pharo/pull/16722

- Fix bug causing classes to lose their traits. #16739
https://github.com/pharo-project/pharo/pull/16739

- Use #update:to: instead of #make: and #fillFor: #16746
https://github.com/pharo-project/pharo/pull/16746

# Cleanups

- Remove deprecated aliases of P12 #16659
https://github.com/pharo-project/pharo/pull/16659

[Pharo-dev] 12 Month engineer position at Toulouse in Pharo

[stephane ducasse]

Hi people 

Can you distribute this job position around you?

Yannick Chevalier has a position to develop a tool to detect abnomalies
Développement de l’outil iCANt pour la détection d’anomalies

 
Who: yannick.cheval...@gmail.com 
Where: Toulouse
Salary: 45 K Euros a more experienced dev could be hired for a shorter 
period and get a better salary.

S.

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

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

[Marcus Denker]

# Pharo 12

- Backport use of icon #smallPharo in #pharoItemsOn: for WorldState and 
#menuCommandOn: for ProfStef #16695
https://github.com/pharo-project/pharo/pull/16695


# Fixes

- fix Reflectivity API #link:toAST: for metaclasses to fix debug points on 
class-side methods #16701
https://github.com/pharo-project/pharo/pull/16701

- Pharo13 fficalls athens cairo surface #16679
https://github.com/pharo-project/pharo/pull/16679

- Fix a small bug with FFI calls when passing 'NULL' as argument to the C 
function #16562
https://github.com/pharo-project/pharo/pull/16562

- eflectivity fixing bytecode to ast mapping #16489
https://github.com/pharo-project/pharo/pull/16489

# Improvements

- Add libgit 1.8 support for Pharo 13 #86
https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/86

- It should be possible to reset a ZnCharacterReadStream #16707
https://github.com/pharo-project/pharo/pull/16707

- Make #withCloseBox and #withPinBox on MenuTitleMorph use a FormSet for the 
button label #16696
https://github.com/pharo-project/pharo/pull/16696

- fix #needRequestorScope of StDebuggerContextInteractionModel so that its 
bindings can be used when evaluating code in the debugger #762
https://github.com/pharo-spec/NewTools/pull/762

- Adopt to new spec #761
https://github.com/pharo-spec/NewTools/pull/761

- Adding entry completion setter to SpRequestDialog #1540
https://github.com/pharo-spec/Spec/pull/1540

# Cleanups

- Cleanup TraitTest>>#testRemovingTraitsRemoveTraitedClassMethodsWithSubclasses 
#16717
https://github.com/pharo-project/pharo/pull/16717

- Cleanup ReOverridingExtentsionMethod>>#basicCheck: #16715
https://github.com/pharo-project/pharo/pull/16715

- Fix lint issue on ZnEncodedStream #16713
https://github.com/pharo-project/pharo/pull/16713

- Fix lint issues on ZnEncodedReadStream #16711
https://github.com/pharo-project/pharo/pull/16711

- Cleanup: ZnCharacterEncoder, ZnEncodedStream, ZnEncodedReadStream and 
ZnEncodedWriteStream should be abstract classes #16709
https://github.com/pharo-project/pharo/pull/16709

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

[Marcus Denker]

# Pharo 11 backports

- P11 - During compilation there are redundant allocation of collections #16485
https://github.com/pharo-project/pharo/pull/16485

# Pharo 12

- Fix for pharo/pharo-project#16677: libgit2 library not listed in 
LGitLibrary>>#unix64LibraryName #85
https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/85


# Fixes

- 15652-Check-and-add-test-for--CompiledCodenewFrom #16663
https://github.com/pharo-project/pharo/pull/16663

- Debug points cleaning fixing #16670
https://github.com/pharo-project/pharo/pull/16670

- Change #pharoItemsOn: for WorldState and #menuCommandOn: for ProfStef to use 
the icon #smallPharo #16496
https://github.com/pharo-project/pharo/pull/16496


# Scriptable Debugger

- Migrate to Tonel V3 #97
https://github.com/pharo-spec/ScriptableDebugger/pull/97

- Cleanup: do not use #notNil, use #isNotNil instead #96
https://github.com/pharo-spec/ScriptableDebugger/pull/96

# Rules / Refactoring Engine

- Make class abstract driver #16347
https://github.com/pharo-project/pharo/pull/16347

- proposition for a potential new rule: use deny: instead of 
assert:equals:false #16668
https://github.com/pharo-project/pharo/pull/16668

# Cleanup

- Debug point refactoring #757
https://github.com/pharo-spec/NewTools/pull/757

- Remove empty Manifests from baseline packages, synchronize on the tag… #16537
https://github.com/pharo-project/pharo/pull/16537

- Remove VariableLayout from tests #16686
https://github.com/pharo-project/pharo/pull/16686

- 16680-Zinc-uses-old-Announcers-API #16681
https://github.com/pharo-project/pharo/pull/16681

- 16608 cleanup crown initialize should call super initialize #16676
https://github.com/pharo-project/pharo/pull/16676

- Deprecate RPackageSet #16675
https://github.com/pharo-project/pharo/pull/16675

- Update call to a deprecated class #16671
https://github.com/pharo-project/pharo/pull/16671

- fixes #16610: Cleanup: simple typo in Crown class comment #1
https://github.com/pharo-project/pharo/pull/1

[Pharo-dev] Re: Info required for bootstrapping pharo on GNU Guix

[Tim Mackinnon]

While it sounds like a lot of work - if thats your itch I suppose its a good 
test of the work that Stephane mentions. By redoing it in a different 
environment it might iron out any accidental environment dependencies.

Presumably its just the VM you need to bootstrap - as I would view the image as 
being like a Word or PDF document - and would be surprised that they would 
expect you to bootstrap those too?

Good luck - and courage.

Tim

On Tue, 21 May 2024, at 9:47 AM, Nicolas Graves via Pharo-dev wrote:
> On 2024-05-21 09:34, stephane ducasse wrote:
>
>> Hi 
>>
>> Why can’t you use the latest Pharo vm and Pharo12?
>> We worked like mad over the years to get a much better system. 
>> Now why do you need to bootstrap Pharo because you can just use a 
>> bootstrapped image
>> and get pharo working and running?
>
> Guix is not using the FHS filesystem so it would be a mess to try and
> bootstrap from binaries. On top of that, they focus on
> reproducibility. The standard on this end is to try and not use any
> binary code if it's possible to build if from source, and yes, it
> requires working like mad over the years. The website is currently down,
> but there's an article about how they get all 30k packages from only a
> single tiny binary file.
>
> Some of the guys behind Guix are also involved in bootstrappable.org
>
> I understand and share that the current system is much better, it's just
> that to comply with their standard, that's what I have to do.
>
> What I understand from there it that it's feasible: 
> https://x.com/estebanlm/status/1042719107307712514
>
> I'll do the work if feasible, I just can't find the information where I
> should start from, hence my email.
>
> Best,
> Nicolas
>
>>
>> S
>>
>>> On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev 
>>>  wrote:
>>> 
>>> Hi Pharo community,
>>> 
>>> I'm trying to package pharo in the GNU Guix linux distribution. Since
>>> the distribution is focused on reproducibility and avoids using binary
>>> code when possible, for that I need to reproduce the bootstrapping steps
>>> that are embedded in Pharo. I understand from some developper online
>>> comment that this is possible.
>>> 
>>> I've started to work on this and it seems feasible, at least I get the
>>> dependency loop, what I've some difficulty is to get precisely when it's
>>> possible to get started.
>>> 
>>>  ---
>>>  | v
>>>  pharo VMpharo
>>>  ∧ |
>>>  ---
>>> 
>>> If I'm correct,
>>> - bootstrapping is very clear after version ~7.0.0, and with a proper
>>> build, just follow the distribution numbers in wget's with a cmake
>>> build-system.
>>> - for earlier versions, there's the repository
>>> https://github.com/pharo-project/PharoBootstrap
>>> that seems (git history) to be able to go back to Pharo 30.
>>> - I understand that at some point, Squeak and Pharo used to have the
>>> same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen
>>> this is in Pharo's ftp files, so I guess I can start there.
>>> 
>>> What I need:
>>> - Some indication about the first version of Pharo that I'm able to
>>> build purely from squeak-vm, and where to find its source code
>>> (git+version or commit if possible, I seem to only be able to find its
>>> binaries currently in phero's ftp files).
>>> - Any useful information for early bootstrap steps.
>>> 
>>> Some useful information on my side:
>>> - During the build process in Guix, we can't download data, so the
>>> entire bootstrap chain has to be explicited at once, hence the need to
>>> go back to the beginning in this case.
>>> 
>>> Thanks in advance!
>>> 
>>> -- 
>>> Best regards,
>>> Nicolas Graves
>>
>> 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
>>
>>
>>
>>
>>
>
> -- 
> Best regards,
> Nicolas Graves

[Pharo-dev] Re: Info required for bootstrapping pharo on GNU Guix

[Nicolas Graves via Pharo-dev]

On 2024-05-21 09:34, stephane ducasse wrote:

> Hi 
>
> Why can’t you use the latest Pharo vm and Pharo12?
> We worked like mad over the years to get a much better system. 
> Now why do you need to bootstrap Pharo because you can just use a 
> bootstrapped image
> and get pharo working and running?

Guix is not using the FHS filesystem so it would be a mess to try and
bootstrap from binaries. On top of that, they focus on
reproducibility. The standard on this end is to try and not use any
binary code if it's possible to build if from source, and yes, it
requires working like mad over the years. The website is currently down,
but there's an article about how they get all 30k packages from only a
single tiny binary file.

Some of the guys behind Guix are also involved in bootstrappable.org

I understand and share that the current system is much better, it's just
that to comply with their standard, that's what I have to do.

What I understand from there it that it's feasible: 
https://x.com/estebanlm/status/1042719107307712514

I'll do the work if feasible, I just can't find the information where I
should start from, hence my email.

Best,
Nicolas

>
> S
>
>> On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev 
>>  wrote:
>> 
>> Hi Pharo community,
>> 
>> I'm trying to package pharo in the GNU Guix linux distribution. Since
>> the distribution is focused on reproducibility and avoids using binary
>> code when possible, for that I need to reproduce the bootstrapping steps
>> that are embedded in Pharo. I understand from some developper online
>> comment that this is possible.
>> 
>> I've started to work on this and it seems feasible, at least I get the
>> dependency loop, what I've some difficulty is to get precisely when it's
>> possible to get started.
>> 
>>  ---
>>  | v
>>  pharo VMpharo
>>  ∧ |
>>  ---
>> 
>> If I'm correct,
>> - bootstrapping is very clear after version ~7.0.0, and with a proper
>> build, just follow the distribution numbers in wget's with a cmake
>> build-system.
>> - for earlier versions, there's the repository
>> https://github.com/pharo-project/PharoBootstrap
>> that seems (git history) to be able to go back to Pharo 30.
>> - I understand that at some point, Squeak and Pharo used to have the
>> same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen
>> this is in Pharo's ftp files, so I guess I can start there.
>> 
>> What I need:
>> - Some indication about the first version of Pharo that I'm able to
>> build purely from squeak-vm, and where to find its source code
>> (git+version or commit if possible, I seem to only be able to find its
>> binaries currently in phero's ftp files).
>> - Any useful information for early bootstrap steps.
>> 
>> Some useful information on my side:
>> - During the build process in Guix, we can't download data, so the
>> entire bootstrap chain has to be explicited at once, hence the need to
>> go back to the beginning in this case.
>> 
>> Thanks in advance!
>> 
>> -- 
>> Best regards,
>> Nicolas Graves
>
> 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
>
>
>
>
>

-- 
Best regards,
Nicolas Graves

[Pharo-dev] Re: Info required for bootstrapping pharo on GNU Guix

[stephane ducasse]

Hi 

Why can’t you use the latest Pharo vm and Pharo12?
We worked like mad over the years to get a much better system. 
Now why do you need to bootstrap Pharo because you can just use a bootstrapped 
image
and get pharo working and running?

S

> On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev 
>  wrote:
> 
> Hi Pharo community,
> 
> I'm trying to package pharo in the GNU Guix linux distribution. Since
> the distribution is focused on reproducibility and avoids using binary
> code when possible, for that I need to reproduce the bootstrapping steps
> that are embedded in Pharo. I understand from some developper online
> comment that this is possible.
> 
> I've started to work on this and it seems feasible, at least I get the
> dependency loop, what I've some difficulty is to get precisely when it's
> possible to get started.
> 
>  ---
>  | v
>  pharo VMpharo
>  ∧ |
>  ---
> 
> If I'm correct,
> - bootstrapping is very clear after version ~7.0.0, and with a proper
> build, just follow the distribution numbers in wget's with a cmake
> build-system.
> - for earlier versions, there's the repository
> https://github.com/pharo-project/PharoBootstrap
> that seems (git history) to be able to go back to Pharo 30.
> - I understand that at some point, Squeak and Pharo used to have the
> same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen
> this is in Pharo's ftp files, so I guess I can start there.
> 
> What I need:
> - Some indication about the first version of Pharo that I'm able to
> build purely from squeak-vm, and where to find its source code
> (git+version or commit if possible, I seem to only be able to find its
> binaries currently in phero's ftp files).
> - Any useful information for early bootstrap steps.
> 
> Some useful information on my side:
> - During the build process in Guix, we can't download data, so the
> entire bootstrap chain has to be explicited at once, hence the need to
> go back to the beginning in this case.
> 
> Thanks in advance!
> 
> -- 
> Best regards,
> Nicolas Graves

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

[Pharo-dev] Re: Info required for bootstrapping pharo on GNU Guix

[stephane ducasse]

Hi 

Why can’t you use the latest Pharo vm and Pharo12?
We worked like mad over the years to get a much better system. 
Now why do you need to bootstrap Pharo because you can just use a bootstrapped 
image
and get pharo working and running?

S

> On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev 
>  wrote:
> 
> Hi Pharo community,
> 
> I'm trying to package pharo in the GNU Guix linux distribution. Since
> the distribution is focused on reproducibility and avoids using binary
> code when possible, for that I need to reproduce the bootstrapping steps
> that are embedded in Pharo. I understand from some developper online
> comment that this is possible.
> 
> I've started to work on this and it seems feasible, at least I get the
> dependency loop, what I've some difficulty is to get precisely when it's
> possible to get started.
> 
>  ---
>  | v
>  pharo VMpharo
>  ∧ |
>  ---
> 
> If I'm correct,
> - bootstrapping is very clear after version ~7.0.0, and with a proper
> build, just follow the distribution numbers in wget's with a cmake
> build-system.
> - for earlier versions, there's the repository
> https://github.com/pharo-project/PharoBootstrap
> that seems (git history) to be able to go back to Pharo 30.
> - I understand that at some point, Squeak and Pharo used to have the
> same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen
> this is in Pharo's ftp files, so I guess I can start there.
> 
> What I need:
> - Some indication about the first version of Pharo that I'm able to
> build purely from squeak-vm, and where to find its source code
> (git+version or commit if possible, I seem to only be able to find its
> binaries currently in phero's ftp files).
> - Any useful information for early bootstrap steps.
> 
> Some useful information on my side:
> - During the build process in Guix, we can't download data, so the
> entire bootstrap chain has to be explicited at once, hence the need to
> go back to the beginning in this case.
> 
> Thanks in advance!
> 
> -- 
> Best regards,
> Nicolas Graves

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

[Pharo-dev] Info required for bootstrapping pharo on GNU Guix

[Nicolas Graves via Pharo-dev]

Hi Pharo community,

I'm trying to package pharo in the GNU Guix linux distribution. Since
the distribution is focused on reproducibility and avoids using binary
code when possible, for that I need to reproduce the bootstrapping steps
that are embedded in Pharo. I understand from some developper online
comment that this is possible.

I've started to work on this and it seems feasible, at least I get the
dependency loop, what I've some difficulty is to get precisely when it's
possible to get started.

  ---
  | v
  pharo VMpharo
  ∧ |
  ---

If I'm correct,
- bootstrapping is very clear after version ~7.0.0, and with a proper
build, just follow the distribution numbers in wget's with a cmake
build-system.
- for earlier versions, there's the repository
https://github.com/pharo-project/PharoBootstrap
that seems (git history) to be able to go back to Pharo 30.
- I understand that at some point, Squeak and Pharo used to have the
same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen
this is in Pharo's ftp files, so I guess I can start there.

What I need:
- Some indication about the first version of Pharo that I'm able to
build purely from squeak-vm, and where to find its source code
(git+version or commit if possible, I seem to only be able to find its
binaries currently in phero's ftp files).
- Any useful information for early bootstrap steps.

Some useful information on my side:
- During the build process in Guix, we can't download data, so the
entire bootstrap chain has to be explicited at once, hence the need to
go back to the beginning in this case.

Thanks in advance!

-- 
Best regards,
Nicolas Graves

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

[Marcus Denker]

# Pharo 12

- Backport use of FormSet for ToggleMenuItemMorph submenu markers #16631
https://github.com/pharo-project/pharo/pull/16631

# Ehancements

- [Enhancement] Add "copy class name" to extras menu in Calypse #16635
https://github.com/pharo-project/pharo/pull/16635

- Add missing RGGlobalVariable>>isInstanceVariable #16644
https://github.com/pharo-project/pharo/pull/16644

- Introduce CompiledMethod>>#isInstanceSide #16626
https://github.com/pharo-project/pharo/pull/16626

# Fixes

- Issue 16430 - String>> asSymbol no protected against concurrent access 
(alternative solution) #16565
https://github.com/pharo-project/pharo/pull/16565

- [Bug]: Date>>#addMonths: should Respect Offset #16603
https://github.com/pharo-project/pharo/pull/16603

- sort subdirectories in the same order as the file tree table #748
https://github.com/pharo-spec/NewTools/pull/748


# VM

- Fixed VirtualMachine 76 and 78 parameters #16641
https://github.com/pharo-project/pharo/pull/16641

- Do not retain any selectors in CogAbstractInstruction #798
https://github.com/pharo-project/pharo-vm/pull/798

- add tests for type harmonization #807
https://github.com/pharo-project/pharo-vm/pull/807

- remove warning because of type and unsigned shift issues #800
https://github.com/pharo-project/pharo-vm/pull/800

- Fixed ntb page selection change announcement if built without pages #1542
https://github.com/pharo-spec/Spec/pull/1542

# Package Structure

- Sindarin/ScriptableDebugger should be listed as external project #16653
https://github.com/pharo-project/pharo/pull/16653

- Sindarin in Pharo13 need to be loaded from Pharo13 branch of 
ScriptableDebugger (and not Pharo12 branch) #751
https://github.com/pharo-spec/NewTools/pull/751

- Simplify Calypso packaging #16602
https://github.com/pharo-project/pharo/pull/16602

- Cleanup: CoverageCollectorTest should be in an own test package #16613
https://github.com/pharo-project/pharo/pull/16613

# Rules

- proposition rule for nil branch #16547
https://github.com/pharo-project/pharo/pull/16547

- [Enhancement] Add a rule ReBaselineProperlyPackagedRule #16630
https://github.com/pharo-project/pharo/pull/16630

- [Enhancement] Add a rule ReBaselineWithProperSuperclassRule #16633
https://github.com/pharo-project/pharo/pull/16633

- proposition for a potential new rule: useless ifTrue:ifFalse: #16638
https://github.com/pharo-project/pharo/pull/16638

- add ReStatementsAfterReturnConditionalRule #16640
https://github.com/pharo-project/pharo/pull/16640

- Review ReClassNotCategorizedRuleTest>>#testRule #16649
https://github.com/pharo-project/pharo/pull/16649

- Improve ReBaselineProperlyPackagedRule and ReBaselineWithProperSuperclassRule 
and cover with tests #16648
https://github.com/pharo-project/pharo/pull/16648

- Enhancement: Provide a lint rule to check for a "super initialize" call in 
instance side #initialize methods #16615
https://github.com/pharo-project/pharo/pull/16615

- tests for rules from the General-Rules package #16474
https://github.com/pharo-project/pharo/pull/16474

# Cleanups

- Reduce references to Undeclared global variable #16642
https://github.com/pharo-project/pharo/pull/16642

- Remove deprecated way to access the global package organizer #754
https://github.com/pharo-spec/NewTools/pull/754

- Remove the package Deprecated12, introduce package Deprecated13 #16538
https://github.com/pharo-project/pharo/pull/16538

- proposition refactoring -> Cleanup: 2 duplicated methods in FreeType #16583
https://github.com/pharo-project/pharo/pull/16583

- Clean up in SDL_Texture and SDL_Renderer #16601
https://github.com/pharo-project/pharo/pull/16601

- Simplify script pragma for FinderUI #16623
https://github.com/pharo-project/pharo/pull/16623

- CommentTestCase should be moved to PharoDocComment-Tests #16619
https://github.com/pharo-project/pharo/pull/16619

- Package "System-DependenciesTests" should be "System-Dependencies-Tests" 
#16621
https://github.com/pharo-project/pharo/pull/16621

- Cleanup: AthensTransformTest>>transformClass should be in accessing #16628
https://github.com/pharo-project/pharo/pull/16628

- Fix lint in ReShouldSendSuperSetUpAsFirstMessage class>>#checksMethod (second 
PR) #16643
https://github.com/pharo-project/pharo/pull/16643

- Remove part of ReAsClassRule about #asClass #16658
https://github.com/pharo-project/pharo/pull/16658

- Cleanup: Remove deprecated announcement #SnapshotDone in 
SnapshotOperation>>#performSnapshot for Pharo 13 #16657
https://github.com/pharo-project/pharo/pull/16657

- Cleanup: unnecessary class BlLoadProjectWorldMenu #16655

[Pharo-dev] IWST Deadline Extension

[Guille Polito]

Dear Community,

Please let us inform you that the submission deadline for the full/short papers 
has been extended until May 31st, 2024 AoE.

Let us remind you of the submission details:
- Short position papers (5 to 10 pages) describing fresh ideas and early 
results.
- Full papers (more than 10 pages) with deeper descriptions of experiments and 
research results.

Please also consider that you may submit another work other than your original 
abstract.

Paper accepted for publishing will be published within a *CEUR-WS 
Proceedings>https://ceur-ws.org/*.
Hence, both submissions and final papers must be prepared using the *CEUR ART 
style>https://ceur-ws.org/Vol-XXX/CEURART.zip*.
We recommend using the template in single-column style, although you may use 
two columns.
CEUR proceedings accept papers in both styles as soon as they follow the 
template and have 5 or more pages.

The IWST team, Gordana, Guille, and Steven
https://esug.org/2024-Conference/IWST2024.html

[Pharo-dev] [Website] updated forms to suggest companies and news entries

[Marcus Denker]

Hi,

I have updated two forms ob pharo.org

1) Companies using Pharo

https://www.pharo.org/Companies
   
2) Suggest news 
 https://www.pharo.org/community
see the link in the Social Media section


The forms for now have simple workflows attached to send emails to do the next 
step manually.


Marcus

[Pharo-dev] Re: Open Call: Object-Centric Breakpoints experiment

[Steven Costiou]

Dear community, 

we are still looking for participants for our experiment in the EVREF
team!
Please help us! 

We need 15 more participants, if you are interested and if you believe
you can work your way around a debugger, the experiment is fully
available online here (using Pharo 9): 

https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd 

We would like to show our results at ESUG, but for that we really need
these 15 additional participations so that we can trust the results
better. 

Thanks in advance,
and many thanks to the people who already participated! 

Steven. 

Le 2024-02-02 14:14, Steven Costiou a écrit :

> Dear Community, 
> 
> as part of a research project in the EVREF team, we are looking for people to 
> participate to an empirical experiment on object-centric breakpoints - a 
> debugging tool present in Pharo 9. 
> 
> Many people from the community already participated, and we thank them very 
> much   
> 
> We are still looking for participants, we need 40 people to do the 
> experiment! 
> 
> Please help us, in return it helps us understand better our tools and their 
> impact and therefore build better tools for the Pharo community! 
> 
> For those who want to know a bit more, see my original email below. 
> For those who just want to jump at the experiment, you can go there 
> https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd 
> 
> Thanks in advance  
> Steven. 
> 
> --- 
> 
> We would like to invite you to participate to our experimental study on 
> Object-Centric Breakpoints. 
> This study aims to evaluate and to understand how Object-Centric Breakpoints 
> impacts the debugging activity. 
> 
> This experiment takes place in **Pharo 9**. 
> In this experiment, we ask you to solve 2 debugging tasks, one with standard 
> Pharo tools and one other with Object-Centric Breakpoints. 
> Between the two tasks, you will have to follow a tutorialand warmup tasks to 
> learn how to use the tool. 
> 
> **How to Participate:** 
> All instructions are here, please read them carefully: 
> https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd 
> 
> **About the Experiment:** 
> 
> The experiment last between 40 minutes and 2 hours. 
> Participants should have experience with Pharo development and debugging. 
> We recommend having more than 6 months experience in Pharo and debugging in 
> general. 
> You will gain insights into the Object-Centric Breakpoints approach and 
> contribute to advancements in debugging research. 
> 
> Help us to build better debugging tools that help you debug! 
> 
> **Some constraints:** 
> 
> - You are not allowed to load external tools and baselines, but you can use 
> anything that is in the base image 
> - Please do the experiment in one shot if possible without interruptions 
> - The experiment sends anonymous data to our inria server, please make sure 
> that you have a valid internet connection 
> - Please try to use the object-centric breakpoints when the experimental 
> framework asks you to 
> 
> **Notes:** 
> Participation is voluntary, and everything is anonymous. 
> You can abandon the experiment at any point (and your data will be 
> discarded). 
> For any question, you can contact us: steven.cost...@inria.fr and 
> valentin.bourc...@inria.fr 
> 
> Thank you for considering participating in our study. 
> Your contribution will be valuable in advancing the field of debugging and 
> helping us understand what tools we need to build for Pharo. 
> 
> Sincerely, 
> Steven and Valentin, 
> EVREF team, Inria

  

[Pharo-dev] Re: [Pharo-users] This week (19/2024) on the Pharo Issue Tracker

[stephane ducasse]

Yes I understood that after sending my mail 


> On 13 May 2024, at 11:56, Marcus Denker  wrote:
> 
> Only the first issue is for Pharo 12, all the other for Pharo 13.
> (the idea is to have just one headline Pharo 12 for all the issues backported)
> 
>   Marcus
> 
>> On 13 May 2024, at 15:31, stephane ducasse  wrote:
>> 
>> Hi
>> 
>> I imagine that this is for Pharo 13 
>> 
>> S
>> 
>>> On 13 May 2024, at 03:11, Marcus Denker  wrote:
>>> 
>>> # Pharo 12
>>> 
>>> - 16576-Problem-with-completion-in-the-tutorial #16582
>>> https://github.com/pharo-project/pharo/pull/16582
>>> 
>>> 
>>> # Virtual Machine
>>> 
>>> - Bump to MacOS 11 and above #792
>>> https://github.com/pharo-project/pharo-vm/pull/792
>>> 
>>> - Do not use asserta: in a statement #788
>>> https://github.com/pharo-project/pharo-vm/pull/788
>>> 
>>> - Moving pharo.signatures files for OSX Bundle to Resources folder #770
>>> https://github.com/pharo-project/pharo-vm/pull/770
>>> 
>>> 
>>> # Features
>>> 
>>> - New debugger extension model to display dynamic extensions #739
>>> https://github.com/pharo-spec/NewTools/pull/739
>>> 
>>> - add asAccessor #16579
>>> https://github.com/pharo-project/pharo/pull/16579
>>> 
>>> - Make it easier to diagnose mock failures by printing message sends 
>>> properly and storing the send history in the mock #16555
>>> https://github.com/pharo-project/pharo/pull/16555
>>> 
>>> - add two's complement display for negative integers #746
>>> https://github.com/pharo-spec/NewTools/pull/746
>>> 
>>> # Fixes
>>> 
>>> - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510
>>> https://github.com/pharo-project/pharo/pull/16510
>>> 
>>> - Taskbar option to close windows hidden behind other windows #16552
>>> https://github.com/pharo-project/pharo/pull/16552
>>> 
>>> - prof stef lesson view did not understand has binding of #16578
>>> https://github.com/pharo-project/pharo/pull/16578
>>> 
>>> - fix precedence computation #16581
>>> https://github.com/pharo-project/pharo/pull/16581
>>> 
>>> # Refactoring Engine
>>> 
>>> - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600
>>> https://github.com/pharo-project/pharo/pull/16600
>>> 
>>> - Refactor: preconditions return array of preconditions by default #16527
>>> https://github.com/pharo-project/pharo/pull/16527
>>> 
>>> 
>>> # Rules
>>> 
>>> - add ReOverridingExtentsionMethod rule #16550
>>> https://github.com/pharo-project/pharo/pull/16550
>>> 
>>> - add rule to avoid that TestCase rely on Initialize #16513
>>> https://github.com/pharo-project/pharo/pull/16513
>>> 
>>> # Tests (Green tests on CI)
>>> 
>>> - Fix testCodeCruftLeftInMethods #16598
>>> https://github.com/pharo-project/pharo/pull/16598
>>> 
>>> - Update roassal to v1.06d #16595
>>> https://github.com/pharo-project/pharo/pull/16595
>>> 
>>> - Fixing reflectivity tests that can randomly fail because of unstable and 
>>> unpredictable tests generating methods #16584
>>> https://github.com/pharo-project/pharo/pull/16584
>>> 
>>> - 16569-CI-Pharo13-code-with-halt-was-merged #16570
>>> https://github.com/pharo-project/pharo/pull/16570
>>> 
>>> - clearing debugger subscriptions and subcomponents in 
>>> StDebuggerExtensionMechanismTest>>#tearDown #712
>>> https://github.com/pharo-spec/NewTools/pull/712
>>> 
>>> 
>>> # Cleanups
>>> 
>>> - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563
>>> https://github.com/pharo-project/pharo/pull/16563
>>> 
>>> - Cleanup: TestCase class>>#lastRunMethodNamed: #16588
>>> https://github.com/pharo-project/pharo/pull/16588
>>> 
>>> - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest 
>>> and TestCase class>>#hasFailedTest #16586
>>> https://github.com/pharo-project/pharo/pull/16586
>>> 
>>> - Changed 'Transcript show:' construct to 'self trace' #16385
>>> https://github.com/pharo-project/pharo/pull/16385
>>> 
>>> - removing dependency to UIManager in StFuelStackCommand #745
>>> https://github.com/pharo-spec/NewTools/pull/745
>>> 
>>> # Documentation
>>> 
>>> - Update CONTRIBUTING.md #16575
>>> https://github.com/pharo-project/pharo/pull/16575
>> 
>> 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
>> 
>> 
>> 
>> 
>> 
> 

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

[Pharo-dev] Re: This week (19/2024) on the Pharo Issue Tracker

[Marcus Denker]

Only the first issue is for Pharo 12, all the other for Pharo 13.
(the idea is to have just one headline Pharo 12 for all the issues backported)

Marcus

> On 13 May 2024, at 15:31, stephane ducasse  wrote:
> 
> Hi
> 
> I imagine that this is for Pharo 13 
> 
> S
> 
>> On 13 May 2024, at 03:11, Marcus Denker  wrote:
>> 
>> # Pharo 12
>> 
>> - 16576-Problem-with-completion-in-the-tutorial #16582
>>  https://github.com/pharo-project/pharo/pull/16582
>> 
>> 
>> # Virtual Machine
>> 
>> - Bump to MacOS 11 and above #792
>>  https://github.com/pharo-project/pharo-vm/pull/792
>>  
>> - Do not use asserta: in a statement #788
>>  https://github.com/pharo-project/pharo-vm/pull/788
>>  
>> - Moving pharo.signatures files for OSX Bundle to Resources folder #770
>>  https://github.com/pharo-project/pharo-vm/pull/770
>> 
>> 
>> # Features
>> 
>> - New debugger extension model to display dynamic extensions #739
>>  https://github.com/pharo-spec/NewTools/pull/739
>> 
>> - add asAccessor #16579
>>  https://github.com/pharo-project/pharo/pull/16579
>> 
>> - Make it easier to diagnose mock failures by printing message sends 
>> properly and storing the send history in the mock #16555
>>  https://github.com/pharo-project/pharo/pull/16555
>>  
>> - add two's complement display for negative integers #746
>>  https://github.com/pharo-spec/NewTools/pull/746
>> 
>> # Fixes
>> 
>> - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510
>>  https://github.com/pharo-project/pharo/pull/16510
>> 
>> - Taskbar option to close windows hidden behind other windows #16552
>>  https://github.com/pharo-project/pharo/pull/16552
>> 
>> - prof stef lesson view did not understand has binding of #16578
>>  https://github.com/pharo-project/pharo/pull/16578
>> 
>> - fix precedence computation #16581
>>  https://github.com/pharo-project/pharo/pull/16581
>> 
>> # Refactoring Engine
>> 
>> - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600
>>  https://github.com/pharo-project/pharo/pull/16600
>>  
>> - Refactor: preconditions return array of preconditions by default #16527
>>  https://github.com/pharo-project/pharo/pull/16527
>>  
>>  
>> # Rules
>> 
>> - add ReOverridingExtentsionMethod rule #16550
>>  https://github.com/pharo-project/pharo/pull/16550
>>  
>> - add rule to avoid that TestCase rely on Initialize #16513
>>  https://github.com/pharo-project/pharo/pull/16513
>>  
>> # Tests (Green tests on CI)
>> 
>> - Fix testCodeCruftLeftInMethods #16598
>>  https://github.com/pharo-project/pharo/pull/16598
>>  
>> - Update roassal to v1.06d #16595
>>  https://github.com/pharo-project/pharo/pull/16595
>>  
>> - Fixing reflectivity tests that can randomly fail because of unstable and 
>> unpredictable tests generating methods #16584
>>  https://github.com/pharo-project/pharo/pull/16584
>>  
>> - 16569-CI-Pharo13-code-with-halt-was-merged #16570
>>  https://github.com/pharo-project/pharo/pull/16570
>>  
>> - clearing debugger subscriptions and subcomponents in 
>> StDebuggerExtensionMechanismTest>>#tearDown #712
>>  https://github.com/pharo-spec/NewTools/pull/712
>>  
>>  
>> # Cleanups
>> 
>> - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563
>>  https://github.com/pharo-project/pharo/pull/16563
>>  
>> - Cleanup: TestCase class>>#lastRunMethodNamed: #16588
>>  https://github.com/pharo-project/pharo/pull/16588
>>  
>> - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and 
>> TestCase class>>#hasFailedTest #16586
>>  https://github.com/pharo-project/pharo/pull/16586
>>  
>> - Changed 'Transcript show:' construct to 'self trace' #16385
>>  https://github.com/pharo-project/pharo/pull/16385
>>  
>> - removing dependency to UIManager in StFuelStackCommand #745
>>  https://github.com/pharo-spec/NewTools/pull/745
>>  
>> # Documentation
>> 
>> - Update CONTRIBUTING.md #16575
>>  https://github.com/pharo-project/pharo/pull/16575
> 
> 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
> 
> 
> 
> 
> 

[Pharo-dev] Re: This week (19/2024) on the Pharo Issue Tracker

[stephane ducasse]

Hi

I imagine that this is for Pharo 13 

S

> On 13 May 2024, at 03:11, Marcus Denker  wrote:
> 
> # Pharo 12
> 
> - 16576-Problem-with-completion-in-the-tutorial #16582
>   https://github.com/pharo-project/pharo/pull/16582
> 
> 
> # Virtual Machine
> 
> - Bump to MacOS 11 and above #792
>   https://github.com/pharo-project/pharo-vm/pull/792
>   
> - Do not use asserta: in a statement #788
>   https://github.com/pharo-project/pharo-vm/pull/788
>   
> - Moving pharo.signatures files for OSX Bundle to Resources folder #770
>   https://github.com/pharo-project/pharo-vm/pull/770
> 
> 
> # Features
> 
> - New debugger extension model to display dynamic extensions #739
>   https://github.com/pharo-spec/NewTools/pull/739
> 
> - add asAccessor #16579
>   https://github.com/pharo-project/pharo/pull/16579
> 
> - Make it easier to diagnose mock failures by printing message sends properly 
> and storing the send history in the mock #16555
>   https://github.com/pharo-project/pharo/pull/16555
>   
> - add two's complement display for negative integers #746
>   https://github.com/pharo-spec/NewTools/pull/746
> 
> # Fixes
> 
> - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510
>   https://github.com/pharo-project/pharo/pull/16510
> 
> - Taskbar option to close windows hidden behind other windows #16552
>   https://github.com/pharo-project/pharo/pull/16552
> 
> - prof stef lesson view did not understand has binding of #16578
>   https://github.com/pharo-project/pharo/pull/16578
> 
> - fix precedence computation #16581
>   https://github.com/pharo-project/pharo/pull/16581
> 
> # Refactoring Engine
> 
> - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600
>   https://github.com/pharo-project/pharo/pull/16600
>   
> - Refactor: preconditions return array of preconditions by default #16527
>   https://github.com/pharo-project/pharo/pull/16527
>   
>   
> # Rules
> 
> - add ReOverridingExtentsionMethod rule #16550
>   https://github.com/pharo-project/pharo/pull/16550
>   
> - add rule to avoid that TestCase rely on Initialize #16513
>   https://github.com/pharo-project/pharo/pull/16513
>   
> # Tests (Green tests on CI)
> 
> - Fix testCodeCruftLeftInMethods #16598
>   https://github.com/pharo-project/pharo/pull/16598
>   
> - Update roassal to v1.06d #16595
>   https://github.com/pharo-project/pharo/pull/16595
>   
> - Fixing reflectivity tests that can randomly fail because of unstable and 
> unpredictable tests generating methods #16584
>   https://github.com/pharo-project/pharo/pull/16584
>   
> - 16569-CI-Pharo13-code-with-halt-was-merged #16570
>   https://github.com/pharo-project/pharo/pull/16570
>   
> - clearing debugger subscriptions and subcomponents in 
> StDebuggerExtensionMechanismTest>>#tearDown #712
>   https://github.com/pharo-spec/NewTools/pull/712
>   
>   
> # Cleanups
> 
> - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563
>   https://github.com/pharo-project/pharo/pull/16563
>   
> - Cleanup: TestCase class>>#lastRunMethodNamed: #16588
>   https://github.com/pharo-project/pharo/pull/16588
>   
> - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and 
> TestCase class>>#hasFailedTest #16586
>   https://github.com/pharo-project/pharo/pull/16586
>   
> - Changed 'Transcript show:' construct to 'self trace' #16385
>   https://github.com/pharo-project/pharo/pull/16385
>   
> - removing dependency to UIManager in StFuelStackCommand #745
>   https://github.com/pharo-spec/NewTools/pull/745
>   
> # Documentation
> 
> - Update CONTRIBUTING.md #16575
>   https://github.com/pharo-project/pharo/pull/16575

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

[Pharo-dev] Re: IWST Paper Submission Deadline is Approaching!

[Kasper Osterbye]

> Den 13. maj 2024 kl. 09.36 skrev Marcus Denker :
> 
> maybe it is not compatible with all browsers somehow? Here only the old dates 
> are “deleted”:

Fortunately it works now! 

Best,

Kasper

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

[Marcus Denker]

# Pharo 12

- 16576-Problem-with-completion-in-the-tutorial #16582
https://github.com/pharo-project/pharo/pull/16582


# Virtual Machine

- Bump to MacOS 11 and above #792
https://github.com/pharo-project/pharo-vm/pull/792

- Do not use asserta: in a statement #788
https://github.com/pharo-project/pharo-vm/pull/788

- Moving pharo.signatures files for OSX Bundle to Resources folder #770
https://github.com/pharo-project/pharo-vm/pull/770


# Features

- New debugger extension model to display dynamic extensions #739
https://github.com/pharo-spec/NewTools/pull/739

- add asAccessor #16579
https://github.com/pharo-project/pharo/pull/16579

- Make it easier to diagnose mock failures by printing message sends properly 
and storing the send history in the mock #16555
https://github.com/pharo-project/pharo/pull/16555

- add two's complement display for negative integers #746
https://github.com/pharo-spec/NewTools/pull/746

# Fixes

- Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510
https://github.com/pharo-project/pharo/pull/16510

- Taskbar option to close windows hidden behind other windows #16552
https://github.com/pharo-project/pharo/pull/16552

- prof stef lesson view did not understand has binding of #16578
https://github.com/pharo-project/pharo/pull/16578

- fix precedence computation #16581
https://github.com/pharo-project/pharo/pull/16581

# Refactoring Engine

- Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600
https://github.com/pharo-project/pharo/pull/16600

- Refactor: preconditions return array of preconditions by default #16527
https://github.com/pharo-project/pharo/pull/16527


# Rules

- add ReOverridingExtentsionMethod rule #16550
https://github.com/pharo-project/pharo/pull/16550

- add rule to avoid that TestCase rely on Initialize #16513
https://github.com/pharo-project/pharo/pull/16513

# Tests (Green tests on CI)

- Fix testCodeCruftLeftInMethods #16598
https://github.com/pharo-project/pharo/pull/16598

- Update roassal to v1.06d #16595
https://github.com/pharo-project/pharo/pull/16595

- Fixing reflectivity tests that can randomly fail because of unstable and 
unpredictable tests generating methods #16584
https://github.com/pharo-project/pharo/pull/16584

- 16569-CI-Pharo13-code-with-halt-was-merged #16570
https://github.com/pharo-project/pharo/pull/16570

- clearing debugger subscriptions and subcomponents in 
StDebuggerExtensionMechanismTest>>#tearDown #712
https://github.com/pharo-spec/NewTools/pull/712


# Cleanups

- Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563
https://github.com/pharo-project/pharo/pull/16563

- Cleanup: TestCase class>>#lastRunMethodNamed: #16588
https://github.com/pharo-project/pharo/pull/16588

- Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and 
TestCase class>>#hasFailedTest #16586
https://github.com/pharo-project/pharo/pull/16586

- Changed 'Transcript show:' construct to 'self trace' #16385
https://github.com/pharo-project/pharo/pull/16385

- removing dependency to UIManager in StFuelStackCommand #745
https://github.com/pharo-spec/NewTools/pull/745

# Documentation

- Update CONTRIBUTING.md #16575
https://github.com/pharo-project/pharo/pull/16575

[Pharo-dev] IWST Paper Submission Deadline is Approaching!

[Guillermo Polito]

Dear community,

IWST invites everybody to submit full/short papers to be considered to be 
plublished in the IWST 2024 Proceedings.
Papers can both be presented in the conference's IWST track and appear in 
proceedings independently of the initially submitted abstracts.

Full/short paper submission deadline: May 19th, 2024

We are looking for papers of two kinds:

- Short position papers (5 to 10 pages) describing fresh ideas and early 
results.
- Full papers (more than 10 pages) with deeper description of experiments and 
of research results.

Paper accepted for publishing will be published within a *CEUR-WS 
Proceedings>https://ceur-ws.org/*.
Hence, both submissions and final papers must be prepared using the *CEUR ART 
style>https://ceur-ws.org/Vol-XXX/CEURART.zip*. 
We recommend to use the template in single column style, although you may use 
two colums.
CEUR proceedings accepts papers in boths styles as soon as they follow the 
template and have 5 or more pages.

The IWST team, Gordana, Guille and Steven
https://esug.org/2024-Conference/IWST2024.html

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

[Yanni Chiu]

I know. I was implying that Soil might be more than just bits of that
stone. By being soil, it can be a fertile ground for ideas.

On Wed, May 8, 2024 at 5:41 PM Dale Henrichs <
dale.henri...@gemtalksystems.com> wrote:

> But ground stone is just sand. There’s more than just sand in soil. Soil
>> should have the other ingredients needed for growth. :)
>
> I was trying to make a reference to a GemStone *stone *:)
>
> Dale
>
> On Wed, May 8, 2024 at 1:27 PM Norbert Hartl  wrote:
>
>>
>>
>> Am 08.05.2024 um 16:14 schrieb Norbert Hartl :
>>
>> 
>>
>> Am 06.05.2024 um 16:47 schrieb Dirk Nel :
>>
>> I'll definitely check it out..! and for those who are not in the know...
>> what inspired the name? :)
>>
>>
>> - I like the word
>> - It has only four letters which qualifies as a class prefix
>> - To me as a non-native speaker it means: ground layer you can build/grow
>> on
>>
>> - people having fun with it
>>
>> Mission accomplished
>>
>> N.
>>
>>
>> Norbert
>>
>>
>> On Wed, 24 Apr 2024 at 17:47, Tim Mackinnon  wrote:
>>
>>> 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 . 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-l...@lists.esug.org
>>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>>
>>>
>>> ___
>>> Esug-list mailing list -- esug-l...@lists.esug.org
>>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>>
>>
>> ___
>> Esug-list mailing list -- esug-l...@lists.esug.org
>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>
>> ___
>> Esug-list mailing list -- esug-l...@lists.esug.org
>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>
>

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

[Dale Henrichs]

>
> But ground stone is just sand. There’s more than just sand in soil. Soil
> should have the other ingredients needed for growth. :)

I was trying to make a reference to a GemStone *stone *:)

Dale

On Wed, May 8, 2024 at 1:27 PM Norbert Hartl  wrote:

>
>
> Am 08.05.2024 um 16:14 schrieb Norbert Hartl :
>
> 
>
> Am 06.05.2024 um 16:47 schrieb Dirk Nel :
>
> I'll definitely check it out..! and for those who are not in the know...
> what inspired the name? :)
>
>
> - I like the word
> - It has only four letters which qualifies as a class prefix
> - To me as a non-native speaker it means: ground layer you can build/grow
> on
>
> - people having fun with it
>
> Mission accomplished
>
> N.
>
>
> Norbert
>
>
> On Wed, 24 Apr 2024 at 17:47, Tim Mackinnon  wrote:
>
>> 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 . 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-l...@lists.esug.org
>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>
>>
>> ___
>> Esug-list mailing list -- esug-l...@lists.esug.org
>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>
>
> ___
> Esug-list mailing list -- esug-l...@lists.esug.org
> To unsubscribe send an email to esug-list-le...@lists.esug.org
>
> ___
> Esug-list mailing list -- esug-l...@lists.esug.org
> To unsubscribe send an email to esug-list-le...@lists.esug.org
>

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

[Norbert Hartl]

Am 08.05.2024 um 16:14 schrieb Norbert Hartl :Am 06.05.2024 um 16:47 schrieb Dirk Nel :I'll definitely check it out..! and for those who are not in the know... what inspired the name? :)- I like the word- It has only four letters which qualifies as a class prefix- To me as a non-native speaker it means: ground layer you can build/grow on- people having fun with itMission accomplishedN.NorbertOn Wed, 24 Apr 2024 at 17:47, Tim Mackinnon  wrote: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.TimOn 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. 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/SoilThis 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-l...@lists.esug.orgTo unsubscribe send an email to esug-list-le...@lists.esug.org___
Esug-list mailing list -- esug-l...@lists.esug.org
To unsubscribe send an email to esug-list-le...@lists.esug.org

___Esug-list mailing list -- esug-l...@lists.esug.orgTo unsubscribe send an email to esug-list-le...@lists.esug.org

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

[Yanni Chiu]

But ground stone is just sand. There’s more than just sand in soil. Soil
should have the other ingredients needed for growth. :)

On Wed, May 8, 2024 at 11:41 AM Dale Henrichs <
dale.henri...@gemtalksystems.com> wrote:

> To me as a non-native speaker it means: ground layer you can build/grow on
>
>
> Haha, Soil can also be thought of as "ground up stone" :)
>
> Dale
>
> On Wed, May 8, 2024 at 7:13 AM Norbert Hartl  wrote:
>
>>
>>
>> Am 06.05.2024 um 16:47 schrieb Dirk Nel :
>>
>> I'll definitely check it out..! and for those who are not in the know...
>> what inspired the name? :)
>>
>>
>> - I like the word
>> - It has only four letters which qualifies as a class prefix
>> - To me as a non-native speaker it means: ground layer you can build/grow
>> on
>>
>> Norbert
>>
>

[Pharo-dev] Re: [Pharo-users] Re: [Esug-list] Re: [ANN] Soil release v1

[Sabine M]

I am always thinking of this movie when hearing „Soil“. Googling for it now, I 
see that it has another spelling.

https://en.wikipedia.org/wiki/Soylent_Green

Gesendet von Outlook für iOS<https://aka.ms/o0ukef>

Von: Cody Sevier 
Gesendet: Wednesday, May 8, 2024 5:43:24 PM
An: Any question about pharo is welcome 
Cc: Norbert Hartl ; Dirk Nel ; 
Pharo Dev ; Tetaz, Jean-Pierre via Esug-list 

Betreff: [Pharo-users] Re: [Esug-list] Re: [ANN] Soil release v1

Or soiling yourself, aka incontinence... Isn't English illogical fun!

Cody

On Wed, May 8, 2024, 10:41 AM Dale Henrichs 
mailto:dale.henri...@gemtalksystems.com>> 
wrote:
To me as a non-native speaker it means: ground layer you can build/grow on

Haha, Soil can also be thought of as "ground up stone" :)

Dale

On Wed, May 8, 2024 at 7:13 AM Norbert Hartl 
mailto:norb...@hartl.name>> wrote:


Am 06.05.2024 um 16:47 schrieb Dirk Nel 
mailto:dirkockert...@gmail.com>>:

I'll definitely check it out..! and for those who are not in the know... what 
inspired the name? :)

- I like the word
- It has only four letters which qualifies as a class prefix
- To me as a non-native speaker it means: ground layer you can build/grow on

Norbert


On Wed, 24 Apr 2024 at 17:47, Tim Mackinnon  wrote:
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-l...@lists.esug.org<mailto:esug-l...@lists.esug.org>
To unsubscribe send an email to 
esug-list-le...@lists.esug.org<mailto:esug-list-le...@lists.esug.org>


___
Esug-list mailing list -- 
esug-l...@lists.esug.org<mailto:esug-l...@lists.esug.org>
To unsubscribe send an email to 
esug-list-le...@lists.esug.org<mailto:esug-list-le...@lists.esug.org>

___
Esug-list mailing list -- 
esug-l...@lists.esug.org<mailto:esug-l...@lists.esug.org>
To unsubscribe send an email to 
esug-list-le...@lists.esug.org<mailto:esug-list-le...@lists.esug.org>

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

[Dale Henrichs]

>
> To me as a non-native speaker it means: ground layer you can build/grow on


Haha, Soil can also be thought of as "ground up stone" :)

Dale

On Wed, May 8, 2024 at 7:13 AM Norbert Hartl  wrote:

>
>
> Am 06.05.2024 um 16:47 schrieb Dirk Nel :
>
> I'll definitely check it out..! and for those who are not in the know...
> what inspired the name? :)
>
>
> - I like the word
> - It has only four letters which qualifies as a class prefix
> - To me as a non-native speaker it means: ground layer you can build/grow
> on
>
> Norbert
>
>
> On Wed, 24 Apr 2024 at 17:47, Tim Mackinnon  wrote:
>
>> 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 . 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-l...@lists.esug.org
>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>
>>
>> ___
>> Esug-list mailing list -- esug-l...@lists.esug.org
>> To unsubscribe send an email to esug-list-le...@lists.esug.org
>>
>
> ___
> Esug-list mailing list -- esug-l...@lists.esug.org
> To unsubscribe send an email to esug-list-le...@lists.esug.org
>

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

[Norbert Hartl]

> Am 06.05.2024 um 16:47 schrieb Dirk Nel :
> 
> I'll definitely check it out..! and for those who are not in the know... what 
> inspired the name? :)

- I like the word
- It has only four letters which qualifies as a class prefix
- To me as a non-native speaker it means: ground layer you can build/grow on

Norbert

> 
> On Wed, 24 Apr 2024 at 17:47, Tim Mackinnon  wrote:
>> 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 . 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-l...@lists.esug.org 
>>> 
>>> To unsubscribe send an email to esug-list-le...@lists.esug.org 
>>> 
>>> 
>> 
>> ___
>> Esug-list mailing list -- esug-l...@lists.esug.org 
>> 
>> To unsubscribe send an email to esug-list-le...@lists.esug.org 
>> 

[Pharo-dev] Some issues in starting Pharo12 - Re: [Pharo-users] [ANN] Pharo 12 Release !

[Davide Varvello via Pharo-dev]

 Hi Guys,
I'm trying to play with Pharo12 so I downloaded it via the Zeroconf script (it 
seems to me more approachable than the Pharo Launcher).The script (curl -L 
https://get.pharo.org | bash) got everything for my machine (apple silicon). 
Now, if I run pharo via command line everything is working, but if I double 
click on Pharo.app and select the image file Pharo.image nothing happens.
Can you check that behavior, please?
TIADavide
-
On Friday, April 26, 2024 at 12:20:41 PM GMT+2, Esteban Lorenzano via 
Pharo-users  wrote:  
 
   
Dear Pharo users and dynamic language lovers:
 
We have released Pharo version 12!
 
What is Pharo?


 

 

   

[Pharo-dev] "Atlas is a Spec application" — New blog post on all: objects all: theTime

[Koen De Hondt]

Dear Pharo users and developers,

I added the next blog post  
to the series on Atlas, a new browser for Pharo. It describes the relationship 
between Atlas and Spec, the UI framework of Pharo. The blog post introduces the 
basic building blocks of the Atlas UI. It also explains the struggle with some 
aspects of Spec and the Morphic backend.

Happy reading!

Ciao,
Koen

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

[Marcus Denker]

With Pharo12 being released, we started to merge more changes in Pharo13.


# Pharo12 

- Pharo12: ProcessorScheduler>>#activeProcess added no instrumentation pragma 
#16557
https://github.com/pharo-project/pharo/pull/16557

- Add Toplo world menu entry (part 2) #16478
https://github.com/pharo-project/pharo/pull/16478


# Graphics

- Change default value for setting #autoSetCanvasScaleFactor to true #16529
https://github.com/pharo-project/pharo/pull/16529

- missing stroke paint method #16531
https://github.com/pharo-project/pharo/pull/16531

- Change #shrinkTo: on FreeTypeCache to selectively remove entries rather than 
all of them #16419
https://github.com/pharo-project/pharo/pull/16419


# Bugs

- ExteranlAddress>>fromString: converts string to UTF-8 first #16560
https://github.com/pharo-project/pharo/pull/16560


- ProcessorScheduler>>#activeProcess added no instrumentation pragma #16551
https://github.com/pharo-project/pharo/pull/16551


# Refactoring Engine

- Refactoring of the RefactoryChange manager #16526
https://github.com/pharo-project/pharo/pull/16526

- Composite extract method refactoring #16525
https://github.com/pharo-project/pharo/pull/16525


# Speed

- Announcer: Return early if there isn't any subscriber #16336
https://github.com/pharo-project/pharo/pull/16336

# Cleanup / Misc

- New pass at removing SystemAnnouncer references #16518
https://github.com/pharo-project/pharo/pull/16518

- update with latest changes from Pharo12 #16523
https://github.com/pharo-project/pharo/pull/16523

- remove interactionState: #16559
https://github.com/pharo-project/pharo/pull/16559

- the tests use #category: from the package Deprecated12 #743
https://github.com/pharo-spec/NewTools/pull/743



# Tests
- add tests for testDoWhileFalse: and testDoWhileTrue: #16532
https://github.com/pharo-project/pharo/pull/16532

- 5 test for rules #16524
https://github.com/pharo-project/pharo/pull/16524

[Pharo-dev] [Success Story] Support Wizard by Thales

[Marcus Denker]

 Support Wizard by Thales
===

Support Wizard is an application developped by Pierre Laborde and Eric Le Pors, 
Global Design and Innovation Leaders at Thales. It is using the latest 
technological innovations from Pharo to create native and high-performance 
desktop human-machine interfaces (Bloc graphics engine, Toplo libraries and OS 
tools). The application is structured with the open-source component 
architecture framework Molecule. The simplicity and speed of production offered 
by Pharo and the power of its language allows Thales to focus our efforts on 
ergonomics and graphic design of the application to offer the best possible 
user experience.




Link (with more infos):
https://www.pharo.org/success/Thales-SupportWizard.html

Youtube Video: 
https://www.youtube.com/watch?v=t5qaFM2F3J0

[Pharo-dev] Re: [ANN] Pharo 12 Release !

[Miloslav.Raus--- via Pharo-dev]

Wow, impressive improvements!

Seems like „soon“ Bloc and Gtk could be on the same footing, and FFI 
improvements „never hurt anybody“.

The rest of the list is no less spectacular.
Probably more spectacular, but I’m constrained by platform requirements, so I 
can’t use interesting languages to „further the cause of evil“, so anything 
that smells like „better integration“ gives me shivers.

Thanks to everyone involved, keep on rocking ;-)

From: Esteban Lorenzano via Pharo-dev 
Sent: Friday, April 26, 2024 12:20 PM
To: pharo-dev@lists.pharo.org; pharo-us...@lists.pharo.org
Cc: Esteban Lorenzano 
Subject: [Pharo-dev] [ANN] Pharo 12 Release !


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.

[https://pharo.org/news/Pharo12.png]

  *   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/Pharo120ChangeLogs.md>

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.

[https://pharo.org/news/Pharo12DebugPoints.png]

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>

[Pharo-dev] Re: [Esug-list] [ANN] Pharo 12 released !

[stephane ducasse]

Thanks to all the team and contributors for this cool release. 

S

> On 26 Apr 2024, at 12:18, Esteban Lorenzano  wrote:
> 
> Dear Pharo users and dynamic language lovers:
> 
> We have released Pharo  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 
>  License and available on GitHub 
> 
> ... more on the Pharo Features page .
> 
> 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 
> 
> 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 
> http://github.com/pharo-spec/NewTools-DocumentBrowser 
> 
> http://github.com/pharo-spec/Spec 
> http://github.com/pharo-vcs/Iceberg 
> http://github.com/ObjectProfile/Roassal3 
> 
> http://github.com/pillar-markup/Microdown 
> 
> http://github.com/pillar-markup/BeautifulComments 
> 
> http://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 
> Learn Pharo: 

[Pharo-dev] Re: [ANN] Pharo 12 Release !

[stephane ducasse]

Yes we should do one!

S. 

> On 26 Apr 2024, at 21:54, Denis Kudriashov  wrote:
> 
> Congrats!!! 
> 
> Have a good release party :))
> 
> пт, 26 апр. 2024 г. в 11:20, Esteban Lorenzano via Pharo-dev 
> mailto:pharo-dev@lists.pharo.org>>:
>> 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/Pharo120ChangeLogs.md>
>> 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>
>> 

[Pharo-dev] Re: [ANN] Pharo 12 Release !

[Denis Kudriashov]

Congrats!!!

Have a good release party :))

пт, 26 апр. 2024 г. в 11:20, Esteban Lorenzano via Pharo-dev <
pharo-dev@lists.pharo.org>:

> 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/Pharo120ChangeLogs.md>
>
> 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 b

[Pharo-dev] Re: [ANN] Pharo 12 Release !

[Privat, Jean]

Congratulation ! It's an impressive piece of work.

-- 

Jean PRIVAT, professeur
Département d'informatique
UQAM

Bureau: PK-4830
Web: http://info.uqam.ca/~privat/

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

[Marcus Denker]

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 go there and 
we back-port important fixes.


# Pharo 12 Release fixes

- Release waiting processes when destroying a socket (without ThreadedFFI 
dependency) #16172
https://github.com/pharo-project/pharo/pull/16172

- P12 external projects fix repository versions #16509
https://github.com/pharo-project/pharo/pull/16509

- Adding a Calypso class to display the Debug Points menu group in the method 
list context menu #16507
https://github.com/pharo-project/pharo/pull/16507

- FFI_i386>>#newCallbackArgumentReaderForCallback:inContext: into "callbacks" 
like any other #16505
https://github.com/pharo-project/pharo/pull/16505

- Clean System-Announcements-Tests #16503
https://github.com/pharo-project/pharo/pull/16503

- Athens Demo not working #16502
https://github.com/pharo-project/pharo/pull/16502

- Remove some users of SystemAnnoucer class>>#uniqueInstance #16498
https://github.com/pharo-project/pharo/pull/16498

- Remove calypso context from search dialogs #16493
https://github.com/pharo-project/pharo/pull/16493

- Revert "Fix for Wrong focus in Calypso Find Class Dialog causes exception" 
#16492
https://github.com/pharo-project/pharo/pull/16492

- Changed the description when trying to delete a class. #16491
https://github.com/pharo-project/pharo/pull/16491

- Issue 16462: Find and replace setup is quadruplicated in the context menu 
#16490
https://github.com/pharo-project/pharo/pull/16490

- Fix 16345: serialization of classes with traits in hierarchy #16487
https://github.com/pharo-project/pharo/pull/16487

- During compilation there are redundant allocation of collections #16486
https://github.com/pharo-project/pharo/pull/16486

- fixes #16362: Abstract instance variables DNU #16482
https://github.com/pharo-project/pharo/pull/16482

- Add setting to set the world renderer canvas scale factor automatically #16479
https://github.com/pharo-project/pharo/pull/16479

- Font-Tests: #testIsAbstractClass should be testIsAbstract like in oth… #16477
https://github.com/pharo-project/pharo/pull/16477

- Added the compare methods to all the byte array classes so they use the new 
primitiveCompareBytes #16461
https://github.com/pharo-project/pharo/pull/16461

- Fix: rename method loop #16444
https://github.com/pharo-project/pharo/pull/16444

# Pharo 13

- P13 use branch repository #16519
https://github.com/pharo-project/pharo/pull/16519

- add Open as external window option #16511
https://github.com/pharo-project/pharo/pull/16511

- Add rule for Point x: x y: y -> x@y #16508
https://github.com/pharo-project/pharo/pull/16508

- Rename SqueakEpoch to Epoch #16418
https://github.com/pharo-project/pharo/pull/16418

[Pharo-dev] Re: [ANN] Pharo 12 Release !

[Sven Van Caekenberghe]

Great work!

> On 26 Apr 2024, at 12:19, Esteban Lorenzano via Pharo-dev 
>  wrote:
> 
> Dear Pharo users and dynamic language lovers:
> We have released Pharo 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 License and 
> available on GitHub
> ... more on the Pharo Features page.
> 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
> 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
> • http://github.com/pharo-spec/NewTools-DocumentBrowser
> • http://github.com/pharo-spec/Spec
> • http://github.com/pharo-vcs/Iceberg
> • http://github.com/ObjectProfile/Roassal3
> • http://github.com/pillar-markup/Microdown
> • http://github.com/pillar-markup/BeautifulComments
> • http://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
> Learn Pharo: http://pharo.org/documentation
> 
> 

[Pharo-dev] Re: [Pharo-users] [ANN] Pharo 12 Release !

[Koen De Hondt]

That is great news. Congratulations!

Koen

> On 26 Apr 2024, at 12:19, Esteban Lorenzano via Pharo-users 
>  wrote:
> 
> Dear Pharo users and dynamic language lovers:
> 
> We have released Pharo  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 
>  License and available on GitHub 
> 
> ... more on the Pharo Features page .
> 
> 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 
> 
> 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 
> http://github.com/pharo-spec/NewTools-DocumentBrowser 
> 
> http://github.com/pharo-spec/Spec 
> http://github.com/pharo-vcs/Iceberg 
> http://github.com/ObjectProfile/Roassal3 
> 
> http://github.com/pillar-markup/Microdown 
> 
> http://github.com/pillar-markup/BeautifulComments 
> 
> http://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 
> Learn Pharo: 

[Pharo-dev] Re: [Esug-list] [ANN] Pharo 12 released !

[Norbert Hartl]

Congratulation once again for this new release. Can‘t wait to put my hands onto it.NorbertAm 26.04.2024 um 12:19 schrieb Esteban Lorenzano :

  


  
  
Dear Pharo users and dynamic language lovers:
We have released Pharo 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 License and
available on GitHub

... more on the Pharo
Features page.
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
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
  http://github.com/pharo-spec/NewTools-DocumentBrowser
  http://github.com/pharo-spec/Spec
  http://github.com/pharo-vcs/Iceberg
  http://github.com/ObjectProfile/Roassal3
  http://github.com/pillar-markup/Microdown
  http://github.com/pillar-markup/BeautifulComments
  http://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
Learn Pharo: http://pharo.org/documentation

  

___Esug-list mailing list -- esug-l...@lists.esug.orgTo unsubscribe send an email to esug-list-le...@lists.esug.org

[Pharo-dev] [ANN] Pharo 12 Release !

[Esteban Lorenzano via Pharo-dev]

Dear Pharo users and dynamic language lovers:

We have released Pharo  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
    License and available on
   GitHub 

... more on the Pharo Features page .

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 



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
   
 * http://github.com/pharo-spec/NewTools-DocumentBrowser
   
 * http://github.com/pharo-spec/Spec 
 * http://github.com/pharo-vcs/Iceberg
   
 * http://github.com/ObjectProfile/Roassal3
   
 * http://github.com/pillar-markup/Microdown
   
 * http://github.com/pillar-markup/BeautifulComments
   
 * http://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 

Learn Pharo: http://pharo.org/documentation 

[Pharo-dev] Re: [ANN] Soil release v1

[Norbert Hartl]

Hi,Am 24.04.2024 um 19:28 schrieb Miloslav.Raus--- via Pharo-dev :







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 ?I have trouble understanding what you mean. Can you elaborate on that?You mean multiple open databases on the same data on different images? As long as you don‘t use indexes it should work. But I think this is only a good option in very rare cases.Norbert
 


From: Norbert Hartl 

Sent: Wednesday, April 24, 2024 1:53 PM
To: Pharo users users ; Pharo Dev ; ESUG 
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. 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

[Pharo-dev] Re: [ANN] Soil release v1

[Miloslav.Raus--- via Pharo-dev]

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 
Sent: Wednesday, April 24, 2024 1:53 PM
To: Pharo users users ; Pharo Dev 
; ESUG 
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

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

[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 . 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-l...@lists.esug.org
> To unsubscribe send an email to esug-list-le...@lists.esug.org
> 

[Pharo-dev] [ANN] Soil release v1

[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 . 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

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

[Miloslav.Raus--- via Pharo-dev]

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 
Sent: Friday, April 19, 2024 9:16 PM
To: Pharo Development List 
Cc: Rauš Miloslav ; Esteban Lorenzano 

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

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

[Noury Bouraqadi]

Thank you !

On Apr 23 2024, at 11:01 am, Marcus Denker  wrote:
> 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 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

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

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

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

[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

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

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

[Pharo-dev] Re: Will there be a new PharoLauncher (with [somewhat] current VM) for the 12.0 Release ?

[Christophe Demarey]

Hi Miroslav,

Indeed a Pharo Launcher release is on the way.
It will be available soon.

Regards,
Christophe.

> Le 18 avr. 2024 à 13:37, Miloslav.Raus--- via Pharo-dev 
>  a écrit :
> 
> Hi.
>  
> The official launcher (from Downloads page) is dated-a-f. (For example won’t 
> repaint when alt-tabbed to, unless some ).
> The latest release from github also wasn’t satisfactory (but IDK exactly how).
>  
> I’m currently using a contemporary image/vm with master PharoLauncher, and 
> the experience seems the best.
>  
> If at all possible, new official Launcher release (based on P11 or P12) would 
> be welcome.
>  
> Thanks (but no expectations / pressure),
>   M.R.

[Pharo-dev] [P12 nearing realease] dark theme problems (wrt. code snippets)

[Miloslav.Raus--- via Pharo-dev]

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.

[Pharo-dev] Will there be a new PharoLauncher (with [somewhat] current VM) for the 12.0 Release ?

[Miloslav.Raus--- via Pharo-dev]

Hi.

The official launcher (from Downloads page) is dated-a-f. (For example won't 
repaint when alt-tabbed to, unless some ).
The latest release from github also wasn't satisfactory (but IDK exactly how).

I'm currently using a contemporary image/vm with master PharoLauncher, and the 
experience seems the best.

If at all possible, new official Launcher release (based on P11 or P12) would 
be welcome.

Thanks (but no expectations / pressure),
  M.R.

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

[Noury Bouraqadi]

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

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

[Marcus Denker]

# 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

- Remove async playground doits #735
https://github.com/pharo-spec/NewTools/pull/735

- Fix issue while trying to display file setting items #736
https://github.com/pharo-spec/NewTools/pull/736

- quick fix that hide the debug context menus when there are unsaved changes 
#16382
https://github.com/pharo-project/pharo/pull/16382

- Fix Generate Equals and Hash DNU #16384
https://github.com/pharo-project/pharo/pull/16384

- Fix for Wrong focus in Calypso Find Class Dialog causes exception #16386
https://github.com/pharo-project/pharo/pull/16386

- Provide a default String for settings without #default: sends. #16400
https://github.com/pharo-project/pharo/pull/16400

- fix MethodConstantTest #16405
https://github.com/pharo-project/pharo/pull/16405

- fix enum type initialization on structures #16406
https://github.com/pharo-project/pharo/pull/16406

- Do not suggest trait when deprecating a class #16409
https://github.com/pharo-project/pharo/pull/16409

- 16366 Insert superclass refactoring is allowed on trait and gives DNU #16413
https://github.com/pharo-project/pharo/pull/16413

- 
16423-Scrolling-always-acts-as-if-macOS-option-Use-inertia-when-scrolling-is-turned-off
 #16426
https://github.com/pharo-project/pharo/pull/16426

- Fix Refactorings should have help menus to explain their actions #16421
https://github.com/pharo-project/pharo/pull/16421

- Reposition Calypso contextual class menu items #16420
https://github.com/pharo-project/pharo/pull/16420

# Improvements

- Add support for Epicea file out #16401
https://github.com/pharo-project/pharo/pull/16401

- Add Toplo world menu entry #16429
https://github.com/pharo-project/pharo/pull/16429


# UI

- Exclude some commands from virtual method groups on Calypso #16404
https://github.com/pharo-project/pharo/pull/16404

- fix enter/escape behavior on dialogs #1537
https://github.com/pharo-spec/Spec/pull/1537

- Improving the behavior in all the dialogs #1536
https://github.com/pharo-spec/Spec/pull/1536

- Fix selection bug in SpFilteringSelectableListPresenter #1535
https://github.com/pharo-spec/Spec/pull/1535

- fix: SpSelectDialog should select the first item #1530 #1534
https://github.com/pharo-spec/Spec/pull/1534

- Improve SpSelectDialog for handling line splitting texts #1533
https://github.com/pharo-spec/Spec/pull/1533

- Cleanup/remove rename default spec to default layout refactoring #1515
https://github.com/pharo-spec/Spec/pull/1515

# Cleanups  

- moved to Spec2-Transmission package #1538
https://github.com/pharo-spec/Spec/pull/1538

- Use #setUp instead of #initialize for test cases #16417
https://github.com/pharo-project/pharo/pull/16417

- Remove CharacterTable #16416
https://github.com/pharo-project/pharo/pull/16416

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

[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

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

[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

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

[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

[Pharo-dev] Re: "The Classification Model" — New blog post on all: objects all: theTime

[Tim Mackinnon]

By the way - it's a shame there is no rss feed for you blog as I like to use a 
feed reader on my phone to keep up with such things. Not sure what you are 
using, but if you could enable it, that would be coo.

Tim

On Tue, 19 Mar 2024, at 4:30 PM, Tim Mackinnon wrote:
> Hi Koen - is there any particular place you would like us to feedback on the 
> posts? Is here useful, or some other location?
> 
> I like the concepts you are introducing (I need to take to read your PHD - so 
> good to have the link in there) - but the devil is in the detail of course.
> 
> If I have understood correctly - the idea of computed classifications give 
> rise to the flexibility we all crave?  So in my previous comment - when 
> designing a new class and trying to work out its protocol, in particular how 
> to instantiate it vs. update it - its very inconvenient to have to flip 
> between class and instance method definitions - a much flatter view of a 
> Class has both instance AND class methods that I can see together is more 
> efficient to work with in that initial design phase vs later when stabilised 
> the more traditional - a Class name has Class and Instance definition, a 
> Class definition has class methods, an Instance definition has instance 
> methods (apologies if terminology isn't quite right - typing this in a hurry 
> on a break). 
> 
> But does the classification model handle the above? To flatten instance and 
> class methods into a single sorted list (discriminated in some manner - like 
> one being bold or having some prefix) and also allowing you to add to add new 
> items to that list and provide that discrimination sounds like it might not 
> fit that classification model? Or maybe it does? I guess we do currently 
> allow methods to have categories and we can view multiple categories in a 
> list.  I guess I'm curious how it hangs together to model non-trivial 
> examples? And maybe this is the next blog post?
> 
> Thanks for surfacing the ideas.
> 
> Tim
> 
> On Mon, 18 Mar 2024, at 5:51 PM, Koen De Hondt wrote:
>> Dear Pharo users and developers,
>> 
>> Last week I told you about a new blog post that outlined the objectives of 
>> the Atlas browser. It was the first post of a series.
>> If you liked it, I invite you to read the next post 
>> . It describes the 
>> Classification Model, which is the foundation of Atlas.
>> 
>> Happy reading!
>> 
>> Ciao,
>> Koen
> 

[Pharo-dev] Re: "The Classification Model" — New blog post on all: objects all: theTime

[Koen De Hondt]

Hi Tim,

This is a good place to discuss. I did not add comment functionality to my blog 
because I do not want people to spam the site with stuff that is not related to 
the content, and I do not want to moderate the comments. Sending me messages is 
fine too, but here everyone can read along.

You have understood correctly, but I consider it a virtual classification 
rather than a computed classification because the classification does not 
depend on user input. Atlas has an “AllMethodsClassification” that holds items 
for all methods of a class. It is used for instance methods and class methods, 
depending on the “source” of the classification, either a class or a metaclass.
Suppose you implement a new classification, let’s say 
“AllInstanceMethodsAndClassMethodsClassification”, that holds items for all 
instance methods and class methods of a class, then you are all set.

All items and classifications have a display name, which is shown in the UI. 
However, the display name depends on the context. If it is clear from the 
context that #example is a class method, then displaying “example” is fine. 
However, when the context is more general, like any manual classification that 
can hold anything, displaying “My class>>#example” would be more appropriate. 
So just implementing a new kind of classification would not be enough for your 
use case. Therefore I would also implement a dedicated view on that 
classification so that the list in the view can indicate whether a method is an 
instance or a class method, together with the protocol it belongs to.

An alternative to what you propose, and a better solution in my opinion, is to 
have two views side by side, so that instance and class methods are not mixed. 
That simplifies the implementation, certainly because Atlas has both views, and 
composing your own browser is possible. That is certainly a topic for a future 
post.

Thank you for your questions. I welcome all feedback, as it will shape Atlas.

Ciao,
Koen

> On 19 Mar 2024, at 17:30, Tim Mackinnon  wrote:
> 
> Hi Koen - is there any particular place you would like us to feedback on the 
> posts? Is here useful, or some other location?
> 
> I like the concepts you are introducing (I need to take to read your PHD - so 
> good to have the link in there) - but the devil is in the detail of course.
> 
> If I have understood correctly - the idea of computed classifications give 
> rise to the flexibility we all crave?  So in my previous comment - when 
> designing a new class and trying to work out its protocol, in particular how 
> to instantiate it vs. update it - its very inconvenient to have to flip 
> between class and instance method definitions - a much flatter view of a 
> Class has both instance AND class methods that I can see together is more 
> efficient to work with in that initial design phase vs later when stabilised 
> the more traditional - a Class name has Class and Instance definition, a 
> Class definition has class methods, an Instance definition has instance 
> methods (apologies if terminology isn't quite right - typing this in a hurry 
> on a break). 
> 
> But does the classification model handle the above? To flatten instance and 
> class methods into a single sorted list (discriminated in some manner - like 
> one being bold or having some prefix) and also allowing you to add to add new 
> items to that list and provide that discrimination sounds like it might not 
> fit that classification model? Or maybe it does? I guess we do currently 
> allow methods to have categories and we can view multiple categories in a 
> list.  I guess I'm curious how it hangs together to model non-trivial 
> examples? And maybe this is the next blog post?
> 
> Thanks for surfacing the ideas.
> 
> Tim
> 
> On Mon, 18 Mar 2024, at 5:51 PM, Koen De Hondt wrote:
>> Dear Pharo users and developers,
>> 
>> Last week I told you about a new blog post that outlined the objectives of 
>> the Atlas browser. It was the first post of a series.
>> If you liked it, I invite you to read the next post 
>> . It describes the 
>> Classification Model, which is the foundation of Atlas.
>> 
>> Happy reading!
>> 
>> Ciao,
>> Koen

[Pharo-dev] Re: "The Classification Model" — New blog post on all: objects all: theTime

[Tim Mackinnon]

Hi Koen - is there any particular place you would like us to feedback on the 
posts? Is here useful, or some other location?

I like the concepts you are introducing (I need to take to read your PHD - so 
good to have the link in there) - but the devil is in the detail of course.

If I have understood correctly - the idea of computed classifications give rise 
to the flexibility we all crave?  So in my previous comment - when designing a 
new class and trying to work out its protocol, in particular how to instantiate 
it vs. update it - its very inconvenient to have to flip between class and 
instance method definitions - a much flatter view of a Class has both instance 
AND class methods that I can see together is more efficient to work with in 
that initial design phase vs later when stabilised the more traditional - a 
Class name has Class and Instance definition, a Class definition has class 
methods, an Instance definition has instance methods (apologies if terminology 
isn't quite right - typing this in a hurry on a break). 

But does the classification model handle the above? To flatten instance and 
class methods into a single sorted list (discriminated in some manner - like 
one being bold or having some prefix) and also allowing you to add to add new 
items to that list and provide that discrimination sounds like it might not fit 
that classification model? Or maybe it does? I guess we do currently allow 
methods to have categories and we can view multiple categories in a list.  I 
guess I'm curious how it hangs together to model non-trivial examples? And 
maybe this is the next blog post?

Thanks for surfacing the ideas.

Tim

On Mon, 18 Mar 2024, at 5:51 PM, Koen De Hondt wrote:
> Dear Pharo users and developers,
> 
> Last week I told you about a new blog post that outlined the objectives of 
> the Atlas browser. It was the first post of a series.
> If you liked it, I invite you to read the next post 
> . It describes the 
> Classification Model, which is the foundation of Atlas.
> 
> Happy reading!
> 
> Ciao,
> Koen

[Pharo-dev] Re: "The Classification Model" — New blog post on all: objects all: theTime

[Noury Bouraqadi]

It sounds promising. I want it now ;-)

Noury
On Mar 18 2024, at 6:51 pm, Koen De Hondt  
wrote:
> Dear Pharo users and developers,
>
> Last week I told you about a new blog post that outlined the objectives of 
> the Atlas browser. It was the first post of a series.
> If you liked it, I invite you to read the next post 
> (https://all-objects-all-the-time.st/#/blog/posts/7). It describes the 
> Classification Model, which is the foundation of Atlas.
>
> Happy reading!
>
> Ciao,
> Koen
>

[Pharo-dev] "The Classification Model" — New blog post on all: objects all: theTime

[Koen De Hondt]

Dear Pharo users and developers,

Last week I told you about a new blog post that outlined the objectives of the 
Atlas browser. It was the first post of a series.
If you liked it, I invite you to read the next post 
. It describes the 
Classification Model, which is the foundation of Atlas.

Happy reading!

Ciao,
Koen

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

[Marcus Denker]

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

- Fixing issue #16291 - RBRemoveDirectAccessToVariableTransformationTest is 
failing #16293
https://github.com/pharo-project/pharo/pull/16293

- Fixes issue: RB - Undo refactoring sometimes not only undo the last changes 
of refactoring #8103 #16285
https://github.com/pharo-project/pharo/pull/16285

- Update Roassal to v1.06 #16287
https://github.com/pharo-project/pharo/pull/16287

- Remove use of ‘set -e’ from script ‘getPharoVM.sh’ #16282
https://github.com/pharo-project/pharo/pull/16282

- Prevents asking for user input twice during the Pushing up method refactoring 
#16281
https://github.com/pharo-project/pharo/pull/16281

- 16233-ChangeRecordtimeStamp-calls-deprecated-method #16254
https://github.com/pharo-project/pharo/pull/16254

- Fix title display in File Presenter windows #716
https://github.com/pharo-spec/NewTools/pull/716


# Improvements

- Add pre-filling the name text presenter in file dialogs #717
https://github.com/pharo-spec/NewTools/pull/717

- Adding tests for debug points + integrating debug points to Calypso Browser 
#16268
https://github.com/pharo-project/pharo/pull/16268

- Make #taskbarButtonMenu: on SystemWindow and MorphicNativeWindow use the 
FormSet for each of the icons #16296
https://github.com/pharo-project/pharo/pull/16296

- Refactor MenuItemMorph, PluggableMenuItemSpec and 
PragmaMenuAndShortcutRegistrationItem to support use of a FormSet and apply 
that to CmdCommand #16201
https://github.com/pharo-project/pharo/pull/16201

[Pharo-dev] IWST 24 — International Workshop on Smalltalk Technologies Lille, France; July 8th to 11th, 2024

[Steven Costiou]

IWST 24 INFORMATION AND CALL FOR PAPERS

IWST 24 -- International Workshop on Smalltalk Technologies Lille,
France; July 8th to 11th, 2024 

GOALS AND SCOPE

The goals of the workshop is to create a forum around contributions and
experiences in building or using technologies related to Smalltalk.
While maturity of presented ideas and results is not crucial, it is
expected that their presentation triggers discussion and exchange of
ideas. The topics of your paper can be on all aspect of Smalltalk,
theoretical as well as practical. Authors are invited to submit research
articles or industrial papers. 

IMPORTANT DATES

* Extended abstract submission deadline: MARCH 31ST, 2024
* Extended abstract notification deadline: April 7th, 2024
* Full/short paper submission deadline: May 19th, 2024
* Full/short paper first-round notification deadline: June 30th, 2024

* Workshop: July 9-10, 2024

* Full/short paper resubmission deadline: July 21st, 2024
* Full/short paper final notification deadline: July 31st, 2024
* Camera ready package submission deadline: August 25th, 2024

TOPICS

We welcome contributions on all aspects, theoretical as well as
practical, of Smalltalk related topics such as: 

* Code Analysis
* Automated Testing
* Debugging
* Compilers, Virtual Machines and Language implementations
* Meta-programming and Meta-modeling
* Refactorings
* Design patterns
* Experience reports
* Libraries and frameworks
* New dialects or languages implemented in Smalltalk
* Interaction and integration with other languages
* Tools

SUBMISSIONS, REVIEWS, AND SELECTION

Authors interetsed to present their work at the IWST 2024 are invited to
submit an abstract of the intended talk before the extended abstract
submission deadline. The extended abstract should be not longer than 2
pages following the CEUR ART style [1]. 

Author of the submitted extended abstratcs will be notified and invited
to present their work by the extended abstract notification deadline
which enables presenters to register at the early registration prices. 

Authors of the accepted abstracts are also invited to submit a paper to
be subject of the review and a potential acceptance for publishing in
the IWST 2024 Proceedings. 

We are looking for papers of two kinds: 

* Short position papers (5 to 10 pages) describing fresh ideas and
early results.
* Full research papers (more than 10 pages) with deeper description of
experiments and of research results.

Paper accepted for publishing will be published within a CEUR-WS
Proceedings [2]. Hence, both submissions and final papers must be
prepared using the CEUR ART style [1]. 

All submissions must be sent via EasyChair submission page [3]. 

Pay attention, for organisation constraints, when submitting your
article you are expected to register to the conference and pay the
conference fees. 

REVIEWING

As the workshop format encourages bringing fresh ideas and early results
to be presented and discussed, and aims for giving a chance to young
community members to learn and grow, we will allow submissions with a
discussion potential to be conditionally accepted. In this case, authors
are expected to follow the recommendation of the reviewers. 

Consequently, the reviewing process will be organized in two rounds: 

* in the first round, all submissions will be reviewed by at least 3
reviewers. Based on these reviews authors will receive a notification
with reviewers comments, advises, and requirements and papers that are
not rejected will be invited to be resubmitted in an improved form
together with change log and answrers to the reviewers.
* in the second round, PC chairs in collaboration with the reviewers
where needed and possible, will evaluate the improved paper version and
notifiy authors about final decision on acceptance/rejection.

BEST PAPER AWARD 

To encourage the submission of high-quality ideas, contributions, and
papers, the IWST organizing committee is very proud to announce a Award
competition in the categories of BEST IDEA, BEST CONTRIBUTION TO THE
COMMUNITY and BEST PAPER FOR THIS EDITION OF IWST. 

The ranking will be decided by the program committee during the review
process and by the audience voting during the conference. 

The awards will be given during the ESUG conference social event. 

The Awards will take place only with a minimum of six submissions.
Notice also that to be eligible, a paper/abstract must be presented at
the workshop by one of the author and that the presenting author must be
registered at the ESUG conference. 

PROGRAM CHAIRS

* Steven Costiou, Inria Lille, France (chair),
* Guille Polito, Inria Lille, France (chair),
* Gordana Rakic, University of Novi Sad, Serbia (chair)

PROGRAM COMMITTEE

to be published ... 

  

Links:
--
[1] 

[Pharo-dev] Re: [Pharo-users] Re: Re: "Introducing Atlas" — New blog post on all: objects all: theTime

[Koen De Hondt]

Thank you Noury.

Writing blog posts about Atlas was my plan to pave the way toward a 
presentation at ESUG’24, but when the date of the conference was announced I 
was sad to conclude that I cannot attend this year. So I will write more blog 
posts ;-)

I like the discussion too. As was already clear when I organized the Pharo 
Browser Survey , a lot of 
people have an opinion on the tool they use every day, which is good. I welcome 
all the feedback.

Best regards,
Koen

> On 13 Mar 2024, at 17:43, Noury Bouraqadi  wrote:
> 
> I read the blog post and I liked it. Thank you Koen!
> 
> I've also liked very much the discussion in this thread.
> I hope that you guys would expand your ideas and give talks at the ESUG 
> conference next July.
> 
> FYI here is the page with the ESUG call for presentations
> https://esug.github.io/2024-Conference/call2024.html
> 
> Noury ;-)
> On Mar 11 2024, at 4:27 pm, Aik-Siong Koh  wrote:
> Atlas is indeed ambitious, and I am glad you want to push the boundaries.
> 
> Over the decades, GUIs have introduced a bewildering array of widgets and 
> designs that I think we are in a mess again.
> I feel we should restart again with a blank window, allow select and 
> rightclick for context menu, and proceed for there to introduce the base 
> minimum for a functional GUI.
> I believe "select and rightclick context menu" can solve almost every GUI 
> need simply.
> I also think the single column menu can be updated to a two-column menu which 
> is more compact and balanced.
> The cursor can be centered between the two columns instead of being at the 
> top left corner.
> The cursor has to travel less for any selection.
> https://askoh.com/index.html#TwoColumnMenu
> 
> All the best,
> Aik-Siong Koh
> 
> On Mon, 11 Mar 2024 09:58:40 +, "Tim Mackinnon"  wrote:
>  
> As browsers are a passion in the Smalltalk world it will be great to read 
> your thoughts - as its certainly a hot potato, and we don't seem to have 
> quite cracked it so far.
>  
> I recall the presentations on Calypso from Pharo days (might have been 
> recorded for review if you haven't seen them). I recall being won over at the 
> time (and I was hesitant)  - there was lots of flexibility that had been 
> thought about, and many useful and tricky browsing patterns were covered - 
> but over time I think its proved tricky to work with. In Pharo 11, the 
> browsers don't seem to work as well as they should (lots of funny focus 
> issues and loss of context that I don't recall in previous version - which I 
> think is more down to understanding how it was supposed to work than 
> technical flaws).
>  
> It's definitely worth generating conversation and getting some consensus 
> otherwise it will be a rise and fall scenario all over again. This said, 
> continuing to find a good model that is both flexible and simple is useful.
>  
> Tim
>  
> p.s. On thing I recall from those Calypso presentations was that the model 
> should have let us design browsers where we  have different navigation models 
>  (e.g. you in theory you could design something where a class has a path to 
> methods which are both instance and class so you don't have to have a mode to 
> swap between them - something I find distracting when designing the interface 
> of a class and trying to figure out how you instantiate/initialize it and you 
> want to jump between the 2 view - I just want to see all all the methods in a 
> list, differentiated in some way vs. hiding them).
>  
> On Sun, 10 Mar 2024, at 5:24 PM, Koen De Hondt wrote:
> Dear Pharo users and developers,
>  
> Some people already know that I am working on a browser for Pharo. With this 
> announcement, I make it official .
> In my latest blog post , 
> I introduce Atlas as an ambitious successor of Calypso. It is the first post 
> in a series.
>  
> Happy reading!
>  
> Ciao,
> Koen
>  
> 

[Pharo-dev] Re: "Introducing Atlas" — New blog post on all: objects all: theTime

[Noury Bouraqadi]

I read the blog post and I liked it. Thank you Koen!

I've also liked very much the discussion in this thread.
I hope that you guys would expand your ideas and give talks at the ESUG 
conference next July.

FYI here is the page with the ESUG call for presentations
https://esug.github.io/2024-Conference/call2024.html

Noury ;-)
On Mar 11 2024, at 4:27 pm, Aik-Siong Koh  wrote:
> Atlas is indeed ambitious, and I am glad you want to push the boundaries.
>
> Over the decades, GUIs have introduced a bewildering array of widgets and 
> designs that I think we are in a mess again.
> I feel we should restart again with a blank window, allow select and 
> rightclick for context menu, and proceed for there to introduce the base 
> minimum for a functional GUI.
> I believe "select and rightclick context menu" can solve almost every GUI 
> need simply.
> I also think the single column menu can be updated to a two-column menu which 
> is more compact and balanced.
> The cursor can be centered between the two columns instead of being at the 
> top left corner.
> The cursor has to travel less for any selection.
> https://askoh.com/index.html#TwoColumnMenu
>
> All the best,
> Aik-Siong Koh
>
> On Mon, 11 Mar 2024 09:58:40 +, "Tim Mackinnon"  wrote:
>
> As browsers are a passion in the Smalltalk world it will be great to read 
> your thoughts - as its certainly a hot potato, and we don't seem to have 
> quite cracked it so far.
>
> I recall the presentations on Calypso from Pharo days (might have been 
> recorded for review if you haven't seen them). I recall being won over at the 
> time (and I was hesitant) - there was lots of flexibility that had been 
> thought about, and many useful and tricky browsing patterns were covered - 
> but over time I think its proved tricky to work with. In Pharo 11, the 
> browsers don't seem to work as well as they should (lots of funny focus 
> issues and loss of context that I don't recall in previous version - which I 
> think is more down to understanding how it was supposed to work than 
> technical flaws).
>
> It's definitely worth generating conversation and getting some consensus 
> otherwise it will be a rise and fall scenario all over again. This said, 
> continuing to find a good model that is both flexible and simple is useful.
>
> Tim
>
> p.s. On thing I recall from those Calypso presentations was that the model 
> should have let us design browsers where we have different navigation models 
> (e.g. you in theory you could design something where a class has a path to 
> methods which are both instance and class so you don't have to have a mode to 
> swap between them - something I find distracting when designing the interface 
> of a class and trying to figure out how you instantiate/initialize it and you 
> want to jump between the 2 view - I just want to see all all the methods in a 
> list, differentiated in some way vs. hiding them).
>
> On Sun, 10 Mar 2024, at 5:24 PM, Koen De Hondt wrote:
> > Dear Pharo users and developers,
> >
> > Some people already know that I am working on a browser for Pharo. With 
> > this announcement, I make it official .
> > In my latest blog post 
> > (https://all-objects-all-the-time.st/#/blog/posts/6), I introduce Atlas as 
> > an ambitious successor of Calypso. It is the first post in a series.
> >
> > Happy reading!
> >
> > Ciao,
> > Koen
> >
>
>
>
>

[Pharo-dev] [ANN] Pharo 12 development is now frozen

[Esteban Lorenzano via Pharo-dev]

Hi,

As we announced a couple of weeks ago, Pharo 12 development entered its 
freeze status.


This means no more new features will be included, we will concentrate 
until release just in important bugfixes.


If you have an issue that you consider a showstopper for your 
workflow/needs, let us now and we will consider it.


Cheers!

Esteban

[Pharo-dev] Re: "Introducing Atlas" — New blog post on all: objects all: theTime

[Aik-Siong Koh]

Atlas is indeed ambitious, and I am glad you want to push the boundaries.

Over the decades, GUIs have introduced a bewildering array of widgets and 
designs that I think we are in a mess again.
I feel we should restart again with a blank window, allow select and rightclick 
for context menu, and proceed for there to introduce the base minimum for a 
functional GUI.
I believe "select and rightclick context menu" can solve almost every GUI need 
simply.
I also think the single column menu can be updated to a two-column menu which 
is more compact and balanced.
The cursor can be centered between the two columns instead of being at the top 
left corner.
The cursor has to travel less for any selection.
https://askoh.com/index.html#TwoColumnMenu

All the best,
Aik-Siong Koh


On Mon, 11 Mar 2024 09:58:40 +, "Tim Mackinnon"  wrote:
 
As browsers are a passion in the Smalltalk world it will be great to read your 
thoughts - as its certainly a hot potato, and we don't seem to have quite 
cracked it so far.

 

I recall the presentations on Calypso from Pharo days (might have been recorded 
for review if you haven't seen them). I recall being won over at the time (and 
I was hesitant)  - there was lots of flexibility that had been thought about, 
and many useful and tricky browsing patterns were covered - but over time I 
think its proved tricky to work with. In Pharo 11, the browsers don't seem to 
work as well as they should (lots of funny focus issues and loss of context 
that I don't recall in previous version - which I think is more down to 
understanding how it was supposed to work than technical flaws).

 

It's definitely worth generating conversation and getting some consensus 
otherwise it will be a rise and fall scenario all over again. This said, 
continuing to find a good model that is both flexible and simple is useful.

 

Tim

 

p.s. On thing I recall from those Calypso presentations was that the model 
should have let us design browsers where we  have different navigation models  
(e.g. you in theory you could design something where a class has a path to 
methods which are both instance and class so you don't have to have a mode to 
swap between them - something I find distracting when designing the interface 
of a class and trying to figure out how you instantiate/initialize it and you 
want to jump between the 2 view - I just want to see all all the methods in a 
list, differentiated in some way vs. hiding them).

 

On Sun, 10 Mar 2024, at 5:24 PM, Koen De Hondt wrote:


Dear Pharo users and developers,

 


Some people already know that I am working on a browser for Pharo. With this 
announcement, I make it official .

In my latest blog post, I introduce Atlas as an ambitious successor of Calypso. 
It is the first post in a series.

 

Happy reading!

 

Ciao,

Koen



 

[Pharo-dev] Re: "Introducing Atlas" — New blog post on all: objects all: theTime

[Tim Mackinnon]

As browsers are a passion in the Smalltalk world it will be great to read your 
thoughts - as its certainly a hot potato, and we don't seem to have quite 
cracked it so far.

I recall the presentations on Calypso from Pharo days (might have been recorded 
for review if you haven't seen them). I recall being won over at the time (and 
I was hesitant)  - there was lots of flexibility that had been thought about, 
and many useful and tricky browsing patterns were covered - but over time I 
think its proved tricky to work with. In Pharo 11, the browsers don't seem to 
work as well as they should (lots of funny focus issues and loss of context 
that I don't recall in previous version - which I think is more down to 
understanding how it was supposed to work than technical flaws).

It's definitely worth generating conversation and getting some consensus 
otherwise it will be a rise and fall scenario all over again. This said, 
continuing to find a good model that is both flexible and simple is useful.

Tim

p.s. On thing I recall from those Calypso presentations was that the model 
should have let us design browsers where we  have different navigation models  
(e.g. you in theory you could design something where a class has a path to 
methods which are both instance and class so you don't have to have a mode to 
swap between them - something I find distracting when designing the interface 
of a class and trying to figure out how you instantiate/initialize it and you 
want to jump between the 2 view - I just want to see all all the methods in a 
list, differentiated in some way vs. hiding them).

On Sun, 10 Mar 2024, at 5:24 PM, Koen De Hondt wrote:
> Dear Pharo users and developers,
> 
> Some people already know that I am working on a browser for Pharo. With this 
> announcement, I make it official .
> In my latest blog post , 
> I introduce Atlas as an ambitious successor of Calypso. It is the first post 
> in a series.
> 
> Happy reading!
> 
> Ciao,
> Koen

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

[Marcus Denker]

# 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 URL #15980 #16284
https://github.com/pharo-project/pharo/pull/16284


# Fixes

- do not spam selectPage: #1528
https://github.com/pharo-spec/Spec/pull/1528

- Restore original message String #16274
https://github.com/pharo-project/pharo/pull/16274

- Fix Method name editor dialog up/down buttons #16273
https://github.com/pharo-project/pharo/pull/16273

- Fix Bug: OrderedDictionary>>#at:at:put: not updating ordered keys #16260
https://github.com/pharo-project/pharo/pull/16260

- Minor improvement in TF test class #16257
https://github.com/pharo-project/pharo/pull/16257

- Fix #magnifyBy:smoothing: on OSSDL2ExternalForm #16225
https://github.com/pharo-project/pharo/pull/16225

- fix a failing test #714
https://github.com/pharo-spec/NewTools/pull/714

# Improvements

- Make #reportTestCase:runBlock: on HDTestReport print the test run time on the 
progress log stream #16266
https://github.com/pharo-project/pharo/pull/16266

# Refactoring Engine

- Fix: rename method shortcut #16251
https://github.com/pharo-project/pharo/pull/16251

- Remove unused instance variable in #ReRenameMethodRefactoring #16279
https://github.com/pharo-project/pharo/pull/16279

- Fix: rename method preconditions fail with DNU #16270
https://github.com/pharo-project/pharo/pull/16270

- Test: rename method driver #16269
https://github.com/pharo-project/pharo/pull/16269

- Cleanup: rename method refactoring driver to new architecture with breaking 
choices #16258
https://github.com/pharo-project/pharo/pull/16258


# Cleanups

- Refactor various ‘worldMenu’ registration methods to use #iconName: instead 
of #icon: #711
https://github.com/pharo-spec/NewTools/pull/711

- Updated baseline of Dependency analyzer #16278
https://github.com/pharo-project/pharo/pull/16278

- 16246-CI-Failing-test-SystemDependenciesTesttestExternalIDEDependencies #16264
https://github.com/pharo-project/pharo/pull/16264

[Pharo-dev] "Introducing Atlas" — New blog post on all: objects all: theTime

[Koen De Hondt]

Dear Pharo users and developers,

Some people already know that I am working on a browser for Pharo. With this 
announcement, I make it official .
In my latest blog post , I 
introduce Atlas as an ambitious successor of Calypso. It is the first post in a 
series.

Happy reading!

Ciao,
Koen

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

[Marcus Denker]

# 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 classes on Windows #16262
https://github.com/pharo-project/pharo/pull/16262

- Fix adding slots in Ring #16247
https://github.com/pharo-project/pharo/pull/16247

- use the correct integration branch for iceberg and Pharo #16244
https://github.com/pharo-project/pharo/pull/16244

- fixing reflectivity bug that executes a #before metalink twice if an #after 
metalink is installed #16236
https://github.com/pharo-project/pharo/pull/16236

- MCWorkingCopy class>>#infoFromDictionary:cache: sends a deprecated method 
#16231
https://github.com/pharo-project/pharo/pull/16231

- 16204-RubPluggableTextFieldMorph-does-not-open-drop-list #16205
https://github.com/pharo-project/pharo/pull/16205

- Bug fix: Context menu item ‘Revert to selected version’ in recent versions of 
a method does not revert #710
https://github.com/pharo-spec/NewTools/pull/710

- ExpressionFinder - matches browser now knows the method that is showing #709
https://github.com/pharo-spec/NewTools/pull/709

# Graphics / Rendering / UI

- Make EpEntryItem use FormSet for the icons #16240
https://github.com/pharo-project/pharo/pull/16240

- Fix #freshLogFromSelection: on EpUnifiedBrowserPresenter to map trigger 
references #16239
https://github.com/pharo-project/pharo/pull/16239

- Refactor various ‘worldMenu’ registration methods to use #iconName: instead 
of #icon: #16237
https://github.com/pharo-project/pharo/pull/16237


# Refactoring Engine

- Fix: use new API for getting the package name in CopyClassRegexRefactoring 
#16256
https://github.com/pharo-project/pharo/pull/16256

- Fix: multiple exceptions when executing a rb move class transformation #16250
https://github.com/pharo-project/pharo/pull/16250

- Fix: #16209: [RB] Insert superclass refactoring breaks class side hierarchy 
#16234
https://github.com/pharo-project/pharo/pull/16234


# Cleanup

- Removed CursorWithAlpha as is not used #16229
https://github.com/pharo-project/pharo/pull/16229

- [Cleanup] #notNil to #isNotNil in Spec #1527
https://github.com/pharo-spec/Spec/pull/1527

# Documentation

- In TerseGuide fix documentation #16228
https://github.com/pharo-project/pharo/pull/16228

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

[Miloslav.Raus--- via Pharo-dev]

(Belated) „Hi, Folks“

To stress the point:
All of the 20-30 in-house apps I would have preferred to develop using 
Pharo(Squeak before that) were done in something that didn’t lack one of the 
following enablers (if we skip diacritics/fonts/locales):

· Drag & Drop (from the outside world)

· taskbar/status icons

· support for being launched as [Windows] Service

· COM

They might seem like small / moot points, but each and single one of them can 
be a show-stopper.
Probably could’ve written the support myself in the meantime, but the total 
lack of interest was what kept me from trying, and even asking for it.

I would have even tried to write something like Matrix myself (Fuel seemed 
promissing fot that use-case), but the rest of the ecosystem ...

Cheers and good luck,
  M.R.

From: Rauš Miloslav
Sent: Thursday, February 29, 2024 5:56 PM
To: Pharo Development List 
Cc: Any question about pharo is welcome 
Subject: RE: [Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and 
Automatize Business Processes

Funny how the story changes depending on the point where one stands.

OH, WE HAVE _AN_ APP.

vs:

Oh, they have an app ...

OS/Ecosystem Integration is what matters

· native integration

o   Drag & Drop (from the outside world)

o   taskbar/status icons

o   support for being launched as [Windows] Service

o   COM on windows (and I mean propper support, not the Astares placebo)

o   .NET bridge everywhere

o   perhaps even @#%$ Java

Semblance of multicore support (even faked, as is – was? – the oh-so-great 
Cincom „Matrix“) wouldn’t hurt (as far as dynamic/scripting languages go, TCL 
nailed it decades ago).

But yeah, progress happens, it just might seem slow to the people who are 
watching from the side-lines (Since Squeak 3, I think).

Keep on pushing forwards!

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

[Miloslav.Raus--- via Pharo-dev]

Funny how the story changes depending on the point where one stands.

OH, WE HAVE _AN_ APP.

vs:

Oh, they have an app ...

OS/Ecosystem Integration is what matters

· native integration

o   Drag & Drop (from the outside world)

o   taskbar/status icons

o   support for being launched as [Windows] Service

o   COM on windows (and I mean propper support, not the Astares placebo)

o   .NET bridge everywhere

o   perhaps even @#%$ Java

Semblance of multicore support (even faked, as is – was? – the oh-so-great 
Cincom „Matrix“) wouldn’t hurt (as far as dynamic/scripting languages go, TCL 
nailed it decades ago).

But yeah, progress happens, it just might seem slow to the people who are 
watching from the side-lines (Since Squeak 3, I think).

Keep on pushing forwards!


From: Noury Bouraqadi 
Sent: Tuesday, February 27, 2024 10:40 AM
To: Pharo Development List 
Cc: Any question about pharo is welcome ; Pharo 
Development List 
Subject: [Pharo-dev] Re: [Success Story] ApptiveGrid - Digitize and Automatize 
Business Processes

Cool. I think we need to share such success stories with the world through 
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 
mailto:marcus.den...@inria.fr>> wrote:
New Story posted on the Website:

ApptiveGrid - Digitize and Automatize Business Processes
https://www.pharo.org/success/ApptiveGrid.html

Marcus

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

[Noury Bouraqadi]

Liked 

On Feb 27 2024, at 1:18 pm, Marcus Denker  wrote:
> 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:
> > > 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 am, Marcus Denker  
> > > > wrote:
> > > > > Twitter and Facebook are posted today (posts are in the queue).
> > > > >
> > > > > I have on the TODO to create am official Pharo page? I think for 
> > > > > LinkedIn.
> > > > >
> > > > > Marcus
> > > > >
> > > > > > On 27 Feb 2024, at 10:40, Noury Bouraqadi  
> > > > > > wrote:
> > > > > > Cool. I think we need to share such success stories with the world 
> > > > > > through 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 - Digitize and Automatize Business Processes
> > > > > > > https://www.pharo.org/success/ApptiveGrid.html
> > > > > > >
> > > > > > >
> > > > > > > Marcus

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

[Marcus Denker]

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:
>> 
>> 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 am, Marcus Denker  wrote:
>>> Twitter and Facebook are posted today (posts are in the queue).
>>> 
>>> I have on the TODO to create am official Pharo page? I think for LinkedIn.
>>> 
>>> Marcus
>>> 
>>> On 27 Feb 2024, at 10:40, Noury Bouraqadi  wrote:
>>> 
>>> Cool. I think we need to share such success stories with the world through 
>>> 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 - Digitize and Automatize Business Processes
>>> https://www.pharo.org/success/ApptiveGrid.html
>>> 
>>> 
>>> Marcus
>> 
> 

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

[Marcus Denker]

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, Noury Bouraqadi  wrote:
>> 
>> There is already a LinkedIn account for Pharo 
>> https://www.linkedin.com/groups/2558378/
>> 
>> On Feb 27 2024, at 11:38 am, Marcus Denker  wrote:
>> Twitter and Facebook are posted today (posts are in the queue).
>> 
>> I have on the TODO to create am official Pharo page? I think for LinkedIn.
>> 
>> Marcus
>> 
>> On 27 Feb 2024, at 10:40, Noury Bouraqadi  wrote:
>> 
>> Cool. I think we need to share such success stories with the world through 
>> 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 - Digitize and Automatize Business Processes
>> https://www.pharo.org/success/ApptiveGrid.html
>> 
>> 
>> Marcus
> 

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

[Marcus Denker]

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 am, Marcus Denker  wrote:
> Twitter and Facebook are posted today (posts are in the queue).
> 
> I have on the TODO to create am official Pharo page? I think for LinkedIn.
> 
> Marcus
> 
> On 27 Feb 2024, at 10:40, Noury Bouraqadi  wrote:
> 
> Cool. I think we need to share such success stories with the world through 
> 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 - Digitize and Automatize Business Processes
> https://www.pharo.org/success/ApptiveGrid.html
> 
> 
> Marcus

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

[Noury Bouraqadi]

There is already a LinkedIn account for Pharo 
https://www.linkedin.com/groups/2558378/

On Feb 27 2024, at 11:38 am, Marcus Denker  wrote:
> Twitter and Facebook are posted today (posts are in the queue).
>
> I have on the TODO to create am official Pharo page? I think for LinkedIn.
>
> Marcus
>
> > On 27 Feb 2024, at 10:40, Noury Bouraqadi  wrote:
> > Cool. I think we need to share such success stories with the world through 
> > 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 - Digitize and Automatize Business Processes
> > > https://www.pharo.org/success/ApptiveGrid.html
> > >
> > >
> > > Marcus

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

[Marcus Denker]

Twitter and Facebook are posted today (posts are in the queue).

I have on the TODO to create am official Pharo page? I think for LinkedIn.

Marcus

> On 27 Feb 2024, at 10:40, Noury Bouraqadi  wrote:
> 
> Cool. I think we need to share such success stories with the world through 
> 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 - Digitize and Automatize Business Processes
> https://www.pharo.org/success/ApptiveGrid.html
> 
> 
> Marcus

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

[Noury Bouraqadi]

Cool. I think we need to share such success stories with the world through 
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 - Digitize and Automatize Business Processes
> https://www.pharo.org/success/ApptiveGrid.html
>
>
> Marcus

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

[Marcus Denker]

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

[Marcus Denker]

# 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
https://github.com/pharo-project/pharo/pull/16223

- add a way to allow some obsoletes through an environment variable #16222
https://github.com/pharo-project/pharo/pull/16222

- 
16132-Caret-return-char-broken-in-Pharo-11-macOS-Keyboard-as-US-International---PC
 #16206
https://github.com/pharo-project/pharo/pull/16206

- Fix tests in metacello, Spec font chooser and date comments #16195
https://github.com/pharo-project/pharo/pull/

# Tools

- Improving Message list morph UI #16096
https://github.com/pharo-project/pharo/pull/16096

- Do not show preview presenter when not needed #696
https://github.com/pharo-spec/NewTools/pull/696

- Align suffixes of FileBrowser #706
https://github.com/pharo-spec/NewTools/pull/706

- move edit path button close to the path #705
https://github.com/pharo-spec/NewTools/pull/705

- Add new folder button to file browser #704
https://github.com/pharo-spec/NewTools/pull/704

- Prevent errors in file operations. #703
https://github.com/pharo-spec/NewTools/pull/703

- Allow to sort some file browser columns #701
https://github.com/pharo-spec/NewTools/pull/701

- Catch preview errors in FileBrowser #700
https://github.com/pharo-spec/NewTools/pull/700


# Refactoring Engine

- Fix: extract method failing tests #16198
https://github.com/pharo-project/pharo/pull/16198

- Refactor: push down method driver #16197
https://github.com/pharo-project/pharo/pull/16197


# Cleanup

- Enhancement check keyword casing via lint rule #16220
https://github.com/pharo-project/pharo/pull/16220

- Fix: failing CI tests #16199
https://github.com/pharo-project/pharo/pull/16199

- Cleanup: Move more deprecated method to Deprecated12 #16194
https://github.com/pharo-project/pharo/pull/16194

- Cleanup: Small glitch in AsciiCharset class>>#toLowercase: #16192
https://github.com/pharo-project/pharo/pull/16192

- Cleanup: Cleanup Character protocols #16190
https://github.com/pharo-project/pharo/pull/16190

- Cleanup: Move deprecated #allCharacters to Deprecated12 package #16188
https://github.com/pharo-project/pharo/pull/16188

- Cleanup: deprecate nominallyUnsent: #16183
https://github.com/pharo-project/pharo/pull/16183

- DateAndTime asXXX methods should not be in accessing protocol #16181
https://github.com/pharo-project/pharo/pull/16181