July 2019 - Pharo-dev - lists.pharo.org

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

by Christophe Demarey

> Le 9 juil. 2019 Ã 07:57, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : > > christophe > > the name of the archive is confusing to me. > what is the diff between x64 and x86 x64: 64 bits version x86: 32 bit version For OS X, choose one of these with a dmg extension. The recommended version is always the 64-bits one. > which one is for mac? > S > >> On 8 Jul 2019, at 10:32, Christophe Demarey <Christophe.Demarey(a)inria.fr <mailto:Christophe.Demarey@inria.fr>> wrote: >> >> 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. >> > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> > http://www.synectique.eu <http://www.synectique.eu/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

July 9, 2019

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

by ducasse

It would be good to add this in the awesome documentation. Stef > On 8 Jul 2019, at 20:44, Torsten Bergmann <astares(a)gmx.de> wrote: > > 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 9, 2019

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

by tesonep＠gmail.com

Thanks Christophe! This thread opens a lot of interesting questions, and as most of them are all subjective and I will only add my opinion that is so wrong (or right) as all the other opinions. First, I consider that having options to do the same tasks with different considerations is good for the community, as it enlarges the options when using Pharo professionally. I always consider that a good engineer takes all the options and decide the best one depending on the existent requirement and restrictions. Sometimes we require to have tools that only fit for a single scenario and others that are general but mostly fit for all scenarios. I also consider good that Christophe, that fixes something for the Pharo Launcher (but it could have been any other project) and releases to the community so anyone else can fix the same problem. I ask everybody else before taking opinions to read the motivations behind the library / framework / couple of classes of Christophe. He required to have something that was working with correctly with UTF8 paths and it is polymorphic with OSSubprocess (as it is used in the other 2 platforms). I don't see any other solution that fulfills these requirements, so he has done an ad-hoc solution. Thankfully he has released it and now whoever cames later can have another option to use or even to copy and spawn a completely new solution. Finally, I share the good point of Torsten that we require to have a better way of publishing all the tools / libraries / pieces of code that we share, so the newcomers can find them easily. But even with the perfect documenting-sharing tool, it will be nice to have different solutions with different constraints and different improvements. Also, it will be nice to have more communication and focussing on pushing to the same targets. But how we can do that without cutting down the innovation, the reception of new ideas and the enjoy of implementing new things. One interesting case we have to accept as an open community is the reimplementation of something because is funny. I know this is not the case with Christophe, because I have seen him. This is also important and should not be cut down. It is not good to reinvent the wheel every time, but if we don't do it when it is required we will not have anything. I will really like to see more contributions of any kind, I invite to reimplement any of the things I did / do with new approaches and vision so everyone can grow. And one that will be really nice to have is a replacement for the catalog, so we can compare all the solutions that we have for a single problem!!! Thanks for reading me!! On Mon, Jul 8, 2019 at 12:13 PM Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi, > > Pharo Launcher had stability problems to spawn new processes (launch Pharo images) on Windows as well as limitations (paths could only contain ASCII characters). > To solve this problem, we developed a new library: OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess) and decided to make it a standalone library so that people can use it if they need to. > We tried to use the same API as OSSubprocess when possible. This library uses the Windows API to create process from both 32-bit and 64-bit Pharo images. It also supports Unicode characters. > > Here are some examples on how to use it: > > process := OSWSWinProcess new > command: 'C:\Windows\notepad.exe'; > run. > ... > process terminate. > > > OSWSWinProcess new > command: 'C:\Windows\notepad.exe'; > arguments: #('notepad.exe' 'C:\foo.txt'); > runAndWait. > > Important note: As of now, this library does not yet support standard streams (stdin, stdout and stderr). It could be done by setting the appropriate information in the STARTUPINFO structutre. > > You can check the README for more information. > > Regards, > Christophe. -- Pablo Tesone. tesonep(a)gmail.com

July 9, 2019

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

by StÃ©phane Ducasse

christophe the name of the archive is confusing to me. what is the diff between x64 and x86 which one is for mac? S > On 8 Jul 2019, at 10:32, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > 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. > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

July 9, 2019

