June 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to use uFFI with String

by Ben Coman

Cool. Looks good. cheers -ben On Wed, Jun 7, 2017 at 2:20 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi ben > > Yes I changed it :) > Stef > > On Mon, May 29, 2017 at 10:16 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Mon, May 29, 2017 at 7:24 AM, horrido <horrido.hobbies(a)gmail.com> > wrote: > >> I don't use GitHub. I've never used GitHub. I don't know how to use > GitHub. > >> > >> I looked at making a pull request and I was totally stymied. "Clueless" > >> doesn't even begin to describe how I felt. > > > > Everyone starts there. Its a useful skill to have, so if you are > > interested to learn, here's a quickstart guide... > > (Note since its a text file, we are shortcutting so you don't even > > need git on your local machine) > > 1. Click on this link. > > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/blob/ > master/Morphic/Morphic.pier > > 2. Click the <Fork> button in the top tight, then browse to > > "Morphic.pier" in your fork. > > 3. To the right of the <Raw/Blame/History> buttons, click the <Pencil> > > button to edit the file. > > 4. After editing, at the bottom select "Create a new branch for this > > commit and start a pull request" > > and enter commit title, comment and new-branch-name to reflect your > > contribution. Click <Propose file change> > > 5. Now looking at "Open a pull request", this is issuing a PR to your > > own fork. We need to change to the upstream fork. At the top click > > on "forked from SquareBracketAssociates/UpdatedPharoByExample" . > > 6. Under "Your recently pushed branches" click <Compare & pull request> > > 7. Check... > > base fork: SquareBracketAssociates/UpdatedPharoByExample > > base: master > > head fork: YourName/UpdatedPharoByExample > > compare: your new-branch-name > > Review the diff, enter PR title and comment, then click <Create pull > request>. > > > > If you have problems, try to catch me on Discord... > > https://discord.gg/dKv4qR/KCKQSSt > > > > cheers -ben > > > > P.S. @Stef, btw, it looks like "the guidelines for contributing" is > > out of date... > > https://github.com/SquareBracketAssociates/ > UpdatedPharoByExample/blob/master/CONTRIBUTING.md > > "This is a test to see if it makes sense to convert PharoByExample > > into pier format." > > > > > >> > >> > >> Ben Coman wrote > >>> On Sat, May 27, 2017 at 9:15 PM, horrido < > >> > >>> horrido.hobbies@ > >> > >>> > wrote: > >>>> Yes, I did. I found it difficult to understand. It would be nice to > have > >>>> some > >>>> clear examples in the documentation, for example, really simple and > >>>> common > >>>> situations such as a C function returning an integer in a > >>>> passed-by-reference argument. > >>>> > >>>> Speaking of documentation, in "Pharo by Example 50," I found this > >>>> statement: > >>>> > >>>>> (Recall that you should set halosEnabled in the Preferences > >>>> browser.) > >>>> > >>>> However, nowhere else in the book is there any reference to > halosEnabled > >>>> or > >>>> Preferences browser. > >>> > >>> Nice pick up. Now in Settings (in a fresh 60473 image), filtering on > >>> "halo" shows only: > >>> * Cycle both directions > >>> * Encloses fullbounds > >>> * Exhibits bounds > >>> so the comment seems irrelevant > >>> > >>> and #halosEnabled & #halosEnabled: each have one implementor > class-side of > >>> Morph > >>> with one sender from MorphTest each, and one sender from > Morph>>addHalo: > >>> > >>> and "Morph halosEnabled" ==> true, so the statement seems unnecessary. > >>> Would you like to contribute a pull request removing it? > >>> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/blob/ > master/Morphic/Morphic.pier > >>> > >>> > >>>> Did you guys forget and leave out a chunk of the book? > >>> > >>> Its an evolutionary book originally from Squeak. It could well be > >>> that some parts of the book have been cleaned > >>> better than others to match Image changes. Thanks for reporting, and > >>> even better if you can correct it. > >>> > >>> cheers -ben > >> > >> > >> > >> > >> > >> -- > >> View this message in context: http://forum.world.st/How-to- > use-uFFI-with-String-tp4947890p4948512.html > >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >> > > > >

