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

[Pharo 8.0] Build #18: 2154-Use-theme-colors-in-Rubric

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

There is a new Pharo build available! The status of the build #18 was: FAILURE. The Pull Request #2290 was integrated: "2154-Use-theme-colors-in-Rubric" Pull request url: https://github.com/pharo-project/pharo/pull/2290 Issue Url: https://pharo.fogbugz.com/f/cases/2154 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 22, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Tudor Girba

Great. I confirm that it works now :) Doru > On Jan 22, 2019, at 9:49 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> On 22 Jan 2019, at 21:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> On HackerNews, people are trying to run the factorial example from the main page and that does not work. It currently looks like this: >> >> $ curl https://get.pharo.org | bash >> $ ./pharo Pharo.image eval "42 factorialâ >> >> But, the path is incorrect. It should probably be more like: >> >> $ wget -O- https://get.pharo.org/64/stable | bash >> $ ./pharo Pharo.image eval "42 factorialâ >> >> Somehow curl did not work on my machine. It says: >> $ https://get.pharo.org/64/stable | bash >> bash: https://get.pharo.org/64/stable: No such file or directory >> bash-3.2$ curl https://get.pharo.org/64/stable | bash >> % Total % Received % Xferd Average Speed Time Time Time Current >> Dload Upload Total Spent Left Speed >> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Couldn't connect to server > > Damn it. > I fixed it (and made it point to 64bit which will work better on linux in general) > > Esteban > >> >> >> Cheers, >> Doru >> >> >> >>> On Jan 22, 2019, at 6:59 PM, Esteban Maringolo <emaringolo(a)gmail.com> wrote: >>> >>> The Discord channel could use some human replies as well, some >>> newcomers are coming with basic questions about getting started with >>> Pharo (and Pharo Launcher), so basic that I don't have a canonical >>> answer (because I work around these issues using my shenanigans). >>> >>> Esteban A. Maringolo >>> >>> El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe >>> (<sven(a)stfx.eu>) escribiÃ³: >>>> >>>> >>>> >>>>> On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> >>>>> https://news.ycombinator.com/item?id=18968116 >>>> >>>> Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). >>>> Let's keep the momentum going (this is a unique chance to get some publicity). >>> >> >> -- >> www.feenk.com >> >> "Things happen when they happen, >> not when you talk about them happening." -- www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

Jan. 22, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Esteban Lorenzano

> On 22 Jan 2019, at 21:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > On HackerNews, people are trying to run the factorial example from the main page and that does not work. It currently looks like this: > > $ curl https://get.pharo.org | bash > $ ./pharo Pharo.image eval "42 factorialâ > > But, the path is incorrect. It should probably be more like: > > $ wget -O- https://get.pharo.org/64/stable | bash > $ ./pharo Pharo.image eval "42 factorialâ > > Somehow curl did not work on my machine. It says: > $ https://get.pharo.org/64/stable | bash > bash: https://get.pharo.org/64/stable: No such file or directory > bash-3.2$ curl https://get.pharo.org/64/stable | bash > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Couldn't connect to server Damn it. I fixed it (and made it point to 64bit which will work better on linux in general) Esteban > > > Cheers, > Doru > > > >> On Jan 22, 2019, at 6:59 PM, Esteban Maringolo <emaringolo(a)gmail.com> wrote: >> >> The Discord channel could use some human replies as well, some >> newcomers are coming with basic questions about getting started with >> Pharo (and Pharo Launcher), so basic that I don't have a canonical >> answer (because I work around these issues using my shenanigans). >> >> Esteban A. Maringolo >> >> El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe >> (<sven(a)stfx.eu>) escribiÃ³: >>> >>> >>> >>>> On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> https://news.ycombinator.com/item?id=18968116 >>> >>> Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). >>> Let's keep the momentum going (this is a unique chance to get some publicity). >> > > -- > www.feenk.com > > "Things happen when they happen, > not when you talk about them happening." > >

Jan. 22, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Tudor Girba

