- Pharo-users - lists.pharo.org

Change code critics to decrease size of navigation pane?

by PAUL DEBRUICKER

Hi - Sometimes (all the times) I write method that violate a critics rule. The quality improvement pane, when it expands, shrinks the code editing pane. Can I change that so that it shrinks the height of the navigation panes instead e.g. the class list etc? Stopping writing "offensive" methods seems impossible. Thanks Paul

July 9, 2019

Comparing to commits in Iceberg

by Esteban Maringolo

Is there a way I can compare, and eventually merge, two arbitrary commits with Iceberg? E.g. I'm working on the latest commit of the master branch and want to see what changed against two commits ago, and maybe roll back some change. Regards, Esteban A. Maringolo

July 9, 2019

Re: [Pharo-users] [Pharo-dev] [ANN] OSWinSubprocess a library to spawn Windows System processes

by Torsten Bergmann

Without having a deeper look I guess what was done for Windows now is wrapping the usual STARTUPINFO, CreateProcess() functions and friends yet again ... Such wrappers and many other native friends were created from my side already years ago with my "OS-XXX" series of projects for different platforms: - http://smalltalkhub.com/#!/~OS/OS-Windows - http://smalltalkhub.com/#!/~OS/OS-OSX - http://smalltalkhub.com/#!/~OS/OS-Unix - http://smalltalkhub.com/#!/~OS/OS-Linux-CentOS - http://smalltalkhub.com/#!/~OS/OS-Linux-Ubuntu - http://smalltalkhub.com/#!/~OS/OS-Raspbian So for instance on Windows you could easily use WinProcess createProcess: 'explorer.exe' or WinProcess createAndWaitForProcess: 'cmd.exe'. The projects are available on Github now since 2018 and kept up to date for recent Pharo versions. - https://github.com/astares/Pharo-OS-Windows - https://github.com/astares/Pharo-OS-OSX - https://github.com/astares/Pharo-OS-Unix - https://github.com/astares/Pharo-OS-Linux-Ubuntu - https://github.com/astares/Pharo-OS-Raspbian All of them are available in Catalog. I have no problem with more and more implementations and the double efforts. But for Pharo users I have the feeling that it gets more and more confusing in the area of OSProcess, OSSubProcess, OSWinSubprocess, .... and more wrappers for basically the same thing ... Bye Torsten (aka astares)

July 8, 2019

Re: [Pharo-users] [ANN] Pharo Launcher 1.9.1 released

by Christophe Demarey

Better with the right url: https://files.pharo.org/pharo-launcher/1.9.1 <https://files.pharo.org/pharo-launcher/1.9.1> > Le 8 juil. 2019 Ã 10:32, Christophe Demarey <christophe.demarey(a)inria.fr> a Ã©crit : > > Hi all, > > We are pleased to announce Pharo Launcher 1.9.1 release! > The goal of this release is to have a better Windows support. Indeed Pharo Launcher now uses a new library OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) created for Pharo Launcher needs. This library allows to create Windows processes through ffi calls to the Windows API. It uses the unicode api, allowing paths with non-ascii characters. > In the same time, we switched from OSProcess to OSSubprocess (Linux and OS X) that is now the preferred library to use to fork processes on Linux-based systems. > > This release is not yet the default download of Pharo Launcher on Pharo web site because we want more feedback before promoting it. > Please use this link to install it: https://files.pharo.org/pharo-launcher/1.9 <https://files.pharo.org/pharo-launcher/1.9> and let us know if this version works fine/better for you. > > ps: For now, the binary is not signed but it will come soon. > ps2: Thanks to Keldon Alleyne for his PR on Pharo Launcher offering the first FFI binding to Windows process API > > Regards, > The Pharo team. >

July 8, 2019

Re: [Pharo-users] Testing "Weekly Digest" for GitHub

by Marcus Denker

> On 8 Jul 2019, at 11:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > if you want to be listed in the contributors section of the weekly report, > you can just do a pull request for one of the easy issues: > > https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%… <https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%…> > This can be nice small personal goal âI want to be listed in every weekly GitHub report as a Contributor until Pharo8 is releasedâ remember, you do not have to do muchâ¦ one tiny PR that improves or fixes *something*, it can be extremely trivial. Marcus

July 8, 2019

Re: [Pharo-users] Testing "Weekly Digest" for GitHub

by Marcus Denker

if you want to be listed in the contributors section of the weekly report, you can just do a pull request for one of the easy issues: https://github.com/pharo-project/pharo/issues?q=is%3Aissue+is%3Aopen+label%… > On 8 Jul 2019, at 10:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 8 Jul 2019, at 10:49, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Hi, >> >> There is a ProBot that creates an issue with a weekly summary. >> >> By installing it for testing, we got the first report: >> >> Weekly Digest (1 July, 2019 - 8 July, 2019) >> https://github.com/pharo-project/pharo/issues/381 <https://github.com/pharo-project/pharo/issues/381> >> > > Link is: > > https://github.com/pharo-project/pharo/issues/3814 <https://github.com/pharo-project/pharo/issues/3814> > >

July 8, 2019

Re: [Pharo-users] Testing "Weekly Digest" for GitHub

by Marcus Denker

> On 8 Jul 2019, at 10:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > There is a ProBot that creates an issue with a weekly summary. > > By installing it for testing, we got the first report: > > Weekly Digest (1 July, 2019 - 8 July, 2019) > https://github.com/pharo-project/pharo/issues/381 > Link is: https://github.com/pharo-project/pharo/issues/3814 <https://github.com/pharo-project/pharo/issues/3814>

July 8, 2019

Testing "Weekly Digest" for GitHub

by Marcus Denker

Hi, There is a ProBot that creates an issue with a weekly summary. By installing it for testing, we got the first report: Weekly Digest (1 July, 2019 - 8 July, 2019) https://github.com/pharo-project/pharo/issues/381 I will do some fine-tuning (e.g. disable commits and star-gazers) later. We then can let it run for some weeks and see if it is useful or not. Marcus

July 8, 2019

[ANN] Pharo Launcher 1.9.1 released

by Christophe Demarey

Hi all, We are pleased to announce Pharo Launcher 1.9.1 release! The goal of this release is to have a better Windows support. Indeed Pharo Launcher now uses a new library OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) created for Pharo Launcher needs. This library allows to create Windows processes through ffi calls to the Windows API. It uses the unicode api, allowing paths with non-ascii characters. In the same time, we switched from OSProcess to OSSubprocess (Linux and OS X) that is now the preferred library to use to fork processes on Linux-based systems. This release is not yet the default download of Pharo Launcher on Pharo web site because we want more feedback before promoting it. Please use this link to install it: https://files.pharo.org/pharo-launcher/1.9 <https://files.pharo.org/pharo-launcher/1.9> and let us know if this version works fine/better for you. ps: For now, the binary is not signed but it will come soon. ps2: Thanks to Keldon Alleyne for his PR on Pharo Launcher offering the first FFI binding to Windows process API Regards, The Pharo team.

July 8, 2019

Re: [Pharo-users] [GSoC blog post] Binary Search Trees

by ducasse

bfs: aValue => findBreadthFirst: aValue dfs: info node: aNode => findDeepFirst: aValue startingFrom: aNode

July 8, 2019