June 7, 2017

Re: [Pharo-users] How to deploy headless app without changes and source files?

by Andreas Sunardi

Hi Stef, I can't have changes file bundled with the tool because the tool is installed in a centralized location in my network and multiple users will run it. So the image is in a central location and read-only and so is the changes file (if I must have a changes file). The tool is only a processor. It does not need to keep/save its state. Hence, I cannot have multiple users writing to that one and the same changes file. I'm trying to dissect the call chain to ChangesLog and try to cut it so Pharo won't write to the changes file. I'm sure I should not do this. There must be a better way. On Tue, Jun 6, 2017 at 11:55 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > We started to work on making the system ready to stop using these files. > There are two things. > - the changes are a tape that logs what you are doing and right now > the system is not done to accept not to log > So I imagine that you can remove the changes file but then do not compile > code. > - I do not get the "so I can't have changes file bundled with the tool." > you do not have a bat or script that launches the application that is > somewhere in a folder where you have the vm and the image? you could > have the changes file there. > > We are interested in your scenario because last year I got a guy > working on making pharo silent. I do not know if its changes got > integrated into pharo. > This is really something that we want to have. > - having sources and changes in a specific location > - having no source and no changes (even if it means lose your code). > - ... > > Stef > > On Tue, Jun 6, 2017 at 8:14 PM, Andreas Sunardi <a.sunardi(a)gmail.com> > wrote: > > Sorry to bring this up again. But it turns out that I had the image > > directory writable by myself, so it created a new changes file. That's > why > > Pharo didn't complain about missing changes file. When I removed write > > permission in the tool installation, Pharo gives error for not having or > not > > able to write to changes file. > > > > I guess I'm back to the problem how to deploy a tool without changes > file. I > > have multiple users that will be running this tool, which is installed > in a > > centralized site, so I can't have changes file bundled with the tool. > > > > On Mon, Jun 5, 2017 at 5:47 PM, Andreas Sunardi <a.sunardi(a)gmail.com> > wrote: > >> > >> I had my changes and sources files in the bundle but has their write > >> permission removed, and that causes the error. Simply deploying the tool > >> without the changes file seems to fix it. Pharo5 doesn't complain if the > >> changes file isn't there. > >> > >> However, without the sources file, I get this warning that pharo cannot > >> locate the sources file. Including the sources file in the deployed > tool is > >> fine with me. > >> > >> So, I think that's my solution. Thanks! > >> > >> > >> On Mon, Jun 5, 2017 at 5:07 PM, Andreas Sunardi <a.sunardi(a)gmail.com> > >> wrote: > >>> > >>> I found this StackOverflow question: > >>> > >>> https://stackoverflow.com/questions/14737695/is-it- > possible-to-deploy-a-pharo-image-without-changes-and- > sources-files/14747328 > >>> > >>> and this older forum thread: > >>> > >>> https://www.mail-archive.com/pharo-project@lists.gforge. > inria.fr/msg21170.html > >>> > >>> I'm using Pharo5.0 and neither of these options is available anymore. > >>> What is the new way to do this? > >>> > >>> -- > >>> Andreas Sunardi > >> > >> > > > >

June 6, 2017

Re: [Pharo-users] How to deploy headless app without changes and source files?

by Stephane Ducasse

