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

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

by Esteban Lorenzano

spreading the word: https://news.ycombinator.com/item?id=9386775 <https://news.ycombinator.com/item?id=9386775> http://www.reddit.com/r/programming/comments/32sdli/pharo_40_the_immersive_… <http://www.reddit.com/r/programming/comments/32sdli/pharo_40_the_immersive_…> cheers, Esteban > On 16 Apr 2015, at 11:29, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Please spread widely. >

April 16, 2015

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

by kilon alios

great work people, keep pushing forward, sky is the limit :) a minor mistake in the website "Check the annonucement <http://pharo.org/news/pharo-4.0-released>, and the ChangeLogs <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo40Change…> ." should be "announcement" On Thu, Apr 16, 2015 at 12:29 PM, 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 > >

April 16, 2015

[ANN] Pharo 4.0 is released!

by Esteban Lorenzano

Please spread widely. Sorry for multiple posts. (this post can be see here: http://pharo.org/news/pharo-4.0-released <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

April 16, 2015

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

by Damien Cassou

Sean P. DeNigris <sean(a)clipperadams.com> writes: > demarey wrote >>>>> This is already possible on Gentoo... and Nix. >> It is always better to have the full documentation instead of relying on >> people knowledge. > > Yes, I did not even know we had these. What do they download? Launcher? VM + > image? VM-only? each package maintainer decide what to package. For Ubuntu and Nix, the Pharo VM and launcher are provided as 2 separate packages. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] Is Pharo Launcher Ready?

by Damien Cassou

Dale Henrichs <dale.henrichs(a)gemtalksystems.com> writes: > On 4/13/15 10:01 AM, Sean P. DeNigris wrote: >> IIUC we are planning on making Pharo Launcher the default download. > Not sure whether this is the right thread or not... > > Keep in mind that the last time I tried to use the Pharo Launcher (a > couple of months ago) on ubunutu12.04 the Ubuntu packaged failed to be > found and I had to abandon my use of Pharo Launcher since Ubuntu12.04 is > still in common use ... I think Ubuntu 12.04 is supported now. See https://launchpad.net/~pharo/+archive/ubuntu/stable?field.series_filter=pre… -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] Ubuntu ppa - How is it made?

by Damien Cassou

Markus Fritsche <mfritsche(a)reauktion.de> writes: > Damien Cassou originally created the scripts I am using. There are a few > manual steps involved that can be IMO automated. > > Look at > https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm-core-i386 > https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-launcher > https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm please update the scripts at https://github.com/pharo-project/pharo-ubuntu instead of having your own repositories. This looks more professional and everybody can find/modify them more easily. The only thing that can't easily be automated I think is the GPG signing. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] PetitMarkdown

by Damien Cassou

Christophe Demarey <Christophe.Demarey(a)inria.fr> writes: > Le 14 avr. 2015 Ã 22:51, phil(a)highoctane.be a Ã©crit : > >> I hate the figures not going where I want due to the LaTeX generation in Pillar. > > There should be options to place it where you want. Maybe a pillar expert could answer? this is not possible and, in my opinion, not desired. The following explains my reasons but requires some LaTeX knowledge to be understood. LaTeX does a really good job a placing figures at nice locations. For example, if your paragraph ends with 2 lines at the top of a page and you place a figure after this paragraph, LaTeX will make sure the figure appears at the top of a page and not after the 2 lines: this is because it would be ugly to have 2 lines, then a figure, then the rest of the text. In LaTeX, you have to make sure to always write things like "as can be seen in Figure 3" instead of "as can be seen in the figure below" because you can never be sure of the exact location of your figures. Please note that if in Pillar you don't specify any label you could reference from your text, then the figure will be placed by LaTeX at the exact location where you put it in Pillar. This is because, in this case, there is no way to write "as can be seen in Figure 3" when there is no label. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Kasper Osterbye

Damien Cassou wrote >> The TextRenderer accepts at least the commands shown by the screenshot >> noted >> by Damien. In addition I would like to point to a special link type I >> added: >> *LinkText>pharo://Classname[/methodname]* which will render a link which >> when clicked will open a new Nautilus browser on said class and >> method. > > I'm a bit skeptical about this syntax has it is heavyweight and I'm not > sure developers will want to use it. What about either: > > 1- let the developer simply write "TheClass" or "TheClass>>method" of > "#method" and get links (when target entity exists)? That's the > simplest. > > 2- or let the developer write ${pharo:TheClass}$, > ${pharo:TheClass>>method}$ or ${pharo:#method}$? This is more complex > but also more explicit. I like it to be a link, and hence the * syntax. A short version could be *>pharo://Class/method* - with auto picking the class or method name as link text as no other links (atm) will be without link text, it might default to *>Class/method* It depends a bit on the parser if it will be able to read it, I cannot try it right now. -- View this message in context: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Damien Cassou

KasperOsterbye <kasper(a)itu.dk> writes: > The TextRenderer accepts at least the commands shown by the screenshot noted > by Damien. In addition I would like to point to a special link type I added: > *LinkText>pharo://Classname[/methodname]* which will render a link which > when clicked will open a new Nautilus browser on said class and > method. I'm a bit skeptical about this syntax has it is heavyweight and I'm not sure developers will want to use it. What about either: 1- let the developer simply write "TheClass" or "TheClass>>method" of "#method" and get links (when target entity exists)? That's the simplest. 2- or let the developer write ${pharo:TheClass}$, ${pharo:TheClass>>method}$ or ${pharo:#method}$? This is more complex but also more explicit. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Damien Cassou

kilon alios <kilon.alios(a)gmail.com> writes: > ok, but where and which repo ? Smalltalkhub ? GitHub ? Is part of Pillar ? > How I install these packages ? load a Pillar image from https://ci.inria.fr/pharo-contribution/job/Pillar (using the launcher for example :-)) and load Pillar-TextRenderer and Pillar-NautilusProofOfConcept in this order from the pillar repository (already in monticello). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015