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

is it related to Freetype or Athens?

by Hilaire

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] [Pharo-dev] [ANN] Pharo 6.0 released!

by Raffaello Giulietti

> On Tue, Jun 6, 2017 at 11:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Dear World, > > The time has come for Pharo 6.0! > Nice! Thanks to all contributors. Greetings Raffaello

June 6, 2017

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

by Sven Van Caekenberghe

> On 6 Jun 2017, at 18:18, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Tue, Jun 6, 2017 at 11:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Dear World, > > The time has come for Pharo 6.0! > > Woot! > cheers -ben Super. Thank you all.

June 6, 2017

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

by Ben Coman

On Tue, Jun 6, 2017 at 11:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Dear World, > > The time has come for Pharo 6.0! > Woot! cheers -ben

June 6, 2017

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

by Norbert Hartl

It is really great! Thank you all! I'm glad the struggles with 32 bit libraries will have an end for normal deployments. The same goes for uFFI that makes things so much easier. And of course the rest of the list of changes is impressive as always. Glad to be part of this community. You rock! Norbert > Am 06.06.2017 um 17:11 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > 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 > > <Pharo6.jpeg> > > 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… <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] Wiring objects, IoC and Service Locator

by Ben Coman

On Tue, Jun 6, 2017 at 9:11 PM, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Thanks for the detailed answer ben :) > > I will try to clarify a little: the question is how to loosely wire > objects, such as MovieLister to MovieFinder, so that changes in the wiring > can be made without effort. In Java, people use DI containers and xml files > or annotations to provide the wiring configuration, which is easy to switch > entirely. For example, I could have a xml file for production code and > another for testing purposes. > > Also, another advantage is that the container takes care of ordering > object creation for me. For example, if the object A, B and C needed to be > injected on the object Y, I just have to declare each one of those objects > on the configuration file, the container arranges the creation order for > me. > I don't see what is special about this. You can easily arrange instance creation order with methods on the class-side of your domain classes. Indeed, the GTTools are set up to work with in-Image sample data. Look at implementors of #sample and #example. There was quite some bike-shedding over the naming convention (and I forget the final result), but hopefully it provide the general idea... http://forum.world.st/a-request-to-change-the-meaning-of-lt-example-gt-prag… http://forum.world.st/lt-example-gt-lt-examplar-gt-td4911728i20.html http://forum.world.st/Existing-lt-script-gt-lt-example-gt-pragmas-and-new-G… > > I started, however, to question DI as a valid mechanisms because of it's > complexities and other problems. The article from Fowler provides the > service locator as an alternative which seems to me much simpler and > completely fine solution for the problem. > If it seems suitable, then to quote Nike, just do it ;) > So, to answer you question "Is it any more complicated than that?": In > the DI approach, yes it can be, but I don't think so in the service locator > approach. > > I am asking here because I wanted to know how people from Smalltalk deal > with this problem. As it seems there is no standard approach, nor this is > perceived as a problem... > DI or Service Locator are both "implementations" of your need. Can we take step backward to see what is your need? To kick off, I hazard a guess at some possible needs... 1. To switch between configurations to use production data and test data ? 2. To make this switch during CI testing and production deployment ? 3. To switch from the command line ? 4. Want the configuration to editable remotely? e.g. from a text editor? ? ... > You think it is enough to do the wiring by hand? > I'm having trouble understanding this "by hand" concept. Don't you create the xml configuration file by hand? You can just as easily > It is ok to use a service locator approach? Or wouldn't you care about > that? > If it works, its okay. So very generally, I'd avoid starting with any external test data, so as to not distract myself by that implementation. I'd copy-paste some test data into the class-side-methods of the domain classes and hack some instance creation code around them. Build your first tests around those. Then later, consolidate them via an InImageTestData object that you'll later replace with ExternalTestData > > > but I'll add, it was so much simpler to understand without all that Java >> typing boiler plate. > > > Yeah, that's for sure! I am just used to read Java code. > > []s, > Vitor > > > As an aside, try evaluting "Smalltalk tools inspect" and debugging "Smalltalk tools browser open" cheers -ben

June 6, 2017

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

by Offray Vladimir Luna CÃ¡rdenas

Thanks community and specially Esteban! Happy of this release and put my two pesos into this! Congrats, Offray On 06/06/17 10:11, Esteban Lorenzano wrote: > 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 > Learn Pharo: http://pharo.org/documentation

June 6, 2017

Re: [Pharo-users] Wiring objects, IoC and Service Locator

by Attila Magyar

I don't think using a DI container worth the effort. They add lots of complexities and solve very little. For some reason DI containers became very popular in the Java world, but if you take a look at other programming communities you'll realize that many people are perfectly happy without using these containers. Using DI and using a DI container is orthogonal. As you also said you can just pass dependencies to objects to achieve loose coupling. Yes, you have to do this manually but what's the big deal? We're talking about code with cyclomatic complexity of 1. Calling a constructor is not a problem that need to be solved. Using an external XML configuration to describe object wiring is the worst idea ever. Here is an article about using plain old object composition to do DI http://blog.davidpeterson.co.uk/2011/01/object-oriented-example.html Some more thoughts about the problems associated with DI containers: http://www.natpryce.com/articles/000783.html http://higherorderlogic.com/2011/07/is-dependency-injection-like-facebook -- View this message in context: http://forum.world.st/Wiring-objects-IoC-and-Service-Locator-tp4949280p4949… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 6, 2017

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

by Tudor Girba

Great work! Doru > On Jun 6, 2017, at 5:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > 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 > > <Pharo6.jpeg> > > 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 > Learn Pharo: http://pharo.org/documentation -- www.tudorgirba.com www.feenk.com âSoftware has no shape. Actually, it has no one shape. It has many."

June 6, 2017

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

by volkert

Thank you Estaban for all your hard work. Volkert Am 06.06.2017 um 17:11 schrieb Esteban Lorenzano: > 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 > Learn Pharo: http://pharo.org/documentation

June 6, 2017