[Pharo 8.0] Build #456: Avoid Symbol as argument to #ifNotNil:

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #456 was: SUCCESS. The Pull Request #3831 was integrated: "Avoid Symbol as argument to #ifNotNil:" Pull request url: https://github.com/pharo-project/pharo/pull/3831 Issue Url: https://github.com/pharo-project/pharo/issues/ifNotNil_Symbol Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 9, 2019

[Pharo 8.0] Build #455: 3577-GLMRubricExample-presentation-has-unnecessary-tempvar-seg

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #455 was: FAILURE. The Pull Request #3833 was integrated: "3577-GLMRubricExample-presentation-has-unnecessary-tempvar-seg" Pull request url: https://github.com/pharo-project/pharo/pull/3833 Issue Url: https://github.com/pharo-project/pharo/issues/3577 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 9, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by ducasse

nice email :) Just helping reviewing PR is a nice action. I do that systematically and I enjoy it. Tx! > On 8 Jul 2019, at 21:25, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hey YOU, YES YOU ! > > it was in 2017 when I asked people here on this list to help cleaning and raise the quality level of our Pharo system: > http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-an… > > I not only talked. I took action - meanwhile with around 658 (!) sometimes very trivial changes to > get Pharo 7 and 8 into a cleaner state (https://github.com/astares/pharo/branches) > > One step at a time ... evening per evening, week per week. Sometimes there was a minute - sometimes not. > > And yes: Pharo already became cleaner with small contributions from my and many others contributors side. Pharo now > already feels a little bit better - has class and test comments, more aligned packages, fixed categories, > less typos, cleaner and more understandable code and more rules to hopefully keep that quality level. > > > What if YOU, YES YOU would also step in and also apply simple or complex fixes and cleanups on internal > and also external packages? You could also help with documentation or feedback on what is working and what not. > > If we all clean the house TOGETHER the next guest would feel already more comfortable and also try not to > wear his dirty shoes... > > I also intentionally opened one single trivial issue without fixing it myself. Now today this issue got somehow > "famous" on Twitter: https://twitter.com/marcusdenker/status/1148287564937400321 > > and YOU can get famous for FIXING or REVIEWING this single issue too. > > Or you can help with many others that are left either here: https://github.com/orgs/pharo-project/projects/8 > or here: https://github.com/pharo-project/pharo/issues > > Jump in - the water is just fine! > > Bye > Torsten (aka "astares" on Discord) > >

July 9, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Torsten Bergmann

Hey YOU, YES YOU ! it was in 2017 when I asked people here on this list to help cleaning and raise the quality level of our Pharo system: http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-an… I not only talked. I took action - meanwhile with around 658 (!) sometimes very trivial changes to get Pharo 7 and 8 into a cleaner state (https://github.com/astares/pharo/branches) One step at a time ... evening per evening, week per week. Sometimes there was a minute - sometimes not. And yes: Pharo already became cleaner with small contributions from my and many others contributors side. Pharo now already feels a little bit better - has class and test comments, more aligned packages, fixed categories, less typos, cleaner and more understandable code and more rules to hopefully keep that quality level. What if YOU, YES YOU would also step in and also apply simple or complex fixes and cleanups on internal and also external packages? You could also help with documentation or feedback on what is working and what not. If we all clean the house TOGETHER the next guest would feel already more comfortable and also try not to wear his dirty shoes... I also intentionally opened one single trivial issue without fixing it myself. Now today this issue got somehow "famous" on Twitter: https://twitter.com/marcusdenker/status/1148287564937400321 and YOU can get famous for FIXING or REVIEWING this single issue too. Or you can help with many others that are left either here: https://github.com/orgs/pharo-project/projects/8 or here: https://github.com/pharo-project/pharo/issues Jump in - the water is just fine! Bye Torsten (aka "astares" on Discord)

July 8, 2019

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

[Pharo 8.0] Build #454: 3809-unify-isCompletionEnabled-and-isCodeCompletionAllowed

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #454 was: SUCCESS. The Pull Request #3810 was integrated: "3809-unify-isCompletionEnabled-and-isCodeCompletionAllowed" Pull request url: https://github.com/pharo-project/pharo/pull/3810 Issue Url: https://github.com/pharo-project/pharo/issues/3809 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 8, 2019