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

Re: [Pharo-dev] New Website online

by Sean P. DeNigris

Marcus Denker-4 wrote > The new website is online! Wow! Instantly obvious that Aurelia was involved because it has that "well designed" look instead of our usual "I'm an engineer trying my best" look, lol ;-P ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Website-online-tp4757241p4757250.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] SuffixConditionals

by Sean P. DeNigris

> I just checked https://github.com/randycoulman/SuffixConditionals, the *.pst > files are XML files and are therefore readable Ha, cool! ----- Cheers, Sean -- View this message in context: http://forum.world.st/SuffixConditionals-tp4757183p4757248.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

Re: [Pharo-dev] [ANN]: Little NeoJSON Helper

by Sean P. DeNigris

Okay, here is version 0.1 - the most basic useful functionality to aid in writing mappings. "Assuming Neo-JSON-Core is loaded" Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'Neo-JSON-Utilities'; load. Now if you: reader := NeoJSONReader on: entity contents readStream. reader nextAs: MyClass "(that does not implement MyClass class>>#neoJsonMapping:)". You will get a debugger (which you probably want to close because the new mappings we create will not be activated as the helper hook is cached in the mappings) and a tree inspector on a NeoJSON model that you can customize, where: - a NeoJSONObject represents each JSON dictionary; for the enclosing object, the schema is already set to MyClass (i.e. the argument to #nextAs:) - a NeoJSONList represents each JSON list - a NeoJSONValue represents all other values e.g. bools, nil, strings, numbers Some useful things to do: - For each NeoJSONObject that you want to map to a class, select it in the explorer and: self schema: MyOtherClass. self generateInstVars. "self explanatory?" self mappingSourceCode inspect. "see the neoJsonMapping: source that would be generated" self generateMapping. "compile class-side neoJsonMapping:" - Select any field inside a NeoJSONObject that you want to map to an inst var with a different name and: self instVarName: #isSaved "(e.g. to map JSON fields_with_underscores to camelCase var names)" - Specify the element type of a list by selecting it and: self elementSchema: MyListReturnType. "This will automatically set the schema to #ArrayOfMyListReturnType, but you can change that manually if you want by sending #schema:) After customizing, sending #generateMapping to a NeoJSONObject should generate something like: neoJsonMapping: mapper mapper for: self do: [ :mapping | mapping mapInstVars: #(notes id). (mapping mapInstVar: #day) valueSchema: Date. (mapping mapInstVar: #events) valueSchema: #ArrayOfMyEvent. mapping mapInstVar: #isSaved to: #is_saved. (mapping mapInstVar: #timeSaved) valueSchema: DateAndTime ]. mapper for: Date customDo: [ :mapping | ]. "now you specify how to convert the string to a Date" mapper for: #ArrayOfMyEvent customDo: [ :mapping | mapping listOfElementSchema: MyEvent ]. mapper for: DateAndTime customDo: [ :mapping | ]. "same as Date above" This started as a tiny little personal experiment that got away from me, ha ha, so there is no UI, tests, or doc (except for this post). MIT of course. Enjoy! ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763p4757243.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 30, 2014

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

by Eliot Miranda

Hi Marcus, On Apr 30, 2014, at 6:42 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 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. Surely that's completely backwards. If they have 100mil (lira?) per year to spend they have the resources to improve their product. Do they have a feedback channel through which you could ask? Why don't you ask them? > >> 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? Right. We should just wallow in depression. Killing myself takes too much effort. > >> 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] Pharo 3.0 Released!

by Sven Van Caekenberghe

https://news.ycombinator.com/item?id=7673462 On 30 Apr 2014, at 16:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > and is also at ycombinator > > thumbs up! > > Esteban > > > On 30 Apr 2014, at 16:14, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> reddit: >> >> http://www.reddit.com/r/programming/comments/24d9d2/pharo_30_the_immersive_… >> >> >> 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

New Website online

by Marcus Denker

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

April 30, 2014

Re: [Pharo-dev] Pharo 3.0 Released!

by Esteban Lorenzano

and is also at ycombinator thumbs up! Esteban On 30 Apr 2014, at 16:14, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > reddit: > > http://www.reddit.com/r/programming/comments/24d9d2/pharo_30_the_immersive_… > > > 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] SuffixConditionals

by Torsten Bergmann

It was a "no-brainer", I did'nt even load the code into VisualWorks (which I do not have installed these days as I have no up to date copy/version). I just checked https://github.com/randycoulman/SuffixConditionals, the *.pst files are XML files and are therefore readable. 3 extension methods if:, unless:, and if:else: methods to BlockClosure plus a few tests. Feel free to do the same with Xtreams ;) Bye T.Â Â Gesendet:Â Mittwoch, 30. April 2014 um 16:07 Uhr Von:Â "Sean P. DeNigris" <sean(a)clipperadams.com> An:Â pharo-dev(a)lists.pharo.org Betreff:Â Re: [Pharo-dev] SuffixConditionals On Apr 30, 2014, at 9:59 AM, Torsten Bergmann [via Smalltalk] <[hidden email]> 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: Re: SuffixConditionals[http://forum.world.st/SuffixConditionals-tp4757183p4757233.html] Sent from the Pharo Smalltalk Developers mailing list archive[http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html] at Nabble.com.

April 30, 2014

Re: [Pharo-dev] Pharo 3.0 Released!

by Esteban Lorenzano

reddit: http://www.reddit.com/r/programming/comments/24d9d2/pharo_30_the_immersive_… 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] SuffixConditionals

by Esteban A. Maringolo

Thanks Torsten. I've been using my own favorite suffix conditional: #haltIfTrue. Regards! Esteban A. Maringolo 2014-04-30 10:57 GMT-03:00 Torsten Bergmann <astares(a)gmx.de>: > 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