April 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo 3.0 Released!

by Sven Van Caekenberghe

On 30 Apr 2014, at 22:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: > It means that we are so happy that CodeCity is built in Pharo and that we can draw Pharo so beautifully from within Pharo. The same applies for Roassal :) Hear, hear ! Indeed: the fact that Pharo is written in Pharo, with accessible and friendly source code, is one of those unique aspects - we take it for granted and don't think about it, but it is actually a very big deal.

April 30, 2014

Re: [Pharo-users] Pharo 3.0 Released!

by Tudor Girba

Hi, It means that we are so happy that CodeCity is built in Pharo and that we can draw Pharo so beautifully from within Pharo. The same applies for Roassal :) Doru On Wed, Apr 30, 2014 at 5:51 PM, Richard Wettel <wettel(a)gmail.com> wrote: > Congratulations to the big Pharo family! > Ricky > P.S. What does "built with Pharo for Pharo" mean? > â > Sent from Mailbox <https://www.dropbox.com/mailbox> > > > On Wed, Apr 30, 2014 at 4:02 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> Dear World, >> >> Pharo 3.0 (http://www.pharo.org) is here. >> >> <pastedGraphic.png> >> >> The past year seemed short as we got busy building more than usual. Many >> things have changed in Pharo. Here are the highlights: >> - The new modular Opal compiler is now the default compiler used in the >> system. >> - The Athens vector graphics canvas is now integrated and it supports >> Cairo rendering on all platforms. >> - Many tools have been rewritten using Spec, a new framework for building >> user interfaces. >> - Versionner and Kommiter are two of the new development tools. >> - RPackage, a new package mechanism got enhanced with tags and is fully >> integrated in the system. >> - The debugger model was rewritten to become modular, the inspector >> received a bump to support multiple views, and the Nautilus code browser >> supports tags, search and lot more improvements. >> - Morphic has seen many cleanings and improvements and the visual theme >> has been revamped. >> >> These are just the more prominent highlights, but the details are just as >> important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues >> in Pharo 2). Take a moment to go through a more detailed recount of the >> progress: >> >> >> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md >> >> Pharo is improving on many fronts. Just take a look at the code city of >> Pharo (built with Pharo for Pharo). Every building is a class, and the red >> bricks represent the modified methods in Pharo 3. >> >> <pastedGraphic_1.png> >> >> Many things are changing but the system gets more stable. Moving from >> Pharo 2 to Pharo 3 is almost a matter of just loading the code. >> >> Remember that Pharo is your platform. We thank all the contributors of >> this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment >> Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, >> Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, >> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo >> Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del >> Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, >> Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo >> Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo >> Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale >> Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, >> Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, >> Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego >> Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto >> Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas >> Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas >> Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, >> Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval >> Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, >> Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan >> Wilkinson. >> And many many more who contributed indirectly, by reporting bugs, >> participating in discussion threads, providing feedback... >> >> Pharo 3.0 is the largest step we took since we started. Yet, itâs just a >> step. Expect more. Much more. >> >> Enjoy! >> The Pharo Team >> > > -- www.tudorgirba.com "Every thing has its own flow"

April 30, 2014

Re: [Pharo-users] [Vm-dev] Pharo 3.0 Released!

by Tudor Girba

