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

2021-03-11 Thread Marcus Denker 
We merged 34 Pull Requests and fixed 41 Issues this week. 
https://github.com/pharo-project/pharo/pulse

Debugger


- 8659 expression leading to error is not highlighted anymore
https://github.com/pharo-project/pharo/pull/8770

- 8502 cannot proceed in debugger when loading fuel and bytecodes have changed 
#8768
https://github.com/pharo-project/pharo/pull/8768

- Fixing packages for extension packages in the debugger stack #8764
https://github.com/pharo-project/pharo/pull/8764

Refactoring Tooks
==

- RB - Introduce new refactoring "Merge inst var x in y" #8708
https://github.com/pharo-project/pharo/pull/8708

- RB - Migrate some class commands to commander2 #8709
https://github.com/pharo-project/pharo/pull/8709

- RB - Improve messages of remove class command #8685
https://github.com/pharo-project/pharo/pull/8685

- RB - Add support for traits in RBNamespace #8660
https://github.com/pharo-project/pharo/pull/8660

Fixes
=

- 8641-valueWithExit-should-answer-the-result-of-value #8696
https://github.com/pharo-project/pharo/pull/8696

- Package level comments #8724
https://github.com/pharo-project/pharo/pull/8724

- In CompiledMethod, replace #definition by #definitionString #8760
https://github.com/pharo-project/pharo/pull/8760

- 7756 Broken class definitions combining traits and slots [new try] #8683
https://github.com/pharo-project/pharo/pull/8683

- 8698-Failing-on-CI-ReleaseTesttestThatAllMethodsArePackaged #8699
https://github.com/pharo-project/pharo/pull/8699

- 8766-Adding-new-accessors-to-the-VM-object-to-statistics-and-parameters #8767
https://github.com/pharo-project/pharo/pull/8767


Cleanup: Unused Variables
==
The release tests for unused instance and class variables are now active!
This means that we will never merge a PR that has an unused variable.

- SptSpotterProcessor has an ivar "order" that is not used #8723
https://github.com/pharo-project/pharo/pull/8723

- 8720-RBTraitedMetaclass-has-unused-ivar #8721
https://github.com/pharo-project/pharo/pull/8721

- 8678-Clean-unused-Class-Vars-so-we-can-un-skip-testNoUnusedClassVariablesLeft 
#8707
https://github.com/pharo-project/pharo/pull/8707

- 8189-testNoUnusedInstanceVariablesLeft-is-skipped #8719
https://github.com/pharo-project/pharo/pull/8719


Cleanup: Abstract Classes
==

- TaskIt: TKTRunner and TKTAbstractExecutor should be abstract #8739
https://github.com/pharo-project/pharo/pull/8739

- Abstract classes in Font packages #8748
https://github.com/pharo-project/pharo/pull/8748

- Cleanups in DependencyAnalyzer (abstract classes, class comments) #8756
https://github.com/pharo-project/pharo/pull/8756

- Abstract classes in VariablesLibrary package #8750
https://github.com/pharo-project/pharo/pull/8750

- Zodiac: ZdcAbstractSocketStream and ZdcAbstractSSLSession as abstract classes 
#8735
https://github.com/pharo-project/pharo/pull/8735

- T2AbstractTest should be abstract #8745
https://github.com/pharo-project/pharo/pull/8745

- TaAbstractComposition should implement #isAbstract #8737
https://github.com/pharo-project/pharo/pull/8737

- Is ReNodeRewriteRule an abstract class? #8731
https://github.com/pharo-project/pharo/pull/8731

- ReAbstractCritique should implement #isAbstract to return true #8727
https://github.com/pharo-project/pharo/pull/8727

- ReAbstractRuleTestCase should be abstract #8716
https://github.com/pharo-project/pharo/pull/8716

- AbstractSessionHandler should be abstract #8714
https://github.com/pharo-project/pharo/pull/8714

Cleanups


- Proper method category names in TKTRunner and subclasses #8743
https://github.com/pharo-project/pharo/pull/8743

- Deprecate JapaneseEnvironment leftover methods #8754
https://github.com/pharo-project/pharo/pull/8754

- Extract example in FontChooser #8752
https://github.com/pharo-project/pharo/pull/8752

- Cleanups in AST packages #8758
https://github.com/pharo-project/pharo/pull/8758

- Cleanup method categories in TKTAbstractExecutor #8741
https://github.com/pharo-project/pharo/pull/8741

- Typo in class comment of ReSystemAnnouncer #8730
https://github.com/pharo-project/pharo/pull/8730

[Pharo-dev] Re: Cmd-line (headless) Pharo Launcher - structure of commands

2021-03-11 Thread bajger 
Hi Guille,

I already had a quick chat with Damien Pollet about how commands should be 
structured. Based on his recommendations, my original list of commands will be 
re-worked to be subject-verb like (gittish, dockerish) style, since CLAP allows 
this and it will be more logically stucured around vm, image, image template 
subjects.

I also set up project with CLAP dependency, so I could experiment with 
commands, here: https://github.com/Bajger/PharoLauncher-cli

More to come hopefully soon (as soon, as I get full understanding how CLAP 
works). 

Thanks for positive words!

David


Guillermo Polito
 wrote:

