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

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

by Smiljana Knezev

Thank you all very much. This is quite useful for me and I can learn a lot. best regards, Smiljana Knezev ÑÑÐµ, 10. ÑÑÐ» 2019. Ñ 12:29 Ben Coman <btc(a)openinworld.com> ÑÐµ Ð½Ð°Ð¿Ð¸ÑÐ°Ð¾/Ð»Ð°: > I agree #bfs: is not explicit, but #breadthFirstSearch: is a well > know term, why not just that? Or even #breathFirstSearchFor: > > In comparison #findBreadthFirst: and #findDeepFirst: feel a bit > awkward to me. > (I think its the repetition rhythm of "f" words) > > cheers -ben > > On Mon, 8 Jul 2019 at 12:55, ducasse <stepharo(a)netcourrier.com> wrote: > > > > bfs: aValue > > > > => > > > > findBreadthFirst: aValue > > > > > > dfs: info node: aNode > > > > => > > > > findDeepFirst: aValue startingFrom: aNode > >

July 10, 2019

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

by Ben Coman

I agree #bfs: is not explicit, but #breadthFirstSearch: is a well know term, why not just that? Or even #breathFirstSearchFor: In comparison #findBreadthFirst: and #findDeepFirst: feel a bit awkward to me. (I think its the repetition rhythm of "f" words) cheers -ben On Mon, 8 Jul 2019 at 12:55, ducasse <stepharo(a)netcourrier.com> wrote: > > bfs: aValue > > => > > findBreadthFirst: aValue > > > dfs: info node: aNode > > => > > findDeepFirst: aValue startingFrom: aNode

July 10, 2019

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

by webwarrior

Smiljana Knezev wrote > Dear all, > > I've written about implementing binary search trees: > https://pharokeepers.github.io/pharo/2019/07/07/SmiljanaBinarySearchTreeinP… > > Feedback and opinions is always welcome :) > > Best regards, > Smiljana Knezev Your implementation is unnecesarily complicated. Remember, tree is a recursive data structure. You may have have reasons to split tree and node into different classes, but at least delegate operations to node. For example, #depth and #size can be defined as following methods of Node class: depth self isLeaf ifTrue: [ ^ 0 ]. ^ leftChild depth max: rightChild depth size self isLeaf ifTrue: [ ^ 1 ]. ^ leftChild size + rightChlid size Most other operations can also be defined in similar fashion. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 10, 2019

ESUG Innovation Technology Awards Call for submissions

by N. Bouraqadi

Dear Smalltalkers, Developers are invited to submit their Smalltalk-related project to the 16th edition of the ESUG Innovation Technology Awards. The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros. Submit now! Instructions are available at: https://esug.github.io/2019-Conference/awardsCall2019.html Noury

July 9, 2019

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

by Christophe Demarey

Hi Torsten, > Le 8 juil. 2019 Ã 20:44, Torsten Bergmann <astares(a)gmx.de> a Ã©crit : > > Without having a deeper look I guess what was done for Windows now is wrapping the usual STARTUPINFO, CreateProcess() > functions and friends yet again â¦ Indeed. A subtle difference is that we use the Unicode version of this API. > > 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 I know this library as doing a lot of cool things for the integration with the OS but I was not aware there was an implementation of processes forking. I thought it used one of the existing library to do that. > - 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 â¦ I think you are right on this point. I have the same feeling. Also, OSSubprocess is now the recommended way to fork processes on Linux like systems, and there is no support yet for Windows, I took the opportunity to create the OSWinSubprocess project that could be easily merged into OSSubprocess once it gets all required features. I based my work on a PR done on Pharo Launcher by Keldon Alleyne. If I knew about the process support in OS-Windows, I would for sure, at least, had a look at it and possibly re-use it. I see you have some support for pipes / streams. If you are willing to we could work together to merge both implementation. The only thing is that we should keep the OSSubprocess API when possible to allow a merge with it in a future. WDYT? Christophe.

July 9, 2019

Re: [Pharo-users] [Pharo-dev] [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-users] [Pharo-dev] [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

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