April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] [ANN] Pharo 4.0 is released!

by phil＠highoctane.be

stef what about next tuesday? phil Le 16 avr. 2015 22:44, "stepharo" <stepharo(a)free.fr> a Ã©crit : > yes phil tell us. > > Stef > > Le 16/4/15 12:11, phil(a)highoctane.be a Ã©crit : > > > Le 16 avr. 2015 11:56, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > > > > Great job! > > > > Thank you everyone for the contributions, support and trust. > > One more out of the door. > That's great. > > Anyone interested in doing a podcast episode on this releasr? Chime in. > > Phil > > > > > Cheers, > > Doru > > > > > > On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> > >> > >> Please spread widely. > >> Sorry for multiple posts. > >> > >> (this post can be see here: http://pharo.org/news/pharo-4.0-released) > >> > >> Dear World, > >> > >> Pharo 4.0 (http://www.pharo.org) is here. > >> > >> Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > >> > >> Many things have changed in Pharo. Here are some highlights: > >> - Inspector/Playground/Spotter are new moldable development tools for > inspecting, coding and searching objects. > >> - Slots model instance variables as first class entities and enable > meta-programming on this level. > >> - ShoreLine reporter introduces a way to report system errors and > collect statistics, that we will use for future improvements > >> - Dark theme. > >> > >> These are just the more prominent highlights, but the details are just > as important. We have closed 1697 issues in Pharo 4. Take a moment to go > through a more detailed recount of the progress: > >> > >> > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > >> > >> Pharo is improving on many fronts, but one of the most prominent > changes is the addition of moldable tools for inspection and search. These > tools provide extension mechanisms that allow every object to define ways > in which it can be understood effectively. To provide an idea of the impact > of the already existing extensions, the map below shows the Pharo classes > grouped in packages, highlighting in red those parts of the system that > have at least one such custom view coming with the main distribution. The > spread of these extensions shows that moldability is powerful mechanism > that can be used in many contexts. > >> > >> > >> Remember that Pharo is your platform. We thank all the contributors of > this release: > >> > >> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe > Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, > Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, > Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei > Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, > Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane > Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, > Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, > Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, > Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max > Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot > Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, > Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, > Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian > Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, > Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin > >> > >> And all those who contributed indirectly, by reporting bugs, > participating in discussion threads, providing feedback... > >> > >> Pharo 4.0 is another big step. And, the best is yet to come. > >> > >> Enjoy! > >> The Pharo Team > >> > >> > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > >

April 16, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by stepharo

Le 16/4/15 15:29, Sean P. DeNigris a Ã©crit : > laurent laffont wrote >> Note that the pkg files are hosted at https://github.com/lolgzs/pharo-aur/ > Should we fork this under the Pharo team? IMHO it is confusing to have our > build system scattered between various repos owned by different people. What > do you think? group things please. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ANN-ArchLinux-pharo-vm-pharo-launcher-packages-tp4749… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 16, 2015

Re: [Pharo-dev] [Vm-dev] [ANN] Pharo 4.0 is released!

by stepharo

yes phil tell us. Stef Le 16/4/15 12:11, phil(a)highoctane.be a Ã©crit : > > > Le 16 avr. 2015 11:56, "Tudor Girba" <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> a Ã©crit : > > > > Great job! > > > > Thank you everyone for the contributions, support and trust. > > One more out of the door. > That's great. > > Anyone interested in doing a podcast episode on this releasr? Chime in. > > Phil > > > > > Cheers, > > Doru > > > > > > On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano > <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >> > >> > >> Please spread widely. > >> Sorry for multiple posts. > >> > >> (this post can be see here: http://pharo.org/news/pharo-4.0-released) > >> > >> Dear World, > >> > >> Pharo 4.0 (http://www.pharo.org) is here. > >> > >> Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > >> > >> Many things have changed in Pharo. Here are some highlights: > >> - Inspector/Playground/Spotter are new moldable development tools > for inspecting, coding and searching objects. > >> - Slots model instance variables as first class entities and enable > meta-programming on this level. > >> - ShoreLine reporter introduces a way to report system errors and > collect statistics, that we will use for future improvements > >> - Dark theme. > >> > >> These are just the more prominent highlights, but the details are > just as important. We have closed 1697 issues in Pharo 4. Take a > moment to go through a more detailed recount of the progress: > >> > >> > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md > >> > >> Pharo is improving on many fronts, but one of the most prominent > changes is the addition of moldable tools for inspection and search. > These tools provide extension mechanisms that allow every object to > define ways in which it can be understood effectively. To provide an > idea of the impact of the already existing extensions, the map below > shows the Pharo classes grouped in packages, highlighting in red those > parts of the system that have at least one such custom view coming > with the main distribution. The spread of these extensions shows that > moldability is powerful mechanism that can be used in many contexts. > >> > >> > >> Remember that Pharo is your platform. We thank all the contributors > of this release: > >> > >> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe > Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent > Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven > Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, > Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso > Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus > Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc > Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, > Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale > Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, > Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, > David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila > Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, > Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan > Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik > Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, > Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres > Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin > Walk, Richard Wettel, Dmitri Zagidulin > >> > >> And all those who contributed indirectly, by reporting bugs, > participating in discussion threads, providing feedback... > >> > >> Pharo 4.0 is another big step. And, the best is yet to come. > >> > >> Enjoy! > >> The Pharo Team > >> > >> > > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Every thing has its own flow" >