Every once in a while, many little pieces come together and reveal a great puzzle. This is one of those moments. Fantastic work, everyone! Doru On Wed, Apr 30, 2014 at 4:01 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > > Dear World, > > Pharo 3.0 (http://www.pharo.org) is here. > > [image: pastedGraphic.png] > > The past year seemed short as we got busy building more than usual. Many > things have changed in Pharo. Here are the highlights: > - The new modular Opal compiler is now the default compiler used in the > system. > - The Athens vector graphics canvas is now integrated and it supports > Cairo rendering on all platforms. > - Many tools have been rewritten using Spec, a new framework for building > user interfaces. > - Versionner and Kommiter are two of the new development tools. > - RPackage, a new package mechanism got enhanced with tags and is fully > integrated in the system. > - The debugger model was rewritten to become modular, the inspector > received a bump to support multiple views, and the Nautilus code browser > supports tags, search and lot more improvements. > - Morphic has seen many cleanings and improvements and the visual theme > has been revamped. > > These are just the more prominent highlights, but the details are just as > important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues > in Pharo 2). Take a moment to go through a more detailed recount of the > progress: > > > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md > > Pharo is improving on many fronts. Just take a look at the code city of > Pharo (built with Pharo for Pharo). Every building is a class, and the red > bricks represent the modified methods in Pharo 3. > > [image: pastedGraphic_1.png] > > Many things are changing but the system gets more stable. Moving from > Pharo 2 to Pharo 3 is almost a matter of just loading the code. > > Remember that Pharo is your platform. We thank all the contributors of > this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment > Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, > Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, > Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo > Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del > Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, > Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo > Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo > Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale > Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, > Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, > Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego > Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto > Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas > Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas > Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, > Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval > Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, > Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan > Wilkinson. > And many many more who contributed indirectly, by reporting bugs, > participating in discussion threads, providing feedback... > > Pharo 3.0 is the largest step we took since we started. Yet, itâs just a > step. Expect more. Much more. > > Enjoy! > The Pharo Team > > -- www.tudorgirba.com "Every thing has its own flow"

April 30, 2014

Pharo 3 minor issue

by giorgio ferraris

Hi, started looking at Pharo after many years. First of all, you all did an awesome works, thank you! There is a small problems on System Browser open image open system browser choose one class select group The class side checkbox is enabled, if you check it, you get a wall bak . Giorgio [image: Inline image 2]

April 30, 2014

Re: [Pharo-users] iStoa, some news

by Alain Busser

Hi, I just tested it and I did not win all the games (my score is only 1700!). For the 3rd game, instead of "select or deselect" maybe you should write "select and deselect", because if some fruits are not selected, they are not counted as deselected: â I thought that only choosing 4 of the apples would yield a good result, but it is not the case. The second activity reminds me of one that I made, about fractions: https://dl.dropboxusercontent.com/u/10996692/englishFractions.html I plan to transform it into something very similar to yours (but with CSS effects). For this activity at least, an Android version would be great, if you consider hox easy very young children use a mobile, compared to a laptop... Alain On Sun, Apr 27, 2014 at 10:35 PM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > Hi, > > I have been working on iStoa lately (http://launchpad.net/istoa) > Few screenshot enclosed, hope for another alpha release soon. > > Thanks > > Hilaire > > > -- > Dr. Geo http://drgeo.eu >

April 30, 2014

Re: [Pharo-users] Pharo 3.0 Released!

by Richard Wettel

Congratulations to the big Pharo family! Ricky P.S. What does "built with Pharo for Pharo" mean? â Sent from Mailbox On Wed, Apr 30, 2014 at 4:02 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Dear World, > Pharo 3.0 (http://www.pharo.org) is here. > The past year seemed short as we got busy building more than usual. Many things have changed in Pharo. Here are the highlights: > - The new modular Opal compiler is now the default compiler used in the system. > - The Athens vector graphics canvas is now integrated and it supports Cairo rendering on all platforms. > - Many tools have been rewritten using Spec, a new framework for building user interfaces. > - Versionner and Kommiter are two of the new development tools. > - RPackage, a new package mechanism got enhanced with tags and is fully integrated in the system. > - The debugger model was rewritten to become modular, the inspector received a bump to support multiple views, and the Nautilus code browser supports tags, search and lot more improvements. > - Morphic has seen many cleanings and improvements and the visual theme has been revamped. > These are just the more prominent highlights, but the details are just as important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues in Pharo 2). Take a moment to go through a more detailed recount of the progress: > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md > Pharo is improving on many fronts. Just take a look at the code city of Pharo (built with Pharo for Pharo). Every building is a class, and the red bricks represent the modified methods in Pharo 3. > Many things are changing but the system gets more stable. Moving from Pharo 2 to Pharo 3 is almost a matter of just loading the code. > Remember that Pharo is your platform. We thank all the contributors of this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan Wilkinson. > And many many more who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... > Pharo 3.0 is the largest step we took since we started. Yet, itâs just a step. Expect more. Much more. > Enjoy! > The Pharo Team

April 30, 2014

Re: [Pharo-users] [Pharo-dev] Pharo 3.0 Released!

by Johan Fabry

And a big +1 on that! On Apr 30, 2014, at 11:01 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Today is a great day ! > > I am really proud to be part of this community and thankful for the contributions and hard work of so many people. > > This is a very important milestone while the future looks even brighter. > > Sven > > On 30 Apr 2014, at 16:01, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Dear World, >> >> Pharo 3.0 (http://www.pharo.org) is here. >> >> <pastedGraphic.png> >> >> The past year seemed short as we got busy building more than usual. Many things have changed in Pharo. Here are the highlights: >> - The new modular Opal compiler is now the default compiler used in the system. >> - The Athens vector graphics canvas is now integrated and it supports Cairo rendering on all platforms. >> - Many tools have been rewritten using Spec, a new framework for building user interfaces. >> - Versionner and Kommiter are two of the new development tools. >> - RPackage, a new package mechanism got enhanced with tags and is fully integrated in the system. >> - The debugger model was rewritten to become modular, the inspector received a bump to support multiple views, and the Nautilus code browser supports tags, search and lot more improvements. >> - Morphic has seen many cleanings and improvements and the visual theme has been revamped. >> >> These are just the more prominent highlights, but the details are just as important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues in Pharo 2). Take a moment to go through a more detailed recount of the progress: >> >> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md >> >> Pharo is improving on many fronts. Just take a look at the code city of Pharo (built with Pharo for Pharo). Every building is a class, and the red bricks represent the modified methods in Pharo 3. >> >> <pastedGraphic_1.png> >> >> Many things are changing but the system gets more stable. Moving from Pharo 2 to Pharo 3 is almost a matter of just loading the code. >> >> Remember that Pharo is your platform. We thank all the contributors of this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan Wilkinson. >> And many many more who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... >> >> Pharo 3.0 is the largest step we took since we started. Yet, itâs just a step. Expect more. Much more. >> >> Enjoy! >> The Pharo Team > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

April 30, 2014

Re: [Pharo-users] New Website online

by Johan Fabry

Slick! Congrats on the site. On Apr 30, 2014, at 10:26 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > The new website is online! > > http://pharo.org > > For now, pharo-project.org still is the old website. > Next: pharo-project.org should forward to pharo.org, > it will still be available as old.pharo-project.org for some time. > > Thanks a lot to > Nico http://nicolas-petton.fr, > Esteban http://smallworks.eu, > Damien http://damiencassou.seasidehosting.st > and Aurelia http://aurelia.saout.fr > > > Marcus > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

April 30, 2014

Re: [Pharo-users] Right-click and tutorial

by Esteban Lorenzano

On 30 Apr 2014, at 17:01, Ben Coman <btc(a)openInWorld.com> wrote: > Its nice to be inspiring ;) Thanks for having a go at it. I'm interested in what you came up with but I am tied up till the weekend. I'll have a look then. no, thanks you for taking the time and correct our mistakes (or enhance our not-so-good explanations) :) cheers, Esteban > cheers -ben > > Sven Van Caekenberghe wrote: >> >> Hi Ben, >> >> I hacked a bit on this today, inspired by your lead: >> >> https://pharo.fogbugz.com/f/cases/13201/Hard-to-start-a-tutorial-in-Pharo >> >> === >> Name: SLICE-Issue-13201-SLICE-Issue-13201-Hard-to-start-a-tutorial-in-Pharo-SvenVanCaekenberghe.1 >> Author: SvenVanCaekenberghe >> Time: 30 April 2014, 4:49:11.694825 pm >> UUID: 02f94c7a-1998-4364-a7d8-ddbe4c5c3973 >> Ancestors: >> Dependencies: HelpSystem-Core-SvenVanCaekenberghe.109, ProfStef-Core-SvenVanCaekenberghe.37 >> >> Improve the user experience of running the Pharo[Syntax]Tutorial aka ProfStef by: >> >> - adding a simplified (do it/print it/inspect it) menu to the HelpBrowser contents view >> - adding inspect it to the LessonView menu >> - adding a lesson about inspection, PharoSyntaxTutorial>>#inspecting >> - change the doing/printing/inspecting lesson titles >> - make PharoTutorial/ProfStef #next and #previous work for both the standalone LessonView and the tree based HelpBrowser (apart and together) without opening a new one >> - make HelpBrowser>>#onItemClicked: deselect in the text view >> >> This needs a review; some hacking was involved. >> === >> >> Sven >> >> On 30 Apr 2014, at 12:43, Ben Coman <btc(a)openInWorld.com> wrote: >> >> >>> Sven Van Caekenberghe wrote: >>> >>>> Ben, >>>> >>>> He is right, it is a problem when you go to the tutorial via the Browse tutorial tool: >>>> >>>> And yes there is already an issue but it was temporary closed because the welcome space's first expression helps a bit. >>>> >>> I had a little look at it. I naively tried... >>> HelpBrowser>>initWindow >>> contentMorph := self defaultViewerClass on: self >>> text: nil >>> accept: nil >>> readSelection: nil >>> menu: #codePaneMenu:shifted:. "<--replaces nil" >>> >>> HelpBrowser>>codePaneMenu: aMenu >>> ^ aMenu addAllFrom: SmalltalkEditor yellowButtonMenu >>> >>> But while it shows a menu, the DoIt opens a new window rather than changing the text in the help browser. Digging further, HelpBrowser >> helpTopic eventually uses PharoTutorialHelpTutorialBuilder to convert Lessons into HelpTopics - and so with the current architecture there seems not possible for the #next sent to PharoTutorial to change the HelpTopic displayed in the HelpBrowser. >>> >>> The options I can guess are: >>> 1. Strip the "PharoTutorial next" from the bottom of each lesson and have the LessonView >> showLesson:withTitle: append "PharoTutorial next" to the text of each Lesson. >>> 2. Lessons are not converted to HelpTopics. Instead use or wrap PharoTutorial directly and link its #lessonView: to the HelpBrowser somehow. >>> 3. Somehow use announcements. >>> >>> cheers -ben >>> >>>> On 30 Apr 2014, at 07:43, Ben Coman <btc(a)openInWorld.com> wrote: >>>> >>>> >>>>> David Harris wrote: >>>>> >>>>>> I reported a problem with the mouse right-click under Windows 7 last January and the 30845 update still exhibits the same behavior. >>>>>> >>>>>> Selected Pharo Tutorials from the World menu. Expanded Pharo Syntax Tutorial. Clicked Welcome. Highlighted 'PharoTutorial next.' Right-click of mouse does nothing. Fortunately, Alt-D does perform the do-it action. Once the new tutorial window opens, then right-click works as advertised. It is just that first panel where it is non-functional. Unfortunately, that panel tells the user "right-click and choose 'do it (d)'" >>>>>> >>>>> That is strange, it works for me on Windows 7 Home Premium SP1 64-bit with freshly downloaded VM+image >>>>> I did this... >>>>> 1. Downloaded and unzipped http://files.pharo.org/platform/Pharo3.0-win.zip (dated 2014-04-29). >>>>> 2. Double clicked pharo.exe >>>>> 3. World Menu > System > System Reporter >>>>> 4. In Welcome, highlighted "PharoTutorial go" > right-click > Do it >>>>> 5. In Tutorial, highlighted "PharoTutorial next" > right-click ---> took the attached snapshot >>>>> >>>>> cheers -ben >>>>> >>>>> btw do you have the case number? >>>>> <PharoTutorial-right-click.png> >>>>> >> >> >> >> >

April 30, 2014

Re: [Pharo-users] [Pharo-dev] Pharo 3.0 Released!

by Sven Van Caekenberghe

We need more votes & comments to get to the front page ! On 30 Apr 2014, at 16:27, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > https://news.ycombinator.com/item?id=7673462 > > On 30 Apr 2014, at 16:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> and is also at ycombinator >> >> thumbs up! >> >> Esteban >> >> >> On 30 Apr 2014, at 16:14, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> reddit: >>> >>> http://www.reddit.com/r/programming/comments/24d9d2/pharo_30_the_immersive_… >>> >>> >>> On 30 Apr 2014, at 16:01, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> Dear World, >>>> >>>> Pharo 3.0 (http://www.pharo.org) is here. >>>> >>>> <pastedGraphic.png> >>>> >>>> The past year seemed short as we got busy building more than usual. Many things have changed in Pharo. Here are the highlights: >>>> - The new modular Opal compiler is now the default compiler used in the system. >>>> - The Athens vector graphics canvas is now integrated and it supports Cairo rendering on all platforms. >>>> - Many tools have been rewritten using Spec, a new framework for building user interfaces. >>>> - Versionner and Kommiter are two of the new development tools. >>>> - RPackage, a new package mechanism got enhanced with tags and is fully integrated in the system. >>>> - The debugger model was rewritten to become modular, the inspector received a bump to support multiple views, and the Nautilus code browser supports tags, search and lot more improvements. >>>> - Morphic has seen many cleanings and improvements and the visual theme has been revamped. >>>> >>>> These are just the more prominent highlights, but the details are just as important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues in Pharo 2). Take a moment to go through a more detailed recount of the progress: >>>> >>>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md >>>> >>>> Pharo is improving on many fronts. Just take a look at the code city of Pharo (built with Pharo for Pharo). Every building is a class, and the red bricks represent the modified methods in Pharo 3. >>>> >>>> <pastedGraphic_1.png> >>>> >>>> Many things are changing but the system gets more stable. Moving from Pharo 2 to Pharo 3 is almost a matter of just loading the code. >>>> >>>> Remember that Pharo is your platform. We thank all the contributors of this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan Wilkinson. >>>> And many many more who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... >>>> >>>> Pharo 3.0 is the largest step we took since we started. Yet, itâs just a step. Expect more. Much more. >>>> >>>> Enjoy! >>>> The Pharo Team >>> >> >

April 30, 2014