We started to work on making the system ready to stop using these files. There are two things. - the changes are a tape that logs what you are doing and right now the system is not done to accept not to log So I imagine that you can remove the changes file but then do not compile code. - I do not get the "so I can't have changes file bundled with the tool." you do not have a bat or script that launches the application that is somewhere in a folder where you have the vm and the image? you could have the changes file there. We are interested in your scenario because last year I got a guy working on making pharo silent. I do not know if its changes got integrated into pharo. This is really something that we want to have. - having sources and changes in a specific location - having no source and no changes (even if it means lose your code). - ... Stef On Tue, Jun 6, 2017 at 8:14 PM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > Sorry to bring this up again. But it turns out that I had the image > directory writable by myself, so it created a new changes file. That's why > Pharo didn't complain about missing changes file. When I removed write > permission in the tool installation, Pharo gives error for not having or not > able to write to changes file. > > I guess I'm back to the problem how to deploy a tool without changes file. I > have multiple users that will be running this tool, which is installed in a > centralized site, so I can't have changes file bundled with the tool. > > On Mon, Jun 5, 2017 at 5:47 PM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: >> >> I had my changes and sources files in the bundle but has their write >> permission removed, and that causes the error. Simply deploying the tool >> without the changes file seems to fix it. Pharo5 doesn't complain if the >> changes file isn't there. >> >> However, without the sources file, I get this warning that pharo cannot >> locate the sources file. Including the sources file in the deployed tool is >> fine with me. >> >> So, I think that's my solution. Thanks! >> >> >> On Mon, Jun 5, 2017 at 5:07 PM, Andreas Sunardi <a.sunardi(a)gmail.com> >> wrote: >>> >>> I found this StackOverflow question: >>> >>> https://stackoverflow.com/questions/14737695/is-it-possible-to-deploy-a-pha… >>> >>> and this older forum thread: >>> >>> https://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg21170.h… >>> >>> I'm using Pharo5.0 and neither of these options is available anymore. >>> What is the new way to do this? >>> >>> -- >>> Andreas Sunardi >> >> >

June 6, 2017

Re: [Pharo-users] [ANN] Pharo 6.0 released!

by Stephan Eggermont

On 06/06/17 17:11, Esteban Lorenzano wrote: > Dear World, > > The time has come for Pharo 6.0! Yes! Well done! Stephan

June 6, 2017

Re: [Pharo-users] is it related to Freetype or Athens?

by Stephane Ducasse

Hilaire If I remember correcly, there is a bug in cairo so igor was sometimes forced to change the font size multiplying a little to force the plugin to react. Stef On Tue, Jun 6, 2017 at 7:33 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi there, > > A Dr. Geo user on Ubuntu 64bits 16.04 got that buggy rendering of the > canvas, then on some situation the rendering completely stop on a red > screen, with a stack showing may be a zero divide error. I did not get > access to the PharoDebog yet. > > Fonts on the screenshot is not right too. Could it be a mixed problem > between FreeType and Cairo? Any first though on the issue welcome. > > Given the fact Dr. Geo is still based on Pharo3 and it works pretty fine > on my old Ubuntu 12.07 derived system, it may be time to port the newer > Pharo6. > > Congrats for the Pharo6 release. > > Hilaire > > -- > Dr. Geo > http://drgeo.eu >

June 6, 2017

Re: [Pharo-users] How to use uFFI with String

by Stephane Ducasse

