- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Seaside] [ANN] Pharo 6.0 released!

by Stephane Ducasse

Hi nicolai Last week we got a sync point to see what should be done. And Guille and Pavel started to set up some new monkey and check the full process. Esteban should do an announce soon. Stef On Tue, Jun 13, 2017 at 10:18 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > +1 > When will the development for Pharo 7 start ? (inbox / monkey / ...). > > > > 2017-06-06 21:54 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> Congrats! >> >> What the status of Pharo 7? When integrations will be started? >> >> 2017-06-06 17:11 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> Dear World, >>> >>> The time has come for Pharo 6.0! >>> >>> Pharo is a pure object-oriented programming language and a powerful >>> environment, focused on simplicity and immediate feedback. >>> >>> This is our most significant release yet. Here are some highlights: >>> >>> - Pharo is now provided in 64-bit version in Linux and OSX and brings >>> even better performance and stability (beware, 64bits version is a new >>> technology and a small amount of tests is still failing) >>> - A new code changes management system named Epicea for easier reviewing >>> and recovering of your code easily >>> - Integrated support for Git through an easy-to-use tool for >>> repositories and commits management named Iceberg (as a preview for Pharo >>> 6, it will be the default in Pharo 7) >>> - The unified foreign function interface (UnifiedFFI) for interfacing >>> with the outside world is significantly improved >>> - The PharoVM is now part of OpenSmalltalk initiative >>> - Introduction of object immutability, alternative bytecode sets and >>> block closures independent of outer context >>> - Pharo can now be bootstrapped from source code managed by Git >>> - Pharo modularity is improved >>> - Pharo is faster >>> - The Dark Theme was improved and set as default color theme of Pharo >>> >>> >>> These are just the more prominent highlights, but the details are just >>> as important. We have closed 1474 issues in Pharo 6.0 (a more complete >>> changelog can be found at https://github.com/pharo-proje >>> ct/pharo-changelogs/blob/master/Pharo60ChangeLogs.md). >>> >>> While the technical improvements are significant (starting the >>> transition to 64bits is a remarkable achievement), still the most >>> impressive fact is that the new code that got in the main Pharo 6.0 image >>> was contributed by more than 80 people. >>> >>> Pharo is more than code. It is an exciting project involving energetic >>> people. We thank all the contributors of this release: >>> >>> Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, >>> Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard >>> Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, >>> Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, >>> Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan >>> Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo >>> Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire >>> Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj >>> Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc >>> Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion >>> Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo >>> Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai >>> Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo >>> Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger >>> Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie >>> Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van >>> Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, >>> Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor >>> Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner >>> Kassens, Yuriy Tymchuk >>> >>> (If you contributed with Pharo 6.0 development in any way and we missed >>> your name, please send us a mail and we will add you). >>> >>> Enjoy! >>> >>> The Pharo Team >>> >>> Try Pharo: http://pharo.org/download >>> Learn Pharo: http://pharo.org/documentation >>> >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> >> >

June 13, 2017

Re: [Pharo-dev] Github package management beta

by Christophe Demarey

christophe.demarey(a)inria.fr Thanks > Le 7 juin 2017 Ã 06:32, Eliot Miranda <eliot.miranda(a)gmail.com> a Ã©crit : > > Hi All, > > I've been invited to participate in github's Bera test of their new package management support. I don't know much, if anything, about the software except that it supports RubyGems (Ruby), Maven (Java) and npm (JavaScript) formats. My contact at github has asked me to supply a list of email addresses of those who would like to test the software. My contact will provide documentation. > > If you would like to participate please reply to me using this same subject line and including in the body of the message the email you'd like used. Please do top post. > > Maybe we could get github to directly support Monticello. Maybe this could achieve some simplifications and ease some tensions. I don't know. But I'm intrigued. > > Cheers! > _,,,^..^,,,_ (phone) >

June 13, 2017

Re: [Pharo-dev] [Seaside] [ANN] Pharo 6.0 released!

by Nicolai Hess

+1 When will the development for Pharo 7 start ? (inbox / monkey / ...). 2017-06-06 21:54 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Congrats! > > What the status of Pharo 7? When integrations will be started? > > 2017-06-06 17:11 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> Dear World, >> >> The time has come for Pharo 6.0! >> >> Pharo is a pure object-oriented programming language and a powerful >> environment, focused on simplicity and immediate feedback. >> >> This is our most significant release yet. Here are some highlights: >> >> - Pharo is now provided in 64-bit version in Linux and OSX and brings >> even better performance and stability (beware, 64bits version is a new >> technology and a small amount of tests is still failing) >> - A new code changes management system named Epicea for easier reviewing >> and recovering of your code easily >> - Integrated support for Git through an easy-to-use tool for repositories >> and commits management named Iceberg (as a preview for Pharo 6, it will be >> the default in Pharo 7) >> - The unified foreign function interface (UnifiedFFI) for interfacing >> with the outside world is significantly improved >> - The PharoVM is now part of OpenSmalltalk initiative >> - Introduction of object immutability, alternative bytecode sets and >> block closures independent of outer context >> - Pharo can now be bootstrapped from source code managed by Git >> - Pharo modularity is improved >> - Pharo is faster >> - The Dark Theme was improved and set as default color theme of Pharo >> >> >> These are just the more prominent highlights, but the details are just as >> important. We have closed 1474 issues in Pharo 6.0 (a more complete >> changelog can be found at https://github.com/pharo-proje >> ct/pharo-changelogs/blob/master/Pharo60ChangeLogs.md). >> >> While the technical improvements are significant (starting the transition >> to 64bits is a remarkable achievement), still the most impressive fact is >> that the new code that got in the main Pharo 6.0 image was contributed by >> more than 80 people. >> >> Pharo is more than code. It is an exciting project involving energetic >> people. We thank all the contributors of this release: >> >> Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, >> Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard >> Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, >> Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, >> Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan >> Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo >> Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire >> Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj >> Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc >> Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion >> Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo >> Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai >> Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo >> Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger >> Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie >> Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van >> Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, >> Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor >> Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner >> Kassens, Yuriy Tymchuk >> >> (If you contributed with Pharo 6.0 development in any way and we missed >> your name, please send us a mail and we will add you). >> >> Enjoy! >> >> The Pharo Team >> >> Try Pharo: http://pharo.org/download >> Learn Pharo: http://pharo.org/documentation >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> >

June 13, 2017

Re: [Pharo-dev] Why don't the Zero Conf examples show how to launch Pharo?

by Alistair Grant

Hi Tim, On Mon, Jun 12, 2017 at 08:02:23PM +0100, Tim Mackinnon wrote: > Actually - I think its as simple as just adding > > && ./pharo-ui Pharo.image > > To the shown command? > > (Although maybe showing it as 2 steps makes it clearer that you don?t need to > download each time) > > Tim I'm currently putting together suggested text for the GNU/Linux download page. In addition to showing how to launch Pharo, I'm also suggesting: - Putting 32 bit first (it's currently safer for a newcomer) - Moving new platforms to the top and older platforms lower in order - Removing reference to Ubuntu 12.04 since it is no longer supported. If you've got any other suggestions, please let me know and I'll be happy to incorporate them. Cheers, Alistair > On 12 Jun 2017, at 19:48, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - I was wondering why the command line section on the http://pharo.org/ > web/download page, doesn?t show you how to then launch the app you have > just downloaded? > > I?m not sure if there is a way to do it all on one line (I tried && ./ > pharo-ui Pharo.image - but this doesn?t work). However I think the > website example should at least have: > > # then run it > ./pharo-ui Pharo.image > > > Otherwise we make it harder for people to figure out what to do with the > program we?ve pointed them to? > > Tim > >

June 12, 2017

Re: [Pharo-dev] Why don't the Zero Conf examples show how to launch Pharo?

by Tim Mackinnon

Actually - I think its as simple as just adding && ./pharo-ui Pharo.image To the shown command? (Although maybe showing it as 2 steps makes it clearer that you donât need to download each time) Tim > On 12 Jun 2017, at 19:48, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - I was wondering why the command line section on the http://pharo.org/web/download <http://pharo.org/web/download> page, doesnât show you how to then launch the app you have just downloaded? > > Iâm not sure if there is a way to do it all on one line (I tried && ./pharo-ui Pharo.image - but this doesnât work). However I think the website example should at least have: > > # then run it > ./pharo-ui Pharo.image > > > Otherwise we make it harder for people to figure out what to do with the program weâve pointed them to? > > Tim

June 12, 2017

Why don't the Zero Conf examples show how to launch Pharo?

by Tim Mackinnon

Hi - I was wondering why the command line section on the http://pharo.org/web/download <http://pharo.org/web/download> page, doesnât show you how to then launch the app you have just downloaded? Iâm not sure if there is a way to do it all on one line (I tried && ./pharo-ui Pharo.image - but this doesnât work). However I think the website example should at least have: # then run it ./pharo-ui Pharo.image Otherwise we make it harder for people to figure out what to do with the program weâve pointed them to? Tim

June 12, 2017

Re: [Pharo-dev] CPU and RAM usage of Pharo3 vs. Pharo6

by Marcus Denker

> On 9 Jun 2017, at 13:06, Holger Freyther <holger(a)freyther.de> wrote: > > Hey! > > my current major deployment is still with Pharo3 and due some bigger changes I start to migrate to Pharo6 and today I finally managed to update the test deployment (and be happy with it). The test is not scientific but maybe an early indicator that there is something to look at? > > The image is idle and not handling any application payload so it might be a fair comparison because of that. > > RSS + ~16 MiB RAM (~53 Mib vs. ~69 Mib) I think this is just size of image increase (e.g. new tools, tutorials, demos...). We need to clean the image in Pharo7â¦ e.g. remove all the old versions of things that we have now a new version of. For Pharo 6: you can unload some things (e.g. Help packages, maybe tests) to shrink (see ImageCleaner). For Pharo7 with the bootstrap we are already better: Image size is 30MB instead of 36, and I think people will use the bootstrap to build images specialised much more (e.g without UI, but remote tools). > CPU + ~0.005s per real second passed (think of Amazon AWS why that could matter) > (In ~1400s wall clock 57.8s vs. 50.86s cpu time was used) > That is not goodâ¦ I think there where some changes regarding the main rendering loop. It might be interesting to track them down (since Phaor3 that is a lot of potential changes, though). Or better, think about a better headless way of running servers (no UI, use Remote tools instead). Marcus

June 12, 2017

CFP - IWST 2017 - International Workshop on Smalltalk Technologies - deadline extension

by Anne Etien

Dear Smalltakers, Deadline of IWST has been postponed to June 21th AoE. However, we ask you to submit at least an abstract for June 16th. Only papers submitted before this date could be modified until June 21th. Thanks in advance, Cheers, Jannik and Anne > DÃ©but du message rÃ©expÃ©diÃ© : > > De: <jannik.laval(a)gmail.com> > Objet: [Moose-dev] CFP - IWST 2017 - International Workshop on Smalltalk Technologies > Date: 13 avril 2017 10:59:00 UTC+2 > Ã: "'Moose-related development'" <moose-dev(a)list.inf.unibe.ch> > RÃ©pondre Ã : Moose-related development <moose-dev(a)list.inf.unibe.ch> > > CFP - IWST 2017 - International Workshop on Smalltalk Technologies > > [Please accept our apologies if you receive multiple copies of this call] > [Please send to interested colleagues / mailing-lists] > ************************************************************************************************************ > CALL FOR PAPERS > > IWST 2017 â International Workshop on Smalltalk Technologies > http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_… <http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_…> > > Maribor, Slovenia; Between September 4th to 8th, 2017 > ************************************************************************************************************ > > ------------------- > Goals and scopes > ------------------- > The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. > > We expect papers of three kinds: > > Short position papers describing emerging ideas > Long research papers with deeper description of experiments and of research results. > Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. > We will not enforce any length restriction. > > -------------------- > Important Dates > -------------------- > Submission deadline: June 16th, 2017 > Notification deadline: July 21th, 2017 > Workshop : between September 4th and 8th, 2017 > All accepted papers will be published in ACM DL (To be confirmed) > > ------------------- > Topics > ------------------- > We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: > > -Aspect-oriented programming, > -Design patterns, > -Experience reports, > -Frameworks, > -Implementation, new dialects or languages implemented in Smalltalk, > -Interaction with other languages, > -Meta-programming and Meta-modeling, > -Tools > > ------------------- > Best Paper Award > ------------------- > To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. > > We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. > > The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. > > The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. > > ------------------- > Publication > ------------------- > Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm <http://www.acm.org/sigs/sigplan/authorInformation.htm>. This site also contains links to useful informations on how to write effective submissions. > > ------------------- > Submission > ------------------- > All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst2017 <https://easychair.org/conferences/?conf=iwst2017> > > ------------------- > Program chairs > ------------------- > Anne Etien (UniversitÃ© de Lille 1, France) > Jannik Laval (UniversitÃ© Lyon 2 LumiÃ¨re, France) > > > -- > ~~Jannik Laval~~ > Enseignant-chercheur > Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information > IUT LumiÃ¨re <http://iut.univ-lyon2.fr/>, UniversitÃ© LumiÃ¨re Lyon 2 <http://www.univ-lyon2.fr/> > laboratoire DISP <http://disp-lab.fr/> > +33 4 78 77 43 06 > http://www.jannik-laval.eu <http://www.jannik-laval.eu/> > http://www.phratch.com <http://www.phratch.com/> > http://www.approchealpes.info <http://www.approchealpes.info/> > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Garanti sans virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <x-msg://222/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev>

June 12, 2017

Esteban's ChangeLog week of 5 June 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 5 June 2017 to 11 June 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=5/6/2017&to=11/6/2017 ChangeLog ========= 6 June 2017: ------------ * Well... we finally [released version 6.0](http://pharo.org/news/pharo6.0-released) ! And yes, I've been working the full day on that :) cheers! Esteban

June 12, 2017

Re: [Pharo-dev] Parallel Port

by olivier auverlot

Hi, Sorry, I can't help. It's not the same problem as us. We work with the serial port to communicate with Arduino. Best regards Olivier :) 2017-06-10 20:38 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > I have forwarded your email to olivier Auverlot because he was > fighting to get Arduino working and I remember there were something > related. > > On Sat, Jun 10, 2017 at 2:57 AM, Facundo Vozzi <facundov79(a)gmail.com> > wrote: > > Hi, > > I need to access to the Parallel Port in order to use an old > Analog/Digital > > board to sense temperature in a micro brewery. Is anyone using any > package > > to do this? > > > > I'm using Pharo 6 on Windows. > > > > Thanks in advance, > > Facundo > >

June 12, 2017