> Hi David,
>
> I think this is cool :)
>
> The things you describe are what I was having in mind too.
> The commands I use the most from the UI are:
>
> * create/delete an image
> * launch it
>
> \:)
>
> About the design of the command line, have you checked Clap? It should 
> provide support for parsing command line arguments and printing all the helps 
> for you.
>
> Also, If I can dream, I’d like that the launcher remembers the open images, 
> so we could also introduce something like
>
> launcher kill imageXXX
>
> Thanks!!!
> G.
>
> > El 10 mar 2021, a las 14:00, baj...@gmail.com escribió:
> >
> > Hi all!
> > I had a chat with Stephane regarding his inquiry about Pharo Launcher 
> > controlled from command-line interface (headless mode).
> > I'd like to ask core Pharo developers to briefly review, if current list of 
> > commands seems to be ok. Document here: 
> > https://github.com/Bajger/Pharo-snippets/blob/master/pharoLauncherCmdLine-description.md
> >  
> > 
> > Some notes:
> >
> > * List of commands is based on what can be executed on UI of Pharo Launcher
> > * there are some open questions, that you can try to comment on.
> >
> > Also, please suggest, if I should move .md page to some more appropriate 
> > project (e.g. Pharo wiki?)
> > Thanks for feedback!
> > David

[Pharo-dev] Re: Pharo - GSOC 2021

2021-03-11 Thread Hernán Morales Durand 
Congratulations :-)

Hernán

El jue, 11 mar 2021 a las 7:34, Serge Stinckwich (<
serge.stinckw...@gmail.com>) escribió:

> Dear all,
>
> great news I want to share with you: Pharo has been selected to be part of
> GSOC 2021
>
>
> https://summerofcode.withgoogle.com/organizations/?sp-search=pharo#4667274369171456
>
> Thank you to the great team of admins for making this happen: Oleksandr
> Zaitsev, Gordana Rakic and Juan Pablo Sandoval Alcocer !
>
> We will send updates soon on the student selection process soon.
> Regards,
> --
> Serge Stinckwic
> h
> https://twitter.com/SergeStinckwich
>

[Pharo-dev] Re: [Pharo-users] Pharo - GSOC 2021

2021-03-11 Thread Serge Stinckwich 
Yes accepted as an organization.
The Pharo GSOC admins will provide more details soon.

On Thu, 11 Mar 2021 at 21:13, Norbert Hartl  wrote:

> Great! This is to be accepted as organization? Projects still have to be
> accepted IIRC. Right?
>
> Norbert
>
> Am 11.03.2021 um 07:33 schrieb Serge Stinckwich <
> serge.stinckw...@gmail.com>:
>
> Dear all,
>
> great news I want to share with you: Pharo has been selected to be part of
> GSOC 2021
>
>
> https://summerofcode.withgoogle.com/organizations/?sp-search=pharo#4667274369171456
>
> Thank you to the great team of admins for making this happen: Oleksandr
> Zaitsev, Gordana Rakic and Juan Pablo Sandoval Alcocer !
>
> We will send updates soon on the student selection process soon.
> Regards,
> --
> Serge Stinckwic
> h
> https://twitter.com/SergeStinckwich
>
>
>

-- 
Serge Stinckwic
​h​
https://twitter.com/SergeStinckwich
​

[Pharo-dev] Re: [Pharo-users] Pharo - GSOC 2021

2021-03-11 Thread Norbert Hartl 
Great! This is to be accepted as organization? Projects still have to be 
accepted IIRC. Right?

Norbert

> Am 11.03.2021 um 07:33 schrieb Serge Stinckwich :
> 
> Dear all,
> 
> great news I want to share with you: Pharo has been selected to be part of 
> GSOC 2021
> 
> https://summerofcode.withgoogle.com/organizations/?sp-search=pharo#4667274369171456
>  
> 
> 
> Thank you to the great team of admins for making this happen: Oleksandr 
> Zaitsev, Gordana Rakic and Juan Pablo Sandoval Alcocer !
> 
> We will send updates soon on the student selection process soon.
> Regards,
> -- 
> Serge Stinckwich
> https://twitter.com/SergeStinckwich

[Pharo-dev] Re: Cmd-line (headless) Pharo Launcher - structure of commands

2021-03-11 Thread Guillermo Polito 
Hi David,

I think this is cool :)

The things you describe are what I was having in mind too.
The commands I use the most from the UI are:
 - create/delete an image
 - launch it

:)

About the design of the command line, have you checked Clap? It should provide 
support for parsing command line arguments and printing all the helps for you.

Also, If I can dream, I’d like that the launcher remembers the open images, so 
we could also introduce something like

launcher kill imageXXX

Thanks!!!
G.


> El 10 mar 2021, a las 14:00, baj...@gmail.com escribió:
> 
> Hi all!
> I had a chat with Stephane regarding his inquiry about Pharo Launcher 
> controlled from command-line interface (headless mode).
> I'd like to ask core Pharo developers to briefly review, if current list of 
> commands seems to be ok. Document here: 
> https://github.com/Bajger/Pharo-snippets/blob/master/pharoLauncherCmdLine-description.md
>  
> 
>  
> Some notes: 
> - List of commands is based on what can be executed on UI of Pharo Launcher 
> - there are some open questions, that you can try to comment on. 
> 
> Also, please suggest, if I should move .md page to some more appropriate 
> project (e.g. Pharo wiki?) 
> Thanks for feedback! 
> David
>