- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core

May 13, 2016

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

by Dimitris Chloupis

our baby is growing up , aaaaah how cute :) great works parents , keep rocking On Fri, May 13, 2016 at 11:20 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 13 May 2016, at 09:33, stepharo <stepharo(a)free.fr> wrote: > > > > I want to particularly thanks esteban and marcus for this release. > > Yes ! > > > Thank you guys for making Pharo what it is. > > > > Then I want to thank all the contributors for their continuous support. > > Yes, yes ! > > > Stef > > > > > > Le 12/5/16 Ã 17:49, Esteban Lorenzano a Ã©crit : > >> Hi, > >> > >> Please spread widely, and sorry for multiple posts. > >> (this post can be see here: http://pharo.org/news/pharo-5.0-released) > >> > >> Dear World, > >> > >> The time has come for Pharo 5.0! > >> > >> <Mail Attachment.png> > >> > >> This is our most significant release yet. Here are some highlights: > >> > >> - The PharoVM is now based on Spur, the new memory management, and it > brings with it a 35% speedup! > >> - A new unified foreign function interface (UFFI) replaced NativeBoost > to provide a strong Spur-compatible framework for interfacing with the > outside world. > >> - The Glamorous Toolkit now includes the GTDebugger to offer a moldable > infrastructure that allows the developer to customize the debugger deeply. > >> - The underlying Reflectivity mechanism has reached maturity with > multiple pieces coming together to empower developers to instrument their > own systems. For example, we now have breakpoints implemented as just a > simple extension of this mechanism. > >> - QualityAssistant is now part of the image to provide live feedback > during development. > >> > >> These are just the more prominent highlights, but the details are just > as important. We have closed 2446 issues in Pharo 5. Take a moment to go > through a more detailed recount of the progress: > https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo50Change… > . > >> > >> While the technical improvements are significant, just think of getting > 30% faster out-of-the-box, still the most impressive fact is that the new > code that got in the main Pharo 5.0 image was contributed by 100 people. > Together we have touched 43% of the classes, and 20% of the methods. The > following visualization rendered with Roassal in Pharo 5.0 is dedicated to > this effort. The picture shows the touched classes and packages in gray, > the authors and the links to the changed classes in red, and, using an > automatically generated visual id, you can spot authors that have worked on > similar projects. > >> > >> > >> <Mail Attachment.png> > >> > >> Pharo is more than code. It is an exciting project involving energetic > people. We thank all the contributors of this release: > >> > >> Abdelghani Alidra, Clara Allende, David Allouche, Nicolas Anquetil, > Thibault Arloing, Jean Baptiste Arnaud, Mangesh Bendre, Clement Bera, > Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, > Johan Brichau, Camillo Bruni, Miguel Campusano, Damien Cassou, Nicolas > Cellier, Danny Chan, Andrei Chis, Christopher Coat, Ben Coman, > Bernardo Contreras, Gabriel Omar Cotelli, Tommaso Dal Sasso, Paul De > Bruicker, Sean De Nigris, Christophe Demarey, Simon Denier, Marcus > Denker, Martin Dias, John Dougan, Stephane Ducasse, Stephan Eggermont, > Johan Fabry, Sergio Fedi, Cyril Ferlicot, Holger Hans Peter Freyther, > Joshua Gargus, Tudor Girba, Thierry Goubier, Kris Gybels, Norbert > Hartl, Thomas Heniart, Dale Henrichs, Nicolai Hess, Alejandro Infante, > Henrik Johansen, Goran Krampe, Pavel Krivanek, Juraj Kubelka, Denis > Kudriashov, Matthieu Lacaton, Laurent Laffont, Kevin Lanvin, Jannik > Laval, Alexander LazareviÄ, Skip Lentz, Max Leske, Dave Lewis, Esteban > Lorenzano, Sheridan Mahoney, Mariano Martinez Peck, Max Mattone, John > McIntosh, Rene Meusel, Eliot Miranda, Henrik Nergaard, Marion > Noirbent, Merwan Ouddane, Nick Papoulias, Nicolas Passerini, Alain > Plantec, Guillermo Polito, Damien Pollet, Baptiste Quide, Andreas Raab > (RIP), Alain Rastoul, Stefan Reichhart, Lukas Renggli, Mark Rizun, > Michael Rueger, Valentin Ryckewaert, Ronie Salgado, Udo Schneider, > Boris Spasojevic, Igor Stasenko, Roger Stebler, Serge Stinckwich, > Aliaksei Syrel, Camille Teruel, Pablo Tesone, Yuriy Tymchuk, Peter > Uhnak, Masashi Umezawa, Dion Stewart, Sven Van Caekenberghe, Jan Van De > Sandt, Benjamin Van Ryseghem, Toon Verwaest, Franck Warlouzet. > >> > >> (If you contributed with Pharo 5.0 development in any way and we missed > your name, please send us a mail and we will add you). > >> > >> Enjoy! > >> The Pharo Team > >> > >> > > > > > > >

May 13, 2016

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

by Sven Van Caekenberghe

> On 13 May 2016, at 09:33, stepharo <stepharo(a)free.fr> wrote: > > I want to particularly thanks esteban and marcus for this release. Yes ! > Thank you guys for making Pharo what it is. > > Then I want to thank all the contributors for their continuous support. Yes, yes ! > Stef > > > Le 12/5/16 Ã 17:49, Esteban Lorenzano a Ã©crit : >> Hi, >> >> Please spread widely, and sorry for multiple posts. >> (this post can be see here: http://pharo.org/news/pharo-5.0-released) >> >> Dear World, >> >> The time has come for Pharo 5.0! >> >> <Mail Attachment.png> >> >> This is our most significant release yet. Here are some highlights: >> >> - The PharoVM is now based on Spur, the new memory management, and it brings with it a 35% speedup! >> - A new unified foreign function interface (UFFI) replaced NativeBoost to provide a strong Spur-compatible framework for interfacing with the outside world. >> - The Glamorous Toolkit now includes the GTDebugger to offer a moldable infrastructure that allows the developer to customize the debugger deeply. >> - The underlying Reflectivity mechanism has reached maturity with multiple pieces coming together to empower developers to instrument their own systems. For example, we now have breakpoints implemented as just a simple extension of this mechanism. >> - QualityAssistant is now part of the image to provide live feedback during development. >> >> These are just the more prominent highlights, but the details are just as important. We have closed 2446 issues in Pharo 5. Take a moment to go through a more detailed recount of the progress: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo50Change…. >> >> While the technical improvements are significant, just think of getting 30% faster out-of-the-box, still the most impressive fact is that the new code that got in the main Pharo 5.0 image was contributed by 100 people. Together we have touched 43% of the classes, and 20% of the methods. The following visualization rendered with Roassal in Pharo 5.0 is dedicated to this effort. The picture shows the touched classes and packages in gray, the authors and the links to the changed classes in red, and, using an automatically generated visual id, you can spot authors that have worked on similar projects. >> >> >> <Mail Attachment.png> >> >> Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: >> >> Abdelghani Alidra, Clara Allende, David Allouche, Nicolas Anquetil, Thibault Arloing, Jean Baptiste Arnaud, Mangesh Bendre, Clement Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Johan Brichau, Camillo Bruni, Miguel Campusano, Damien Cassou, Nicolas Cellier, Danny Chan, Andrei Chis, Christopher Coat, Ben Coman, Bernardo Contreras, Gabriel Omar Cotelli, Tommaso Dal Sasso, Paul De Bruicker, Sean De Nigris, Christophe Demarey, Simon Denier, Marcus Denker, Martin Dias, John Dougan, Stephane Ducasse, Stephan Eggermont, Johan Fabry, Sergio Fedi, Cyril Ferlicot, Holger Hans Peter Freyther, Joshua Gargus, Tudor Girba, Thierry Goubier, Kris Gybels, Norbert Hartl, Thomas Heniart, Dale Henrichs, Nicolai Hess, Alejandro Infante, Henrik Johansen, Goran Krampe, Pavel Krivanek, Juraj Kubelka, Denis Kudriashov, Matthieu Lacaton, Laurent Laffont, Kevin Lanvin, Jannik Laval, Alexander LazareviÄ, Skip Lentz, Max Leske, Dave Lewis, Esteban Lorenzano, Sheridan Mahoney, Mariano Martinez Peck, Max Mattone, John McIntosh, Rene Meusel, Eliot Miranda, Henrik Nergaard, Marion Noirbent, Merwan Ouddane, Nick Papoulias, Nicolas Passerini, Alain Plantec, Guillermo Polito, Damien Pollet, Baptiste Quide, Andreas Raab (RIP), Alain Rastoul, Stefan Reichhart, Lukas Renggli, Mark Rizun, Michael Rueger, Valentin Ryckewaert, Ronie Salgado, Udo Schneider, Boris Spasojevic, Igor Stasenko, Roger Stebler, Serge Stinckwich, Aliaksei Syrel, Camille Teruel, Pablo Tesone, Yuriy Tymchuk, Peter Uhnak, Masashi Umezawa, Dion Stewart, Sven Van Caekenberghe, Jan Van De Sandt, Benjamin Van Ryseghem, Toon Verwaest, Franck Warlouzet. >> >> (If you contributed with Pharo 5.0 development in any way and we missed your name, please send us a mail and we will add you). >> >> Enjoy! >> The Pharo Team >> >> > >

May 13, 2016

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

by stepharo

I want to particularly thanks esteban and marcus for this release. Thank you guys for making Pharo what it is. Then I want to thank all the contributors for their continuous support. Stef Le 12/5/16 Ã 17:49, Esteban Lorenzano a Ã©crit : > Hi, > Please spread widely, and sorry for multiple posts. > (this post can be see here: http://pharo.org/news/pharo-5.0-released) > > Dear World, > > The time has come for *Pharo 5.0*! > > > This is our most significant release yet. Here are some highlights: > > - The PharoVM is now based on Spur, the new memory management, and it > brings with it a 35% speedup! > - A new unified foreign function interface (UFFI) replaced NativeBoost > to provide a strong Spur-compatible framework for interfacing with the > outside world. > - The Glamorous Toolkit now includes the GTDebugger to offer a > moldable infrastructure that allows the developer to customize the > debugger deeply. > - The underlying Reflectivity mechanism has reached maturity with > multiple pieces coming together to empower developers to instrument > their own systems. For example, we now have breakpoints implemented as > just a simple extension of this mechanism. > - QualityAssistant is now part of the image to provide live feedback > during development. > > These are just the more prominent highlights, but the details are just > as important. We have closed 2446 issues in Pharo 5. Take a moment to > go through a more detailed recount of the progress: > https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo50Change…. > > While the technical improvements are significant, just think of > getting 30% faster out-of-the-box, still the most impressive fact is > that the new code that got in the main Pharo 5.0 image was contributed > by 100 people. Together we have touched 43% of the classes, and 20% of > the methods. The following visualization rendered with Roassal in > Pharo 5.0 is dedicated to this effort. The picture shows the touched > classes and packages in gray, the authors and the links to the changed > classes in red, and, using an automatically generated visual id, you > can spot authors that have worked on similar projects. > > > > Pharo is more than code. It is an exciting project involving energetic > people. We thank all the contributors of this release: > > Abdelghani Alidra, Clara Allende, David Allouche, Nicolas Anquetil, > Thibault Arloing, Jean Baptiste Arnaud, Mangesh Bendre, Clement > Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent > Blondeau, Johan Brichau, Camillo Bruni, Miguel Campusano, Damien > Cassou, Nicolas Cellier, Danny Chan, Andrei Chis, Christopher > Coat, Ben Coman, Bernardo Contreras, Gabriel Omar Cotelli, Tommaso > Dal Sasso, Paul De Bruicker, Sean De Nigris, Christophe Demarey, > Simon Denier, Marcus Denker, Martin Dias, John Dougan, Stephane > Ducasse, Stephan Eggermont, Johan Fabry, Sergio Fedi, Cyril > Ferlicot, Holger Hans Peter Freyther, Joshua Gargus, Tudor Girba, > Thierry Goubier, Kris Gybels, Norbert Hartl, Thomas Heniart, Dale > Henrichs, Nicolai Hess, Alejandro Infante, Henrik Johansen, Goran > Krampe, Pavel Krivanek, Juraj Kubelka, Denis Kudriashov, Matthieu > Lacaton, Laurent Laffont, Kevin Lanvin, Jannik Laval, Alexander > LazareviÄ, Skip Lentz, Max Leske, Dave Lewis, Esteban Lorenzano, > Sheridan Mahoney, Mariano Martinez Peck, Max Mattone, John > McIntosh, Rene Meusel, Eliot Miranda, Henrik Nergaard, Marion > Noirbent, Merwan Ouddane, Nick Papoulias, Nicolas Passerini, Alain > Plantec, Guillermo Polito, Damien Pollet, Baptiste Quide, Andreas > Raab (RIP), Alain Rastoul, Stefan Reichhart, Lukas Renggli, Mark > Rizun, Michael Rueger, Valentin Ryckewaert, Ronie Salgado, Udo > Schneider, Boris Spasojevic, Igor Stasenko, Roger Stebler, Serge > Stinckwich, Aliaksei Syrel, Camille Teruel, Pablo Tesone, Yuriy > Tymchuk, Peter Uhnak, Masashi Umezawa, Dion Stewart, Sven Van > Caekenberghe, Jan Van De Sandt, Benjamin Van Ryseghem, Toon > Verwaest, Franck Warlouzet. > > (If you contributed with Pharo 5.0 development in any way and we > missed your name, please send us a mail and we will add you). > > Enjoy! > The Pharo Team > >

May 13, 2016

Re: [Pharo-dev] Easier way to parse this?

by Denis Kudriashov

Hi. I always solve such kind of problems with streams. It is super easy and much easy then regex (I hate regex). For your case it would be something like: in := source readStream. result := String streamContents: [:out | [in atEnd] whileFalse: [ out nextPutAll: (in upToAll: '<code>'). code := in upToAll: '</code>'. out nextPutAll: code asUppercase; nextPutAll: '</code>']. ] And it could be much nicer with Xtreams but I not remember it API (maybe tomorrow I will remember). 2016-05-12 21:50 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi guys, > > I wonder which is the easier way to do the following. I have a string > which inside could have something like 'this is a string with <code>some > funny lines</code> and here is another <code>haha</code>'. I need to parse > that string, get all places where I have things surrounded with > <code>SOMETHING</code>, get the "SOMETHING" (in previous example, that > would be 'some funny lines'), execute that (this is something internal) , > and from that I get the real string (imagine in this case the answer is > 'SOME FUNNY LINES'). Finally, I need to replace the orignal string... So > ... given the input: > > 'this is a string with <code>some funny lines</code> and here is another > <code>haha</code>' > > And given my specific domain logic transformation (in this example I > assume a simple #asUppercase), I would like to get: > > 'this is a string with SOME FUNNY LINES and here is another HAHA' > > I got it working with below lines. But it is a hack and terrible slow (I > imagine). > So...anyone has an idea how can I do this simpler/faster? Maybe some RB > re-write rule? > > Thanks in advance > > > > | dom string originalString stringToBeAbleToParse xmlDocument replacements > finalString | > replacements := Dictionary new. > originalString := 'this is a string with <code>some funny lines</code> and > here is another <code>haha</code>'. > stringToBeAbleToParse := '<hack>', originalString, '</hack>'. > dom := XMLDOMParser on: stringToBeAbleToParse. > dom configuration isValidating: false. > xmlDocument := dom parseDocument. > (xmlDocument allElementsNamed: 'code') do: [ :aXMLElement | > > "Let's simulate my domain transformation logic as a simple > #asUppercase" > replacements at: aXMLElement asString put: (([:code | code asUppercase ]) > value: aXMLElement nodes first asString). > ]. > finalString := originalString. > replacements keysAndValuesDo: [ :originalText :new | > finalString := finalString copyReplaceAll: originalText with: new. > ]. > finalString > > > > > -- > Mariano > http://marianopeck.wordpress.com >

May 12, 2016

Re: [Pharo-dev] Easier way to parse this?

by Alistair Grant

Hi Mariano, On Thu, May 12, 2016 at 04:50:29PM -0300, Mariano Martinez Peck wrote: > Hi guys, > > I wonder which is the easier way to do the following. I have a string which > inside could have something likeÂ Â 'this is a string with <code>some funny lines > </code> and here is another <code>haha</code>'. I need to parse that string, > get all places where I have things surrounded with <code>SOMETHING</code>, get > the "SOMETHING" (in previous example, that would be 'some funny lines'), > execute that (this is something internal) , and from that I get the real string > (imagine in this case the answer is 'SOME FUNNY LINES'). Finally, I need to > replace the orignal string... So ... given the input: > > 'this is a string with <code>some funny lines</code> and here is another <code> > haha</code>' > > And given my specific domain logic transformation (in this example I assume a > simple #asUppercase), I would like to get: > > Â 'this is a string with SOME FUNNY LINES and here is another HAHA' > > I got it working with below lines. But it is a hack and terrible slow (I > imagine).Â > So...anyone has an idea how can I do this simpler/faster? Maybe some RB > re-write rule? > > Thanks in advance > > > > | dom string originalString stringToBeAbleToParse xmlDocument replacements > finalString | > replacements := Dictionary new.Â > originalString := 'this is a string with <code>some funny lines</code> and here > is another <code>haha</code>'. > stringToBeAbleToParse := '<hack>', originalString, '</hack>'. > dom := XMLDOMParser on: stringToBeAbleToParse.Â > dom configuration isValidating: false.Â > xmlDocument := dom parseDocument. > (xmlDocument allElementsNamed: 'code') do: [ :aXMLElement | > > Â Â Â Â "Let's simulate my domain transformation logic as a simple # > asUppercase" > replacements at: aXMLElement asString put: (([:code | code asUppercase ]) > value: aXMLElement nodes first asString).Â > ]. > finalString := originalString. > replacements keysAndValuesDo: [ :originalText :new | > finalString := finalString copyReplaceAll: originalText with: new. > ]. > finalString I don't think this is quite what you want, but it should be close enough to get you started: | str re oc | str := 'this is a string with <code>some funny lines</code> and here is another <code>haha</code>'. re := '<code>([^<]*)</code>' asRegex. re copy: str translatingMatchesUsing: [ :each | each asUppercase]. HTH, Alistair

May 12, 2016

Easier way to parse this?

by Mariano Martinez Peck

Hi guys, I wonder which is the easier way to do the following. I have a string which inside could have something like 'this is a string with <code>some funny lines</code> and here is another <code>haha</code>'. I need to parse that string, get all places where I have things surrounded with <code>SOMETHING</code>, get the "SOMETHING" (in previous example, that would be 'some funny lines'), execute that (this is something internal) , and from that I get the real string (imagine in this case the answer is 'SOME FUNNY LINES'). Finally, I need to replace the orignal string... So ... given the input: 'this is a string with <code>some funny lines</code> and here is another <code>haha</code>' And given my specific domain logic transformation (in this example I assume a simple #asUppercase), I would like to get: 'this is a string with SOME FUNNY LINES and here is another HAHA' I got it working with below lines. But it is a hack and terrible slow (I imagine). So...anyone has an idea how can I do this simpler/faster? Maybe some RB re-write rule? Thanks in advance | dom string originalString stringToBeAbleToParse xmlDocument replacements finalString | replacements := Dictionary new. originalString := 'this is a string with <code>some funny lines</code> and here is another <code>haha</code>'. stringToBeAbleToParse := '<hack>', originalString, '</hack>'. dom := XMLDOMParser on: stringToBeAbleToParse. dom configuration isValidating: false. xmlDocument := dom parseDocument. (xmlDocument allElementsNamed: 'code') do: [ :aXMLElement | "Let's simulate my domain transformation logic as a simple #asUppercase" replacements at: aXMLElement asString put: (([:code | code asUppercase ]) value: aXMLElement nodes first asString). ]. finalString := originalString. replacements keysAndValuesDo: [ :originalText :new | finalString := finalString copyReplaceAll: originalText with: new. ]. finalString -- Mariano http://marianopeck.wordpress.com

May 12, 2016

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

by Chris Muller

Congratulations! On Thu, May 12, 2016 at 10:57 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Vote up! > > Reddit: > https://www.reddit.com/r/programming/comments/4j1clo/pharo_50_the_immersive… > > YC: > https://news.ycombinator.com/item?id=11684285 > > > On 12 May 2016, at 17:49, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Please spread widely, and sorry for multiple posts. > (this post can be see here: http://pharo.org/news/pharo-5.0-released) > > Dear World, > > The time has come for Pharo 5.0! > > <pharo50-screenshot.png> > > This is our most significant release yet. Here are some highlights: > > - The PharoVM is now based on Spur, the new memory management, and it brings > with it a 35% speedup! > - A new unified foreign function interface (UFFI) replaced NativeBoost to > provide a strong Spur-compatible framework for interfacing with the outside > world. > - The Glamorous Toolkit now includes the GTDebugger to offer a moldable > infrastructure that allows the developer to customize the debugger deeply. > - The underlying Reflectivity mechanism has reached maturity with multiple > pieces coming together to empower developers to instrument their own > systems. For example, we now have breakpoints implemented as just a simple > extension of this mechanism. > - QualityAssistant is now part of the image to provide live feedback during > development. > > These are just the more prominent highlights, but the details are just as > important. We have closed 2446 issues in Pharo 5. Take a moment to go > through a more detailed recount of the progress: > https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo50Change…. > > While the technical improvements are significant, just think of getting 30% > faster out-of-the-box, still the most impressive fact is that the new code > that got in the main Pharo 5.0 image was contributed by 100 people. Together > we have touched 43% of the classes, and 20% of the methods. The following > visualization rendered with Roassal in Pharo 5.0 is dedicated to this > effort. The picture shows the touched classes and packages in gray, the > authors and the links to the changed classes in red, and, using an > automatically generated visual id, you can spot authors that have worked on > similar projects. > > > <pharo50-contributors.png> > > Pharo is more than code. It is an exciting project involving energetic > people. We thank all the contributors of this release: > > Abdelghani Alidra, Clara Allende, David Allouche, Nicolas Anquetil, > Thibault Arloing, Jean Baptiste Arnaud, Mangesh Bendre, Clement Bera, > Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, > Johan Brichau, Camillo Bruni, Miguel Campusano, Damien Cassou, Nicolas > Cellier, Danny Chan, Andrei Chis, Christopher Coat, Ben Coman, Bernardo > Contreras, Gabriel Omar Cotelli, Tommaso Dal Sasso, Paul De Bruicker, > Sean De Nigris, Christophe Demarey, Simon Denier, Marcus Denker, Martin > Dias, John Dougan, Stephane Ducasse, Stephan Eggermont, Johan Fabry, > Sergio Fedi, Cyril Ferlicot, Holger Hans Peter Freyther, Joshua Gargus, > Tudor Girba, Thierry Goubier, Kris Gybels, Norbert Hartl, Thomas > Heniart, Dale Henrichs, Nicolai Hess, Alejandro Infante, Henrik > Johansen, Goran Krampe, Pavel Krivanek, Juraj Kubelka, Denis Kudriashov, > Matthieu Lacaton, Laurent Laffont, Kevin Lanvin, Jannik Laval, Alexander > LazareviÄ, Skip Lentz, Max Leske, Dave Lewis, Esteban Lorenzano, Sheridan > Mahoney, Mariano Martinez Peck, Max Mattone, John McIntosh, Rene Meusel, > Eliot Miranda, Henrik Nergaard, Marion Noirbent, Merwan Ouddane, Nick > Papoulias, Nicolas Passerini, Alain Plantec, Guillermo Polito, Damien > Pollet, Baptiste Quide, Andreas Raab (RIP), Alain Rastoul, Stefan > Reichhart, Lukas Renggli, Mark Rizun, Michael Rueger, Valentin > Ryckewaert, Ronie Salgado, Udo Schneider, Boris Spasojevic, Igor > Stasenko, Roger Stebler, Serge Stinckwich, Aliaksei Syrel, Camille > Teruel, Pablo Tesone, Yuriy Tymchuk, Peter Uhnak, Masashi Umezawa, Dion > Stewart, Sven Van Caekenberghe, Jan Van De Sandt, Benjamin Van Ryseghem, > Toon Verwaest, Franck Warlouzet. > > (If you contributed with Pharo 5.0 development in any way and we missed your > name, please send us a mail and we will add you). > > Enjoy! > The Pharo Team > > >

May 12, 2016

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

by Esteban Lorenzano

Vote up! Reddit: https://www.reddit.com/r/programming/comments/4j1clo/pharo_50_the_immersive… YC: https://news.ycombinator.com/item?id=11684285 > On 12 May 2016, at 17:49, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > Please spread widely, and sorry for multiple posts. > (this post can be see here: http://pharo.org/news/pharo-5.0-released <http://pharo.org/news/pharo-5.0-released>) > > Dear World, > > The time has come for Pharo 5.0! > > <pharo50-screenshot.png> > > This is our most significant release yet. Here are some highlights: > > - The PharoVM is now based on Spur, the new memory management, and it brings with it a 35% speedup! > - A new unified foreign function interface (UFFI) replaced NativeBoost to provide a strong Spur-compatible framework for interfacing with the outside world. > - The Glamorous Toolkit now includes the GTDebugger to offer a moldable infrastructure that allows the developer to customize the debugger deeply. > - The underlying Reflectivity mechanism has reached maturity with multiple pieces coming together to empower developers to instrument their own systems. For example, we now have breakpoints implemented as just a simple extension of this mechanism. > - QualityAssistant is now part of the image to provide live feedback during development. > > These are just the more prominent highlights, but the details are just as important. We have closed 2446 issues in Pharo 5. Take a moment to go through a more detailed recount of the progress: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo50Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo50Change…>. > > While the technical improvements are significant, just think of getting 30% faster out-of-the-box, still the most impressive fact is that the new code that got in the main Pharo 5.0 image was contributed by 100 people. Together we have touched 43% of the classes, and 20% of the methods. The following visualization rendered with Roassal in Pharo 5.0 is dedicated to this effort. The picture shows the touched classes and packages in gray, the authors and the links to the changed classes in red, and, using an automatically generated visual id, you can spot authors that have worked on similar projects. > > > <pharo50-contributors.png> > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Abdelghani Alidra, Clara Allende, David Allouche, Nicolas Anquetil, Thibault Arloing, Jean Baptiste Arnaud, Mangesh Bendre, Clement Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Johan Brichau, Camillo Bruni, Miguel Campusano, Damien Cassou, Nicolas Cellier, Danny Chan, Andrei Chis, Christopher Coat, Ben Coman, Bernardo Contreras, Gabriel Omar Cotelli, Tommaso Dal Sasso, Paul De Bruicker, Sean De Nigris, Christophe Demarey, Simon Denier, Marcus Denker, Martin Dias, John Dougan, Stephane Ducasse, Stephan Eggermont, Johan Fabry, Sergio Fedi, Cyril Ferlicot, Holger Hans Peter Freyther, Joshua Gargus, Tudor Girba, Thierry Goubier, Kris Gybels, Norbert Hartl, Thomas Heniart, Dale Henrichs, Nicolai Hess, Alejandro Infante, Henrik Johansen, Goran Krampe, Pavel Krivanek, Juraj Kubelka, Denis Kudriashov, Matthieu Lacaton, Laurent Laffont, Kevin Lanvin, Jannik Laval, Alexander LazareviÄ, Skip Lentz, Max Leske, Dave Lewis, Esteban Lorenzano, Sheridan Mahoney, Mariano Martinez Peck, Max Mattone, John McIntosh, Rene Meusel, Eliot Miranda, Henrik Nergaard, Marion Noirbent, Merwan Ouddane, Nick Papoulias, Nicolas Passerini, Alain Plantec, Guillermo Polito, Damien Pollet, Baptiste Quide, Andreas Raab (RIP), Alain Rastoul, Stefan Reichhart, Lukas Renggli, Mark Rizun, Michael Rueger, Valentin Ryckewaert, Ronie Salgado, Udo Schneider, Boris Spasojevic, Igor Stasenko, Roger Stebler, Serge Stinckwich, Aliaksei Syrel, Camille Teruel, Pablo Tesone, Yuriy Tymchuk, Peter Uhnak, Masashi Umezawa, Dion Stewart, Sven Van Caekenberghe, Jan Van De Sandt, Benjamin Van Ryseghem, Toon Verwaest, Franck Warlouzet. > > (If you contributed with Pharo 5.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > The Pharo Team > >

May 12, 2016

Re: [Pharo-dev] taskit

by Santiago Bragagnolo

Yeah, actually I reused and worked on TaskIT2 as well, I change the model behind. Is the one i am maintaining. It's quite les ambitious for the moment, but more coherent :) http://smalltalkhub.com/#!/~sbragagnolo/TaskIT2 The only documentation i have yet is the example class and the comments :$. But if you are interested in using it I can work on that. On Mon, 25 Apr 2016 at 12:10 Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Does anyone know what is the status of the TaskIT project? > > The documentation talks about (from 2014): > > https://github.com/SquareBracketAssociates/PharoReadyForReviews/blob/master… > > But, on SmalltalkHub I see 3 projects: > http://www.smalltalkhub.com/#!/~CAR/TaskIT (created in 2014) > http://www.smalltalkhub.com/#!/~sbragagnolo/TaskIT (created in 2013) > http://www.smalltalkhub.com/#!/~sbragagnolo/TaskIT2 (created in 2015) > > Could you point me to the version that is currently maintained I would be > interested in playing with it. > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Every successful trip needs a suitable vehicle." > > > > > > >

May 12, 2016