Hi ben Yes I changed it :) Stef On Mon, May 29, 2017 at 10:16 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, May 29, 2017 at 7:24 AM, horrido <horrido.hobbies(a)gmail.com> wrote: >> I don't use GitHub. I've never used GitHub. I don't know how to use GitHub. >> >> I looked at making a pull request and I was totally stymied. "Clueless" >> doesn't even begin to describe how I felt. > > Everyone starts there. Its a useful skill to have, so if you are > interested to learn, here's a quickstart guide... > (Note since its a text file, we are shortcutting so you don't even > need git on your local machine) > 1. Click on this link. > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/blob/maste… > 2. Click the <Fork> button in the top tight, then browse to > "Morphic.pier" in your fork. > 3. To the right of the <Raw/Blame/History> buttons, click the <Pencil> > button to edit the file. > 4. After editing, at the bottom select "Create a new branch for this > commit and start a pull request" > and enter commit title, comment and new-branch-name to reflect your > contribution. Click <Propose file change> > 5. Now looking at "Open a pull request", this is issuing a PR to your > own fork. We need to change to the upstream fork. At the top click > on "forked from SquareBracketAssociates/UpdatedPharoByExample" . > 6. Under "Your recently pushed branches" click <Compare & pull request> > 7. Check... > base fork: SquareBracketAssociates/UpdatedPharoByExample > base: master > head fork: YourName/UpdatedPharoByExample > compare: your new-branch-name > Review the diff, enter PR title and comment, then click <Create pull request>. > > If you have problems, try to catch me on Discord... > https://discord.gg/dKv4qR/KCKQSSt > > cheers -ben > > P.S. @Stef, btw, it looks like "the guidelines for contributing" is > out of date... > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/blob/maste… > "This is a test to see if it makes sense to convert PharoByExample > into pier format." > > >> >> >> Ben Coman wrote >>> On Sat, May 27, 2017 at 9:15 PM, horrido < >> >>> horrido.hobbies@ >> >>> > wrote: >>>> Yes, I did. I found it difficult to understand. It would be nice to have >>>> some >>>> clear examples in the documentation, for example, really simple and >>>> common >>>> situations such as a C function returning an integer in a >>>> passed-by-reference argument. >>>> >>>> Speaking of documentation, in "Pharo by Example 50," I found this >>>> statement: >>>> >>>>> (Recall that you should set halosEnabled in the Preferences >>>> browser.) >>>> >>>> However, nowhere else in the book is there any reference to halosEnabled >>>> or >>>> Preferences browser. >>> >>> Nice pick up. Now in Settings (in a fresh 60473 image), filtering on >>> "halo" shows only: >>> * Cycle both directions >>> * Encloses fullbounds >>> * Exhibits bounds >>> so the comment seems irrelevant >>> >>> and #halosEnabled & #halosEnabled: each have one implementor class-side of >>> Morph >>> with one sender from MorphTest each, and one sender from Morph>>addHalo: >>> >>> and "Morph halosEnabled" ==> true, so the statement seems unnecessary. >>> Would you like to contribute a pull request removing it? >>> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/blob/maste… >>> >>> >>>> Did you guys forget and leave out a chunk of the book? >>> >>> Its an evolutionary book originally from Squeak. It could well be >>> that some parts of the book have been cleaned >>> better than others to match Image changes. Thanks for reporting, and >>> even better if you can correct it. >>> >>> cheers -ben >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/How-to-use-uFFI-with-String-tp4947890p4948512.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >

June 6, 2017

Re: [Pharo-users] How to deploy headless app without changes and source files?

by Andreas Sunardi

Sorry to bring this up again. But it turns out that I had the image directory writable by myself, so it created a new changes file. That's why Pharo didn't complain about missing changes file. When I removed write permission in the tool installation, Pharo gives error for not having or not able to write to changes file. I guess I'm back to the problem how to deploy a tool without changes file. I have multiple users that will be running this tool, which is installed in a centralized site, so I can't have changes file bundled with the tool. On Mon, Jun 5, 2017 at 5:47 PM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > I had my changes and sources files in the bundle but has their write > permission removed, and that causes the error. Simply deploying the tool > without the changes file seems to fix it. Pharo5 doesn't complain if the > changes file isn't there. > > However, without the sources file, I get this warning that pharo cannot > locate the sources file. Including the sources file in the deployed tool is > fine with me. > > So, I think that's my solution. Thanks! > > > On Mon, Jun 5, 2017 at 5:07 PM, Andreas Sunardi <a.sunardi(a)gmail.com> > wrote: > >> I found this StackOverflow question: >> https://stackoverflow.com/questions/14737695/is-it-possible- >> to-deploy-a-pharo-image-without-changes-and-sources-files/14747328 >> >> and this older forum thread: >> https://www.mail-archive.com/pharo-project@lists.gforge.inri >> a.fr/msg21170.html >> >> I'm using Pharo5.0 and neither of these options is available anymore. >> What is the new way to do this? >> >> -- >> Andreas Sunardi >> > >

June 6, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.0 released!

by Stephane Ducasse

