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

Re: [Pharo-dev] Pharo 3.0 Released!

by phil＠highoctane.be

On Wed, Apr 30, 2014 at 5:01 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Today is a great day ! > > I am really proud to be part of this community and thankful for the > contributions and hard work of so many people. > > This is a very important milestone while the future looks even brighter. > Very true. Thanks for everything. And the new site is very nice indeed. Phil > > Sven > > On 30 Apr 2014, at 16:01, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > Dear World, > > > > Pharo 3.0 (http://www.pharo.org) is here. > > > > <pastedGraphic.png> > > > > The past year seemed short as we got busy building more than usual. Many > things have changed in Pharo. Here are the highlights: > > - The new modular Opal compiler is now the default compiler used in the > system. > > - The Athens vector graphics canvas is now integrated and it supports > Cairo rendering on all platforms. > > - Many tools have been rewritten using Spec, a new framework for > building user interfaces. > > - Versionner and Kommiter are two of the new development tools. > > - RPackage, a new package mechanism got enhanced with tags and is fully > integrated in the system. > > - The debugger model was rewritten to become modular, the inspector > received a bump to support multiple views, and the Nautilus code browser > supports tags, search and lot more improvements. > > - Morphic has seen many cleanings and improvements and the visual theme > has been revamped. > > > > These are just the more prominent highlights, but the details are just > as important. We have closed 2364 issues in Pharo 3 (compared with 1727 > issues in Pharo 2). Take a moment to go through a more detailed recount of > the progress: > > > > > https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md > > > > Pharo is improving on many fronts. Just take a look at the code city of > Pharo (built with Pharo for Pharo). Every building is a class, and the red > bricks represent the modified methods in Pharo 3. > > > > <pastedGraphic_1.png> > > > > Many things are changing but the system gets more stable. Moving from > Pharo 2 to Pharo 3 is almost a matter of just loading the code. > > > > Remember that Pharo is your platform. We thank all the contributors of > this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment > Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, > Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, > Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo > Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del > Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, > Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo > Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo > Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale > Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, > Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, > Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego > Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto > Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas > Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas > Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, > Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval > Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, > Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan > Wilkinson. > > And many many more who contributed indirectly, by reporting bugs, > participating in discussion threads, providing feedback... > > > > Pharo 3.0 is the largest step we took since we started. Yet, itâs just a > step. Expect more. Much more. > > > > Enjoy! > > The Pharo Team > > >

April 30, 2014

Re: [Pharo-dev] [Pharo-users] New Website online

by Alexandre Bergel

Yes, well done!! Alexandre On Apr 30, 2014, at 12:48 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Slick! Congrats on the site. > > On Apr 30, 2014, at 10:26 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Hi, >> >> The new website is online! >> >> http://pharo.org >> >> For now, pharo-project.org still is the old website. >> Next: pharo-project.org should forward to pharo.org, >> it will still be available as old.pharo-project.org for some time. >> >> Thanks a lot to >> Nico http://nicolas-petton.fr, >> Esteban http://smallworks.eu, >> Damien http://damiencassou.seasidehosting.st >> and Aurelia http://aurelia.saout.fr >> >> >> Marcus >> >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 30, 2014

Re: [Pharo-dev] New Website online

by Sean P. DeNigris

One of Simon Sinek's core ideas is that people "buy" your product because they believe what you believe, and that the why needs to come first to suck them in. Until we decide on the perfect wording, I would at least: - change the heading from "The live programming environment" to "The immersive programming experience" - combine the top section and the why section into: "Pharo gives you immediate and total control over your programming experience. Focused on simplicity, cleanness, and immediate feedback, it is a pure object-oriented programming language <italics>and</italics> a clean, beautiful, innovative environment (think IDE and OS rolled into one). It is open source and available for Mac OS X, Windows and Linux. because: - it puts the why first - someone on reddit specifically said that "environment" doesn't really clear anything up for them; thus "(think IDE and OS rolled into one)" - moves the most nitty gritty implementation details to the rear (e.g. platform support) But I would seriously consider my other suggestion (the one starting with "Do you want total, immediate control..."). It may sound a bit cheesy with our engineer hats on, but I've had a lot of marketing/branding training, and bold, emotionally appealing stuff like this is pure gold. And for the release snippet, I would change from: "Pharo, the programming language, live IDE and core library has a new release!" to maybe "Pharo - the programming language and core library immersed in a live IDE (all written in itself!) - has a new release!" to highlight the key points ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Website-online-tp4757241p4757278.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] Pharo RPi and FileSystem error

by David T. Lewis

> > There are no NativeBoost on Rpi, FFI or OSProcess. > Basically the fileSystem work, but some data are fetch via env variable > and then NativeBoost. > The solution is to bypass all the request of env variable. > You should use another way until, we finish to integrate a way to request > correctly the env variable (NB on arm). > > I will studies the possibility to reintegrate fast the OSProcess plugin to > offer "better" solution. I would expect OSProcess to work without problems on Rpi, although I do not have a way to test it. The plugin should be fine. Maybe some changes will be needed on the image side for detecting the platform, I'm not sure. Let me know if I can help, I will be glad to add any necessary patches to OSProcess. Dave

April 30, 2014

Re: [Pharo-dev] [Pharo-users] Pharo 3.0 Released!

by Alexandre Bergel

big big + 1 Congrat to all of us Alexandre On Apr 30, 2014, at 12:48 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > And a big +1 on that! > > On Apr 30, 2014, at 11:01 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Today is a great day ! >> >> I am really proud to be part of this community and thankful for the contributions and hard work of so many people. >> >> This is a very important milestone while the future looks even brighter. >> >> Sven >> >> On 30 Apr 2014, at 16:01, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> Dear World, >>> >>> Pharo 3.0 (http://www.pharo.org) is here. >>> >>> <pastedGraphic.png> >>> >>> The past year seemed short as we got busy building more than usual. Many things have changed in Pharo. Here are the highlights: >>> - The new modular Opal compiler is now the default compiler used in the system. >>> - The Athens vector graphics canvas is now integrated and it supports Cairo rendering on all platforms. >>> - Many tools have been rewritten using Spec, a new framework for building user interfaces. >>> - Versionner and Kommiter are two of the new development tools. >>> - RPackage, a new package mechanism got enhanced with tags and is fully integrated in the system. >>> - The debugger model was rewritten to become modular, the inspector received a bump to support multiple views, and the Nautilus code browser supports tags, search and lot more improvements. >>> - Morphic has seen many cleanings and improvements and the visual theme has been revamped. >>> >>> These are just the more prominent highlights, but the details are just as important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues in Pharo 2). Take a moment to go through a more detailed recount of the progress: >>> >>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md >>> >>> Pharo is improving on many fronts. Just take a look at the code city of Pharo (built with Pharo for Pharo). Every building is a class, and the red bricks represent the modified methods in Pharo 3. >>> >>> <pastedGraphic_1.png> >>> >>> Many things are changing but the system gets more stable. Moving from Pharo 2 to Pharo 3 is almost a matter of just loading the code. >>> >>> Remember that Pharo is your platform. We thank all the contributors of this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan Wilkinson. >>> And many many more who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... >>> >>> Pharo 3.0 is the largest step we took since we started. Yet, itâs just a step. Expect more. Much more. >>> >>> Enjoy! >>> The Pharo Team >> >> >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 30, 2014

Re: [Pharo-dev] [Esug-list] Pharo 3.0 Released!

by Ben Coman

April 30, 2014

Re: [Pharo-dev] [Pharo-users] Pharo 3.0 Released!

by Johan Fabry

And a big +1 on that! On Apr 30, 2014, at 11:01 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Today is a great day ! > > I am really proud to be part of this community and thankful for the contributions and hard work of so many people. > > This is a very important milestone while the future looks even brighter. > > Sven > > On 30 Apr 2014, at 16:01, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Dear World, >> >> Pharo 3.0 (http://www.pharo.org) is here. >> >> <pastedGraphic.png> >> >> The past year seemed short as we got busy building more than usual. Many things have changed in Pharo. Here are the highlights: >> - The new modular Opal compiler is now the default compiler used in the system. >> - The Athens vector graphics canvas is now integrated and it supports Cairo rendering on all platforms. >> - Many tools have been rewritten using Spec, a new framework for building user interfaces. >> - Versionner and Kommiter are two of the new development tools. >> - RPackage, a new package mechanism got enhanced with tags and is fully integrated in the system. >> - The debugger model was rewritten to become modular, the inspector received a bump to support multiple views, and the Nautilus code browser supports tags, search and lot more improvements. >> - Morphic has seen many cleanings and improvements and the visual theme has been revamped. >> >> These are just the more prominent highlights, but the details are just as important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues in Pharo 2). Take a moment to go through a more detailed recount of the progress: >> >> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md >> >> Pharo is improving on many fronts. Just take a look at the code city of Pharo (built with Pharo for Pharo). Every building is a class, and the red bricks represent the modified methods in Pharo 3. >> >> <pastedGraphic_1.png> >> >> Many things are changing but the system gets more stable. Moving from Pharo 2 to Pharo 3 is almost a matter of just loading the code. >> >> Remember that Pharo is your platform. We thank all the contributors of this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, ClÃ©ment Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante, Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek, Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa PeÃ±a, Nicolas Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick, Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel, Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan Wilkinson. >> And many many more who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... >> >> Pharo 3.0 is the largest step we took since we started. Yet, itâs just a step. Expect more. Much more. >> >> Enjoy! >> The Pharo Team > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

April 30, 2014

Re: [Pharo-dev] [Pharo-users] New Website online

by Johan Fabry

Slick! Congrats on the site. On Apr 30, 2014, at 10:26 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > The new website is online! > > http://pharo.org > > For now, pharo-project.org still is the old website. > Next: pharo-project.org should forward to pharo.org, > it will still be available as old.pharo-project.org for some time. > > Thanks a lot to > Nico http://nicolas-petton.fr, > Esteban http://smallworks.eu, > Damien http://damiencassou.seasidehosting.st > and Aurelia http://aurelia.saout.fr > > > Marcus > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

April 30, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Jimmie Houchin

On 04/28/2014 11:12 AM, Marcus Denker wrote: > â¦ more a Smalltalk one using Pharo: > > MountainWest RubyConf 2014 > > Noel Rappin: "But Really, You Should Learn Smalltalkâ > > Smalltalk has mystique. We talk about it more than we use it. It seems like it should be so similar to Ruby. It has similar Object-Oriented structures, it even has blocks. But everything is so slightly different, from the programming environment, to the 1-based arrays, to the simple syntax. Using Smalltalk will make you look at familiar constructs with new eyes. Weâll show you how to get started on Smalltalk, and walk through some sample code. Live coding may be involved. Youâll never look at objects the same way again. > > http://www.confreaks.com/videos/3284-mwrc-but-really-you-should-learn-small… In this thread and many others there is this debate as to whether Pharo is a Smalltalk or is Smalltalk Inspired. I find the Smalltalk Inspired arguments to be unpersuasive. To be Smalltalk Inspired is to say that you are not a Smalltalk. It is to say that Pharo is not Smalltalk but inspired by it. I find that reasoning patently false. First of all everything in Pharo begins from a Smalltalk image. It comes from Squeak Smalltalk which comes from Apple Smalltalk. etc. Pharo has an isA relationship with Smalltalk, not an isInspiredBy relationship. It may change and add features, but as has been stated before, Smalltalk isn't a static idea or artifact. It has always been a dynamic live environment in which to change itself into something it believed to be better. By removing features and by growing them. Smalltalk (an instance of SmalltalkImage), SmalltalkImage, SmalltalkImageTest, SmalltalkEditingState are all part of the Pharo Smalltalk image. The Pharo image is a Smalltalk image. It says so inside the image itself. Where are we hosting are source code? Would that be SmalltalkHub? Lets see something. http://www.smalltalkhub.com/#!/~Pharo Okay, Pharo might be doing things that would break compatibility with other Smalltalks. And that causes some people pain and grief. However that does not make Pharo not a Smalltalk. Was Smalltalk 76 constrained by backward compatibility with Smalltalk 72? Or Smalltalk 80 with either Smalltalk 76 or 72? No! Is it a requirement of Pharo to be constrained by other Smalltalk implementations in order to still be a Smalltalk. No! And then there is the argument of the outside worlds perception of Smalltalk. Since when does the perception of the outside world change whether or not Pharo is a Smalltalk? If the outside world changed their mind and decided Smalltalk is wonderful, does Pharo then all of the sudden become a Smalltalk? Ugh! We are who we are. Our roots are our roots. Pharo should be happy and proud to be a Smalltalk. A Smalltalk that is continuing the heritage of innovation. A Smalltalk that is continuing the heritage of inventing the future. We have decided to be marketing driven. Marketing is important. But marketing should determine who we are. And we should engage in disingenuous marketing practice trying to hide our roots or who we are. Why do we things distancing ourselves from Smalltalk advantages us? Just because there are lots of uneducated people who have the wrong idea about Smalltalk. Clojure embraced its Lisp heritage and is thriving. Lisp has every bit as much baggage. This talk which inspired this thread called Pharo as Smalltalk. He said, Pharo Smalltalk throughout the presentation. So in the mind of the presenter and now in the mind of the audience at the conference and of the video, Pharo is a Smalltalk. So now are we to go about re-educating all these people that Pharo is not a Smalltalk but is rather Smalltalk Inspired? We don't require the outside world's permission. We don't need their approval. We would like to have a reasonable and sufficient number of them to catch the Pharo Smalltalk vision and become a part of the family. Do we really desire everybody. No. Do we desire those people who are so closed minded that the mention of Smalltalk closes their mind because of their ignorance. I don't think so. Smalltalk is different. Pharo is Smalltalk and is different. There will be those who don't like it because of the baggage they bring, not the baggage we bring. And that is okay. All of us think different. People need to embrace what empowers them and quit complaining about what empowers somebody else. We need to embrace empowering people who understand Smalltalk not the people who don't get it for whatever reason. Let those people go and be empowered somewhere else. We and they will both be better off. Feel free to shred and destroy my arguments. I am proud to use Smalltalk. And currently Pharo is the Smalltalk I am choosing to use. Currently I am studying C. A C library is required for my project and in order to use Pharo and use this library, I need sufficient C skills. My opinion unapologetically. And if the powers that be who are in charge of Pharo decide that Smalltalk (in name) is baggage and Pharo is not Smalltalk. And that marketing Pharo as Smalltalk is bad. Then please be honest and change all references in the image of Smalltalk to Pharo. Also change SmalltalkHub to PharoHub or SmalltalkInspiredHub. If if not, be sincere and embrace Pharo Smalltalk. Long live Smalltalk. Jimmie

April 30, 2014

Re: [Pharo-dev] New Website online

by Esteban Lorenzano

there you go. I changed the âwhy pharoâ taking your ides and extending them a bit. opinions/contributions are welcome :) Esteban On 30 Apr 2014, at 17:24, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Esteban A. Maringolo wrote >> "Ok, but WTF is Pharo? A new OS, A language/gui, A dockeresque > > The pattern from other "cool" language home pages seems to be one sentence > with what and why (examples below). > > Here's a first take leveraging Simon Sinek's advice to "Start With Why" [1]: > Do you want total, immediate control over your programming and computing > experience? Then Pharo is for you. It is a live, dynamic, > turtles-all-the-way-down environment (like an IDE and OS rolled into one). > Pharo is also a purely object-oriented language. Are you sitting down? The > environment is <italics>written in itself</italics>! Pharo is open source, > and available for Mac OS X, Windows and Linux. > > Examples from other languages: > > Ruby is... > A dynamic, open source programming language with a focus on simplicity and > productivity. It has an elegant syntax that is natural to read and easy to > write. > > Python is a programming language that lets you work quickly > and integrate systems more effectively. Learn More > > JavaScriptÂ® (often shortened to JS) is a lightweight, interpreted, > object-oriented language with first-class functions, most known as the > scripting language for Web pages, but used in many non-browser environments > as well such as node.js or Apache CouchDB. It is a prototype-based, > multi-paradigm scripting language that is dynamic, and supports > object-oriented, imperative, and functional programming styles. > > [1] http://www.youtube.com/watch?v=sioZd3AxmnE @ 4:05 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/New-Website-online-tp4757241p4757267.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 30, 2014