April 16, 2015

Re: [Pharo-dev] Shorter Pharo Launcher download link

by Jean-Christophe Bach

* Damien Cassou <damien.cassou(a)inria.fr> [16.04.2015. @17:13:45 +0200]: > > Sean P. DeNigris <sean(a)clipperadams.com> writes: > > > Thanks for the clarification! Where are the Nix and Gentoo infrastructure > > hosted? I think we should collect all of these things under github/pharo > > for Nix, this is in the nixpkgs repository: > https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/pharo > > for Gentoo, it seems that several people contributed several recipes. I > put JC on CC so he can tell more. Pharo is not in the official Portage tree, but there is an overlay that includes a pharo ebuild: https://bitbucket.org/erosa/erosa-overlay Note that Gentoo ebuilds are more "recipes" than "packages". I wanted to write my own overlay with the real Gentoo style (i.e. with full compilation), but my latest attempt to compile the whole thing failed. I will probably write one for Pharo 4. JC

April 16, 2015

Versioning Jenkins Logic

by Sean P. DeNigris

Right now, the https://ci.inria.fr/pharo/view/4.0-VM/job/PharoVM-CentOs6 Jenkins job has the following shell script embedded in Jenkins. As you can see, there is quite a bit of logic there. Wouldn't it be better to put this type of thing under SCM? If so, I'm happy to do it, but where would be the best place? Is there an existing location that could fit? #!bash -lex cd "$WORKSPACE" # Set environment ============================================================ ZIP_FILTER='*' if [ "$OS" == "win" ]; then set -e # Stop the execution if a command fails! ZIP_FILTER=' *.exe *.dll' fi # Download the latest sources ================================================ wget --quiet files.pharo.org/vm/src/vmmaker-image.zip wget --quiet files.pharo.org/vm/src/cog.tar.gz # Unpack sources ============================================================= tar -xzf cog.tar.gz || echo # echo needed for Windows build (error on symlinks creation) mkdir -p cog/build mkdir -p cog/image cd cog/image unzip -o ../../vmmaker-image.zip # Generate sources =========================================================== #wget -O- get.pharo.org/vm40 | bash #wget -O pharovm-centos65.zip https://github.com/philippeback/pharovm-centos65/archive/master.zip #unzip pharovm-centos65.zip #mv pharovm-centos65-master/zeroconf-centos/* . #rmdir pharovm-centos65-master/zeroconf-centos # Only execute for a new slave # cd pharovm-centos65-master # sudo install-requisites.sh wget -O vm.zip http://files.pharo.org/vm/pharo/linux/centos/latest.zip unzip vm.zip wget http://files.pharo.org/sources/PharoV30.sources.zip unzip PharoV30.sources.zip ./pharo --nodisplay generator.image eval "PharoVMBuilder buildOnJenkins: '$OS'" || (cat stderr; exit 1) cd "$WORKSPACE" tar -czf sources.tar.gz -C cog . # Compile ==================================================================== cd cog/build sh build.sh # Archive ==================================================================== cd "$WORKSPACE/cog/results" zip -r "vm.zip" $ZIP_FILTER cp -f vm.zip ../../"${BUILD_NUMBER}.zip" cp -f vm.zip ../../"latest.zip" mv -f vm.zip ../../"Pharo-VM-${OS}-latest.zip" # success exit 0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versioning-Jenkins-Logic-tp4820056.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

Re: [Pharo-dev] VM Building on Fedora: SDL2 failure

by Sean P. DeNigris

philippeback wrote > looks like that vm code has some new things inside... I took the source tarball from the vanilla CI GNU/Linux build. The weird thing is that the Centos build is still passing... ----- Cheers, Sean -- View this message in context: http://forum.world.st/VM-Building-on-Fedora-SDL2-failure-tp4819999p4820039.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

Re: [Pharo-dev] VM Building on Fedora: SDL2 failure

by phil＠highoctane.be