Tx torsten. New space is opening to us :) On Tue, Jun 6, 2017 at 7:49 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Dear friends, > > Yes - really an impressive release. With many cleanups and new treasures in the image - but also many > shiny new/updated external packages and projects (like Roassal, Polymath, Calypso browser, ... to name just a few). > > Thanks to all who helped - especially to the ones who cared and also worked on the not so interesting but > often hard to solve issues or boring but necessary parts or infrastructure. > > The new git integration in Pharo and the included Iceberg tool will allow us to work with services > like GitHub, GitLab, BitBucket - even own local git servers (for instance setups using Gogs.io). We can now manage > project resources beside code, commit several packages at once and branch and merge as necessary. > This really rocks! > > Many thanks also to all the contributors of the OpenSmalltalk initiative - it is also impressive > how much progress was done on VM side. Also thanks to the ones writing new books, articles and tutorials > so other can learn and enjoy such a fantastic dynamic and lively system. > > We still have a way to go for Pharo 7 and onwards. I'm eager to play with the new git based development process and > interested on how we can manage to build our future Pharo based on the bootstrap efforts. > > Even when not finally there ... step by step it goes! > > Bye > T. > > > > Gesendet: Dienstag, 06. Juni 2017 um 17:11 Uhr > Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" <pharo-dev(a)lists.pharo.org>, members-consortium(a)pharo.org, "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org>, "list ESUG Mailing" <esug-list(a)lists.esug.org> > Betreff: [Pharo-dev] [ANN] Pharo 6.0 released! > > Dear World, > > The time has come for Pharo 6.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > This is our most significant release yet. Here are some highlights: > > > - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) > - A new code changes management system named Epicea for easier reviewing and recovering of your code easily > - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) > - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved > - The PharoVM is now part of OpenSmalltalk initiative > - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context > - Pharo can now be bootstrapped from source code managed by Git > - Pharo modularity is improved > - Pharo is faster > - The Dark Theme was improved and set as default color theme of Pharo > > > > These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…) > > While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk > > (If you contributed with Pharo 6.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[http://pharo.org/download] > Learn Pharo: http://pharo.org/documentation[http://pharo.org/documentation] >

June 6, 2017

[Pharo-dev] [ANN] Pharo 6.0 released!

by Torsten Bergmann

Dear friends, Yes - really an impressive release. With many cleanups and new treasures in the image - but also many shiny new/updated external packages and projects (like Roassal, Polymath, Calypso browser, ... to name just a few). Thanks to all who helped - especially to the ones who cared and also worked on the not so interesting but often hard to solve issues or boring but necessary parts or infrastructure. The new git integration in Pharo and the included Iceberg tool will allow us to work with services like GitHub, GitLab, BitBucket - even own local git servers (for instance setups using Gogs.io). We can now manage project resources beside code, commit several packages at once and branch and merge as necessary. This really rocks! Many thanks also to all the contributors of the OpenSmalltalk initiative - it is also impressive how much progress was done on VM side. Also thanks to the ones writing new books, articles and tutorials so other can learn and enjoy such a fantastic dynamic and lively system. We still have a way to go for Pharo 7 and onwards. I'm eager to play with the new git based development process and interested on how we can manage to build our future Pharo based on the bootstrap efforts. Even when not finally there ... step by step it goes! Bye T. Â Gesendet:Â Dienstag, 06. Juni 2017 um 17:11 Uhr Von:Â "Esteban Lorenzano" <estebanlm(a)gmail.com> An:Â "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" <pharo-dev(a)lists.pharo.org>, members-consortium(a)pharo.org, "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org>, "list ESUG Mailing" <esug-list(a)lists.esug.org> Betreff:Â [Pharo-dev] [ANN] Pharo 6.0 released! Dear World, Â The time has come for Pharo 6.0! Â Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Â This is our most significant release yet. Here are some highlights: Â - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) - A new code changes management system named Epicea for easier reviewing and recovering of your code easily - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved - The PharoVM is now part of OpenSmalltalk initiative - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context - Pharo can now be bootstrapped from source code managed by Git - Pharo modularity is improved - Pharo is faster - The Dark Theme was improved and set as default color theme of Pharo Â Â These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change… Â While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. Â Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: Â Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk Â (If you contributed with Pharo 6.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[http://pharo.org/download] Learn Pharo: http://pharo.org/documentation[http://pharo.org/documentation]

June 6, 2017

Re: [Pharo-users] [ANN] Pharo 6.0 released!

by Hilaire

Congratulations ! Le 06/06/2017 Ã 17:11, Esteban Lorenzano a Ã©crit : > The time has come for Pharo 6.0! > -- Dr. Geo http://drgeo.eu

June 6, 2017