Hi, On HackerNews, people are trying to run the factorial example from the main page and that does not work. It currently looks like this: $ curl https://get.pharo.org | bash $ ./pharo Pharo.image eval "42 factorialâ But, the path is incorrect. It should probably be more like: $ wget -O- https://get.pharo.org/64/stable | bash $ ./pharo Pharo.image eval "42 factorialâ Somehow curl did not work on my machine. It says: $ https://get.pharo.org/64/stable | bash bash: https://get.pharo.org/64/stable: No such file or directory bash-3.2$ curl https://get.pharo.org/64/stable | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Couldn't connect to server Cheers, Doru > On Jan 22, 2019, at 6:59 PM, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > The Discord channel could use some human replies as well, some > newcomers are coming with basic questions about getting started with > Pharo (and Pharo Launcher), so basic that I don't have a canonical > answer (because I work around these issues using my shenanigans). > > Esteban A. Maringolo > > El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe > (<sven(a)stfx.eu>) escribiÃ³: >> >> >> >>> On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> https://news.ycombinator.com/item?id=18968116 >> >> Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). >> Let's keep the momentum going (this is a unique chance to get some publicity). > -- www.feenk.com "Things happen when they happen, not when you talk about them happening."

Jan. 22, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Esteban Maringolo

The Discord channel could use some human replies as well, some newcomers are coming with basic questions about getting started with Pharo (and Pharo Launcher), so basic that I don't have a canonical answer (because I work around these issues using my shenanigans). Esteban A. Maringolo El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > > > > On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > https://news.ycombinator.com/item?id=18968116 > > Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). > Let's keep the momentum going (this is a unique chance to get some publicity).

Jan. 22, 2019

Win32OSProcessPlugin question (was: Better management of encoding of environment variables)

by David T. Lewis

Hi Nicolas, Motivated by the discussion on Pharo list, I added new primitives to OSProcessPlugin to answer environment variables and path information as raw ByteArray, such that those byte arrays can be converted in the image to strings with any encoding. I did the changes in "trunk" OSPP, and am now implementing them in the oscog branch. I have tested the Unix changes in both branches. Unfortunately I do not have a Windows development at the moment, so I need to ask for help. In Win32OSProcessPlugin, I am adding two primitives: #primitiveGetCurrentWorkingDirectoryAsBytes #primitiveGetEnvironmentStringsAsBytes These are based on the two string primitives, which remain available: #primitiveGetCurrentWorkingDirectory #primitiveGetEnvironmentStrings The string primitives include your recent changes for UTF8 encoding, and the "xxxAsBytes" variants are based on my earlier logic without the UTF8 support. This means that OSProcess on Windows will use your UTF8 string support, and the additional primitives (based on the old logic, and answering raw bytes) will be available for people who want to do the encoding work in the image. Does this sound like the right approach? Thanks, Dave I have a question concerning the Win32 changes. On Wed, Jan 16, 2019 at 10:24:51AM +0100, Nicolas Cellier wrote: > IMO, windows VM (and plugins) should do the UCS2 -> UTF8 conversion because > the purpose of a VM is to provide an OS independant fa??ade. > I made progress recently in this area, but we should finish the > job/test/consolidate. > If someone bypass the VM and use direct windows API thru FFI, then he takes > the responsibility, but uniformity doesn't hurt. > > Le mer. 16 janv. 2019 ?? 10:14, Guillermo Polito <guillermopolito(a)gmail.com> > a ??crit : > > > Hi Stephan, > > > > I'm sorry for the noise. > > > > At the time, both #at: and #getEnv: variants existed. The changes > > backported from the PharoLauncher were only using the getter versions of > > getEnv, but for Pharo I decided to implement also the setter versions. And > > after checking the code and its users in image, I've finally decided to go > > for an at:[[ifAbsent]put:] version. So I'd say that the leading > > **guideline** was at the end the one here in the mailing list, but also if > > you check the PR I've introduced a more complete and consistent API, > > following the one of dictionaries. > > > > https://github.com/pharo-project/pharo/pull/1980/files > > > > at: > > at:ifAbsent: > > at:ifPresent: > > at:ifPresent:ifAbsent: > > at:put: > > removeKey: > > > > Plus, in *nix, variants where an encoding can be specified. > > > > I'm sorry if I've introduced some confussion. > > > > > > On Wed, Jan 16, 2019 at 9:47 AM Stephan Eggermont <stephan(a)stack.nl> > > wrote: > > > > > > Guillermo Polito <guillermopolito(a)gmail.com> > > > wrote: > > > > Hi all, > > > > > > > > following the meeting we had here @Inria headquarters, I'll be > > backporting > > > > some of the improvements we did in the launcher this last month > > regarding > > > > the encoding of environment variables. > > > > > > > > I've opened for this issue https://pharo.fogbugz.com/f/cases/22658/ > > > > > > > > We have already studied possible alternatives with Pablo and > > Christophe and > > > > we have some conclusions and we propose some changes: > > > > > > > > API Proposal for OSEnvironment > > > > ========================= > > > > > > > > > > > > - > > > > *at: aVariableName * > > > > > > > > Gets the String value of an environment variable called `aVariableName` > > > > It is the system reponsibility to manage the encoding. > > > > Rationale: A common denominator for all platforms providing an already > > > > decoded string, because windows does not (compared to *nix systems) > > provide > > > > a encoded byte representation of the value. Windows has instead its own > > > > wide string representation. > > > > > > > > - *[optionally] rawAt: anEncodedVariableName* > > > > > > > > Gets the Byte value of an environment variable called > > > > `anEncodedVariableName`. > > > > It is the user responsibility to encode and decode argument and return > > > > values in the encoding of this preference. > > > > Rationale: Some systems may want to have the liberty to use different > > > > encodings, or even to put binary data in the variables. > > > > > > > > - *[optionally] at: aVariableName encoding: anEncoding* > > > > > > > > Gets the value of an environment variable called `aVariableName` using > > > > `anEncoding` to encode/decode arguments and return values. > > > > Rationale: *xes could potentially use different encodings for their > > > > environment variables or even use different encodings in different > > parts of > > > > their file system. > > > > > > > > Other Implementation details > > > > ========================= > > > > > > > > - VM primitives returning paths Strings should be carefuly managed > > to > > > > decode them, since they are actually C strings (so byte arrays) > > disguised > > > > as ByteStrings. > > > > - Windows requires calling the right *Wide version of the functions > > from > > > > C, plus the correct encoding routine. This could be implemented as > > an FFI > > > > call or by modifying the VM to do it properly instead of calling > > the Ascii > > > > version > > > > > > > > > > > > > > What is the conclusion from this and issue 22658? See PR 2238. #getEnv: > > is > > > public API > > > > > > Stephan > > > > > > > > > > > > > > > -- > > > > > > > > Guille Polito > > > > Research Engineer > > > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > > > CRIStAL - UMR 9189 > > > > French National Center for Scientific Research - http://www.cnrs.fr > > > > > > Web: http://guillep.github.io > > > > Phone: +33 06 52 70 66 13 > >

