- Pharo-users - lists.pharo.org

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

by Norbert Hartl

Hurrrray!!!! Congrats you guys for the hard work!!!! Norbert > Am 16.04.2015 um 11:29 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > 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 <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 <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 > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki

April 16, 2015

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

by Tudor Girba

Great job! Thank you everyone for the contributions, support and trust. 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-users] [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

[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-users] Polygons + Skybox in woden?

by Henrik Johansen

> On 16 Apr 2015, at 9:41 , Lusa Nicolas <nicolas.lusa(a)usi.ch> wrote: > > Hello, > > I am Nicolas Lusa from university of Lugano and I am working on my master thesis with the supervision of Yuriy Tymchuk. > Right now I am working with woden and I am trying to build polygons. > Question1: Is it possible somehow to build polygons in woden? > > If not: > I know woden is based on OpenGL and I also know that in OpenGL is possible to draw polygons with GL_POLYGON and a given array of points. > Question2: How could I use GL_POLYGON through woden for my purpose? > > Moreover, I would like to put some sort of skybox in my scene. Apparently it's not possible yet, so my question is how could I do that? > > Thanks in advance. > Cheers. > Nicolas IIRC, Woden is built on modern GL techniques, and GL_POLYGON is deprecated in 3.0, so I doubt it. Luckily, triangulation of polygons is pretty much a solved problem, though I don't know of any implementations in Pharo yet. Cheers, Henry

April 16, 2015

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

by Nicolai Hess

2015-04-15 17:52 GMT+02:00 Damien Cassou <damien.cassou(a)gmail.com>: > Hi, > > Kasper Ãsterbye has just finished a proof-of-concept that renders Pillar > text inside a class comment pane. > > From the view, the developer can press $ (dollar) to edit the document in > Pillar. > What font is used for the comment pane? This is not a free type font, or? > > > > Best regards, > > -- > 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

Polygons + Skybox in woden?

by Lusa Nicolas

Hello, I am Nicolas Lusa from university of Lugano and I am working on my master thesis with the supervision of Yuriy Tymchuk. Right now I am working with woden and I am trying to build polygons. Question1: Is it possible somehow to build polygons in woden? If not: I know woden is based on OpenGL and I also know that in OpenGL is possible to draw polygons with GL_POLYGON and a given array of points. Question2: How could I use GL_POLYGON through woden for my purpose? Moreover, I would like to put some sort of skybox in my scene. Apparently it's not possible yet, so my question is how could I do that? Thanks in advance. Cheers. Nicolas

April 16, 2015

Re: [Pharo-users] Fwd: Debris' Quuve - Technologies used

by stepharo

If one day you think that this part can be shared it would be great because it could bring business around your techno Le 16/4/15 08:10, Cameron Sanders via Pharo-users a Ã©crit : > We have a full-featured CRUD system based on Magritte. Actually, we > have extended Magritte so much that all our descriptions and > components are actually subclasses of the original Magritte classes. > We have our own descriptions, components, report column classes, > mementos, table layouts, etc. All our framework is Twitter Bootstrap > integrated, fully AJAX and with lots of rich features. We can make a > full CRUD report/form out of Magritte descriptions in no time.

April 16, 2015

[FUN] [OUT OF TOPIC] Lighthouse in their way ;-)

by Luc Fabresse

https://www.youtube.com/watch?v=_VHXRYXzEVU Enjoy, #Luc

April 16, 2015

Re: [Pharo-users] Fwd: Fwd: Debris' Quuve - Technologies used

by Yanni Chiu

On Apr 15, 2015, at 8:01 PM, Cameron Sanders via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Sure, I am happy to share. We are to the point that we need to get people interested in this platform; one thing we offer is a source license and therefore we need to document things that we have not yet documented. > > So please, fire away any questions. Are there any instances of Magritte framework that are not an instances of a custom subclass? (Did you have to subclass everything?) What pushed you toward custom subclasses? Was the properties dictionary not sufficient for extending the object state variables, or was it a speed/performance issue? Would refactoring the Magritte classes to have various hook methods allowed you to avoid making custom subclasses? (I found that it was Twitter Bootstrap which drove the need for subclassing the framework, whereas native HTML would have been adaptable to Magritteâs needs). Did you use the OneToOne and OneToMany relationship descriptions by subclassing, or did you create entirely new ones? What are some statistics on your model - e.g. number to classes? average (mean/median/mode) number of attributes/methods per class? average depth of the class hierarchy? Do you translate/map the âSmalltalkâ query blocks for GemStone to get better speed, or is this unnecessary? Do you use Magritte descriptions to tag things for indexing on GemStone? Or, do you just manually create indexes on GemStone as necessary (e.g. via install code that encapsulates knowledge of where to index, or does the system automatically raise flags when indexing is needed). >From various postings, I gather you have a lot of data to process. Do you have any numbers like: - total number of objects in the system - biggest collection, typical collection size Thanks for sharing your experience.

April 16, 2015