looks like that vm code has some new things inside... Le 16 avr. 2015 18:22, "Sean P. DeNigris" <sean(a)clipperadams.com> a Ã©crit : > Nicolai Hess wrote > > Mixing 64 bit / 32 bit environments/toolchain? > > Yes, where I went wrong is too embarrassing to mention ha ha, so I'll move > on to the next errors... > <http://forum.world.st/file/n4820011/Screenshot_2015-04-16_12.png> > > p.s. sorry about the screenshots but it's a server running in VirtualBox so > I can't copy/paste > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/VM-Building-on-Fedora-SDL2-failure-tp4819999p4820011.… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 16, 2015

Re: [Pharo-dev] VM Building on Fedora: SDL2 failure

by Nicolai Hess

2015-04-16 18:08 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Nicolai Hess wrote > > Mixing 64 bit / 32 bit environments/toolchain? > > Yes, where I went wrong is too embarrassing to mention ha ha, :) > so I'll move > on to the next errors... > <http://forum.world.st/file/n4820011/Screenshot_2015-04-16_12.png> > search vm-dev for "NoDbgRegParms". Timothy wrote about this (I don't know if this is fully solved) and and Max Leske wrote what to change to make the build work. > > p.s. sorry about the screenshots but it's a server running in VirtualBox so > I can't copy/paste > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/VM-Building-on-Fedora-SDL2-failure-tp4819999p4820011.… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 16, 2015

Re: [Pharo-dev] VM Building on Fedora: SDL2 failure

by Nicolai Hess

Mixing 64 bit / 32 bit environments/toolchain? Am 16.04.2015 17:52 schrieb "Sean P. DeNigris" <sean(a)clipperadams.com>: > I installed all the packages listed at > > https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-in… > , > plus SDL2 and SDL2-devel, and got the following error: > <http://forum.world.st/file/n4819999/Screenshot_2015-04-16_12.png> > Any ideas? Thanks in advance! > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/VM-Building-on-Fedora-SDL2-failure-tp4819999.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 16, 2015

Re: [Pharo-dev] [Pharo-users] [Esug-list] [ANN] Pharo 4.0 is released!

by Mariano Martinez Peck

Super good news! thank you all! On Thu, Apr 16, 2015 at 1:08 PM, Richard Wettel <wettel(a)gmail.com> wrote: > Great! And thank you all! > Ricky > > â > Sent from Mailbox <https://www.dropbox.com/mailbox> > > > On Thu, Apr 16, 2015 at 5:24 PM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> Thank you all ! >> >> On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> Please spread widely. >>> Sorry for multiple posts. >>> >>> (this post can be see here: http://pharo.org/news/pharo-4.0-released) >>> >>> Dear World, >>> >>> Pharo 4.0 (http://www.pharo.org) is here. >>> >>> Pharo is a pure object-oriented programming language and a powerful >>> environment, focused on simplicity and immediate feedback. >>> >>> Many things have changed in Pharo. Here are some highlights: >>> - Inspector/Playground/Spotter are new moldable development tools for >>> inspecting, coding and searching objects. >>> - Slots model instance variables as first class entities and enable >>> meta-programming on this level. >>> - ShoreLine reporter introduces a way to report system errors and >>> collect statistics, that we will use for future improvements >>> - Dark theme. >>> >>> These are just the more prominent highlights, but the details are just >>> as important. We have closed 1697 issues in Pharo 4. Take a moment to go >>> through a more detailed recount of the progress: >>> >>> >>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md >>> >>> Pharo is improving on many fronts, but one of the most prominent changes >>> is the addition of moldable tools for inspection and search. These tools >>> provide extension mechanisms that allow every object to define ways in >>> which it can be understood effectively. To provide an idea of the impact of >>> the already existing extensions, the map below shows the Pharo classes >>> grouped in packages, highlighting in red those parts of the system that >>> have at least one such custom view coming with the main distribution. The >>> spread of these extensions shows that moldability is powerful mechanism >>> that can be used in many contexts. >>> >>> >>> Remember that Pharo is your platform. We thank all the contributors of >>> this release: >>> >>> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe >>> Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, >>> Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, >>> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei >>> Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, >>> Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane >>> Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, >>> Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, >>> Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, >>> Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max >>> Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila >>> Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot >>> Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, >>> Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, >>> Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian >>> Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, >>> Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin >>> >>> And all those who contributed indirectly, by reporting bugs, >>> participating in discussion threads, providing feedback... >>> >>> Pharo 4.0 is another big step. And, the best is yet to come. >>> >>> Enjoy! >>> The Pharo Team >>> >>> >>> _______________________________________________ >>> Esug-list mailing list >>> Esug-list(a)lists.esug.org >>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>> >>> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> > > -- Mariano http://marianopeck.wordpress.com

April 16, 2015