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

Re: [Pharo-dev] SuffixConditionals

by Sean P. DeNigris

On Apr 30, 2014, at 9:59 AM, Torsten Bergmann [via Smalltalk] <ml-node+s1294792n4757223h1(a)n4.nabble.com> wrote: > As it is MIT I ported it to Pharo: Cool! Thanks :) Was it straightforward to port? I havenât ported anything from VW in a while. Xtreams was in my sights - we did a proof of concept with filetree and cyprus mapping namespaces to prefixes. Should revisit that... ----- Cheers, Sean -- View this message in context: http://forum.world.st/SuffixConditionals-tp4757183p4757233.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

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

by Sebastian Tleye

Awesome!! ;) 2014-04-30 16:01 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Dear World, > > Pharo 3.0 (http://www.pharo.org) is here. > > [image: 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. > > [image: 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 > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > >

April 30, 2014

Pharo 3.0 Released!

by Esteban Lorenzano

Dear World, Pharo 3.0 (http://www.pharo.org) is here. 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. 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] a Pharo talk from a ruby conference

by Esteban A. Maringolo

I did a simple test, googled for "smalltalk jobs", and the fourth result was a link to this page: http://c2.com/cgi/wiki?WhyIsSmalltalkDead, which contains historical info and some rants about the ups and downs of Smalltalk use. But had a link to a Paul Graham's essay I read many years ago, which is still valuable, and helps getting a better insight: http://paulgraham.com/popular.html Best regards! -- Esteban. ps: I did a search for "pharo jobs" and only found a reference to Netstyle's search :) Esteban A. Maringolo 2014-04-29 14:14 GMT-03:00 Sebastian Sastre <sebastian(a)flowingconcept.com>: > > On Apr 29, 2014, at 2:08 PM, Ben Coman <btc(a)openInWorld.com> wrote: > > Why do some people prefer rock music and others classical music? Its about > the patterns they know. Our brains naturally try to cram each experience > into a pattern it already knows. I remember when I used to dislike Jazz > music - I couldn't "understand it". Then I started to listen to Jamiroquai > a lot - a funky Jazz/Techno hybrid. Then later I found that I had learned > to like Jazz - I could now "understand it" and know its patterns - but I > needed a stepping stone to get there. It might be that some starts using > Pharo with their favourite text editor as a comfort factor, as a stepping > stone, and then migrates over time to the standard editors. So that is a > path to draw in new users - but of course that takes effort to set up. > cheers -ben > > > This is interesting, youâre talking of acquired taste here. > > Things that needs time and context and repetition to sink in. > > Whatâs also interesting is Jamiroquai, because heâs work was your bridge to > Jazz. > > He did the inception. > > Now the question is this: > > Who in the industry is functioning as our Jamiroquai? >

April 30, 2014

Re: [Pharo-dev] SuffixConditionals

by Torsten Bergmann

As it is MIT I ported it to Pharo: Code is available on http://smalltalkhub.com/#!/~TorstenBergmann/SuffixConditionals One can load it from the config browser Bye T. > Gesendet: Mittwoch, 30. April 2014 um 14:29 Uhr > Von: "Sean P. DeNigris" <sean(a)clipperadams.com> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] SuffixConditionals > > Torsten Bergmann wrote > > SuffixConditionals adds #if: and #unless methods to BlockClosure. > > Currently in VisualWorks but can be ported to other Smalltalks (like > > Pharo) as well. > > Good idea! It is MIT and would be a great bridge for a Ruby community in the > spirit of > http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4757055… > : > FAQ > Q: ifTrue: and ifFalse: look weird to me. Why can't I have more readable > control flow statements like Ruby? > A: You can! Simply load SuffixConditionals from the Configuration Browser > and you can write things like: > [process stop] if: process isRunning > and > [process start] unless: process isRunning > > Also would be a great answer when this inevitably comes up in the endless > "why isn't Smalltalk as popular as Ruby" conversations > (http://stackoverflow.com/a/438986/424245) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/SuffixConditionals-tp4757183p4757212.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 30, 2014

Re: [Pharo-dev] [pharo-project/pharo-core]

by Marcus Denker

On 29 Apr 2014, at 16:13, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Marcus, > > > On Apr 29, 2014, at 6:31 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 29 Apr 2014, at 15:29, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >>> Without any information on what has been changed these GitHub messages are almost pure noise. It's more than tedious to expect someone to follow the link to get more info. Can the system not include at least the commit comment? >> >> There are two mails: >> >> 1) useless >> 2) it has *everything* >> -> changed methods and classes >> -> commit comments >> -> Link to get the diffs very nicely formatted. >> >> Sadly we did not find a way to turn of this one useless mail. There is sadly no option. > > So who develops github? Github inc. they have now >10 million repositories. got 100mill funding in 2012â¦ > Are they willing to provide a third option? Unlikely, considering the scale of the operation. > Another potential solution would be to direct the full commit to a server that filters/edits down the full messages and resends. > Yes, I was thinking about thatâ¦ but who has the time? > Personally I'd like to keep up with the GitHub commits through email but right now I just delete them. I could filter them out but that's no better. :-( > >> >>> Eliot (phone) >>> >>> On Apr 29, 2014, at 4:12 AM, GitHub <noreply(a)github.com> wrote: >>> >>>> Branch: refs/tags/30843 >>>> Home: https://github.com/pharo-project/pharo-core >> >> >

April 30, 2014

Re: [Pharo-dev] [Fuel] Serialize and materialize to GZip

by Mariano Martinez Peck

On Wed, Apr 30, 2014 at 6:33 AM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > Hi, > > Following the Fuel test FLUserGuidesTest>>#testGZip I discovered that I > can serialize and materialize to and from GZip archives. Cool! > > I tried with some small test object and it worked like a charm. When I > tried with a large objectâ¦ > > Yes, I have the exact same problem long ago. As far as I could debug at that point in time, it was a bug in the compression plugin in the VM. So there isn't anything easy you can do about. See http://lists.gforge.inria.fr/pipermail/pharo-project/2011-December/056419.h… for more details. > Serialization > - It does not work, the image instantly crashes > > Materialization > - Since I was not able to serialize the large object on GZip, I serialized > "normally" than compressed the resulting fuel file using GZipWriteStream > class>>#compressFile: > - When I materialize from the GZip archive, it takes forever and does not > succeed after more than 1 minute. Note that the same non-Gzipped file takes > a couple of seconds to be materialized. > > If you serialized normally and the compressed, then to materialize you need to first uncompress and then give fuel the decompressed version. BTW...what I did for Fuel and compressing is a Pharo binding to a really fast compressor/uncompressor: LZ4. http://smalltalkhub.com/#!/~marianopeck/LZ4 That is very fast, but it doesn't provide a streaming API. So the usage I did was: - Fuel serialize in memory to a bytearray - LZ4 compress that bytearray and write compressed to file or whatever you want - LZ4 uncompress from file or from where you stored the compressed version. - Fuel materialize from the compressed stream from previous step this will work even for very large graphs. There is also an experiment Max and I were doing about compressing strings right inside Fuel: https://code.google.com/p/fuel/issues/detail?id=160 But this is committed in the experiments repo. If you want to take a look... Best, -- Mariano http://marianopeck.wordpress.com

April 30, 2014

Re: [Pharo-dev] SuffixConditionals

by Sean P. DeNigris

Torsten Bergmann wrote > SuffixConditionals adds #if: and #unless methods to BlockClosure. > Currently in VisualWorks but can be ported to other Smalltalks (like > Pharo) as well. Good idea! It is MIT and would be a great bridge for a Ruby community in the spirit of http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4757055… : FAQ Q: ifTrue: and ifFalse: look weird to me. Why can't I have more readable control flow statements like Ruby? A: You can! Simply load SuffixConditionals from the Configuration Browser and you can write things like: [process stop] if: process isRunning and [process start] unless: process isRunning Also would be a great answer when this inevitably comes up in the endless "why isn't Smalltalk as popular as Ruby" conversations (http://stackoverflow.com/a/438986/424245) ----- Cheers, Sean -- View this message in context: http://forum.world.st/SuffixConditionals-tp4757183p4757212.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] Pen back in the image

by Sean P. DeNigris

philippeback wrote > I'd like to see the Pen class coming back in the main image. Answered at https://stackoverflow.com/questions/22737674/wheres-the-pen-class-in-pharo Gofer it squeaksource: 'PharoNonCorePackages'; package: 'BitBltPen'; load. Then you can "Display restoreAfter: [Pen example]" HTH ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pen-back-in-the-image-tp4751190p4757210.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] Pharo on RPi

by Goubier Thierry

Thanks JB! This is really great! Thierry Le 30/04/2014 13:18, Jean Baptiste Arnaud a Ã©crit : > The status of Rpi. > The VM work as a StackVM linux one, > Except for: > - Sound (recent bug will be fixed soon), > - NativeBoost (arm), > - FFI (recent change from Doug will be here soon) > and OsProcess (I just don not try it yet but I didn't look at it). > > > I think the VM is stable enough to be used. > I will move the infrastructure to the file server today, the last > raspberry pi VM should work. > It will be fixed during the day. > > > > On 30 Apr 2014, at 12:31, Goubier Thierry <thierry.goubier(a)cea.fr > <mailto:thierry.goubier@cea.fr>> wrote: > >> >> >> Le 30/04/2014 11:58, jannik laval a Ã©crit : >>> I have a Phratch that begin to work on RPi >>> (https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick-RP…) >>> So, you can probably use Pharo 3 >> >> Thanks. >> >> I'll start moving the infrastructure there then. >> >> Thierry >> >>> Now I have problems with FileSystem, I will ask in another thread. >> >>> Jannik >>> >>> -- >>> >>> ~~Jannik Laval~~ >>> Ãcole des Mines de Douai >>> Enseignant-chercheur >>> http://www.jannik-laval.eu >>> http://www.phratch.com >>> http://car.mines-douai.fr/ >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > Best Regards > Jean Baptiste Arnaud > jbaptiste.arnaud(a)gmail.com <mailto:jbaptiste.arnaud@gmail.com> > > > > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

April 30, 2014