Jan. 22, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Sven Van Caekenberghe

> On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > https://news.ycombinator.com/item?id=18968116 Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). Let's keep the momentum going (this is a unique chance to get some publicity).

Jan. 22, 2019

[Pharo 7.0] Build #142: 22901-Image-crash-on-commit-and-push-in-windows-64bit

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

There is a new Pharo build available! The status of the build #142 was: SUCCESS. The Pull Request #2295 was integrated: "22901-Image-crash-on-commit-and-push-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/2295 Issue Url: https://pharo.fogbugz.com/f/cases/22901 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 22, 2019

[Pharo 7.0] Build #141: 22901-Image-crash-on-commit-and-push-in-windows-64bit

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

There is a new Pharo build available! The status of the build #141 was: SUCCESS. The Pull Request #2295 was integrated: "22901-Image-crash-on-commit-and-push-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/2295 Issue Url: https://pharo.fogbugz.com/f/cases/22901 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 22, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

by Sven Van Caekenberghe

Thank you, everybody, this is a massive collaborative effort, something to be proud of. > On 22 Jan 2019, at 14:36, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Pharo 7.0 released! > =============== > > Dear World and dynamic language lovers: > > The time has come for Pharo 7.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > <pastedGraphic.png> > > > This is our most significant release yet. Here are the key highlights of this release: > > â¢ Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. > â¢ Pharo comes with a new version of the PharoLauncher (https://pharo.org/download) THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). > â¢ Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. > â¢ Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. > â¢ Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. > â¢ IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. > â¢ The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit. > > Pharo 70âs new infrastructure and process set the stage for a new generation of version. > The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off. > > These are just the more prominent highlights, but the details are just as important. > > We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70Change…) > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, StÃ©phane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, ClÃ©ment BÃ©ra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, BenoÃ®t Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, HernÃ¡n Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, SÃ©bastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. > (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > The Pharo Team > > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

Jan. 22, 2019