February 2017 - Pharo-users

Re: [Pharo-users] Issue with Iceberg

by stepharong

there is only one way get.pharo.org curl get.pharo.org/vmLatest60 | bash It has been like that since 2013 or 2012

Feb. 18, 2017

Re: [Pharo-users] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

by stepharong

I voted On Fri, 17 Feb 2017 18:56:51 +0100, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > Dear All > > It feels delighted to be nominated as finalist for *Red Hat International > Women in Open Source Academic Awards 2017* owing to my significant > contributions to the open source community spanning various > organisations & > projects viz FOSSASIA, Pharo/Smalltalk, European Smalltalk Users Group > (ESUG), Hashkat, Women Who Code, Google Developers Group, Learn IT Girl!, > various tech stints in Canada, Europe, Singapore & India, etc. and > everyone's best wishes. > > After initial two rounds, final voting round is open now till March 6, > 2017. > I request and appeal all of you to kindly bless me with your valuable > votes. > > Folks, Some love & maximum clicks please :wink: > > Details: https://www.redhat.com/en/about/women-in-open-source > Vote here: > https://engage.redhat.com/opensourceawards-winners-votingform-2017 > > > > -- > View this message in context: > http://forum.world.st/Seeking-support-Vote-for-Jigyasa-Grover-for-Red-Hat-I… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 18, 2017

Re: [Pharo-users] Team programming with Smalltalk

by stepharong

For the record I never lost code with MC. We are managing Pharo since 2008 with MC and it works. Now I cannot open my old code stored in Envy on my current mac. While I can dezip MC files. So you see the devil is in the details.

Feb. 18, 2017

Re: [Pharo-users] Team programming with Smalltalk

by stepharong

You see. Pharo is free. Give me money and you will get something much better. For me closed and proprietary tools do not exist anymore. You see I'm moving from Keynote for my lecture slides because they decided that they do not want to load my old lectures :). Tx apple. I worked with Envy. Now Envy is not good to work in the train and deconnected. I run a local envy base on my machine but it was a bit heavy. Pharo is moving to git and this is really cool because we do not just save files in git but will offer a process and tools around. Then we will get the associate exposure :) Stef

Feb. 18, 2017

Re: [Pharo-users] Team programming with Smalltalk

by stepharong

Hilaire What we do and it is working for a lot of projects. I used the launcher to grab an image built from a CI based on a release Pharo image and a configuration of my project so that I do not have to wait. Pharo50 + ConfigurationOf/BaselineOf + jenkins => image PharoLauncher + click => download image For example for Pillar Jenkins builds 40 stable / dev 50 stable / dev 60 stable / dev based on my configuration and I pick the ones I want to work. When I commit..... bingo the CI sees it and create a new ones with the tests run :) Stef > Building the image from the shell is what I do for DrGeo release. > For development environment it is more in flux but likely should be > done. Any recommended reading on that specific point? > > Hilaire > > Le 18/02/2017 Ã 12:54, Pierce Ng a Ã©crit : >> Nowadays we are encouraging building images from configs from the CLI or >> programmatically, no? Some have mentioned starting with a freshly baked >> image >> every day. In my case, I took a fresh image, into which GitFileTree >> loaded >> cleanly, then loaded my working stuff through their configs that I've >> been >> maintaining. > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 18, 2017

Re: [Pharo-users] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

by Offray Vladimir Luna CÃ¡rdenas

Done Jigyasa and thanks for your work on Pharo and empowering women with digital tools. Cheers, Offray On 18/02/17 09:07, Ben Coman wrote: > On Sat, Feb 18, 2017 at 1:56 AM, Jigyasa Grover > <grover.jigyasa1(a)gmail.com> wrote: >> Dear All >> >> It feels delighted to be nominated as finalist for *Red Hat International >> Women in Open Source Academic Awards 2017* owing to my significant >> contributions to the open source community spanning various organisations & >> projects viz FOSSASIA, Pharo/Smalltalk, European Smalltalk Users Group >> (ESUG), Hashkat, Women Who Code, Google Developers Group, Learn IT Girl!, >> various tech stints in Canada, Europe, Singapore & India, etc. and >> everyone's best wishes. >> >> After initial two rounds, final voting round is open now till March 6, 2017. >> I request and appeal all of you to kindly bless me with your valuable votes. >> >> Folks, Some love & maximum clicks please :wink: >> >> Details: https://www.redhat.com/en/about/women-in-open-source >> Vote here: >> https://engage.redhat.com/opensourceawards-winners-votingform-2017 > Happy to help. Nice to learn a bit more about one of Pharo's > contributors, and Pharo can only benefit from broader exposure. > Voting was quite simple. > > cheers -ben > >

Feb. 18, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by stepharong

Hilaire I do not understand what Voyage would be dependent from Seaside. Stef On Sat, 18 Feb 2017 16:32:48 +0100, Hilaire <hilaire(a)drgeo.eu> wrote: > Dale, > > May be you don't want to waste anymore time on that. Thanks for your > effort. I got a way to get Voyage installed in my development image. > > Not sure what wrong, because something is wrong[1], but I got the things > installed, first update to Seaside, which break when upgrading the > Seaside installed from the configuration browser, fix the seaside broken > installation, then install Voyage which went fine. Did not test Voyage > is working though. > > Hilaire > > [1]The Pharo4 configuration browser's Magritte3 is installing Seaside > update, this should NOT happen. > Now image comes with a Configuration Browser, if I understand correctly > its intend, an user is expected those configurations to work happily > together, but it looks like not, some configurations will request update > breaking package previously installed from this configuration browser. > May be it is more a policy problem on the quality of the configuration > than a tool problem, a lot can be learn from Debian packaging. For > example Debian stable is released only when quality is ok, don't know > the details but they don't like to rush for release and people complain > new stable release take too much time to emerge, the price for quality? > For me Pharo fells too fuzzy, and it makes me very sceptical for > reliability; may be not nice to write and to read but it is how I fell. > I may be biased and I don't mean bad to anyone writing this, I know how > quality is hard to achieve and Pharo teams did great endeavour in many > aspects. > > > > > Le 17/02/2017 Ã 22:15, Dale Henrichs a Ã©crit : >> Again, thanks for detailed info ... >> >> The fact that you loaded Seaside3.1.x is good enough for my purposes >> .. the fact that Seaside3.2 is getting installed implies that there is a >> hard dependency on Seaside in one of the projects (Magritte3 perhaps?) >> ... odd that ConfigurationOfSeaside3 wasn't downloaded this time around >> --- Can you get the package version of ConfigurationOfSeaside3 that's in >> the image after the `Metacello new` loads?... I'll have to dive into the >> configurations now ... > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 18, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Hilaire

Dale, May be you don't want to waste anymore time on that. Thanks for your effort. I got a way to get Voyage installed in my development image. Not sure what wrong, because something is wrong[1], but I got the things installed, first update to Seaside, which break when upgrading the Seaside installed from the configuration browser, fix the seaside broken installation, then install Voyage which went fine. Did not test Voyage is working though. Hilaire [1]The Pharo4 configuration browser's Magritte3 is installing Seaside update, this should NOT happen. Now image comes with a Configuration Browser, if I understand correctly its intend, an user is expected those configurations to work happily together, but it looks like not, some configurations will request update breaking package previously installed from this configuration browser. May be it is more a policy problem on the quality of the configuration than a tool problem, a lot can be learn from Debian packaging. For example Debian stable is released only when quality is ok, don't know the details but they don't like to rush for release and people complain new stable release take too much time to emerge, the price for quality? For me Pharo fells too fuzzy, and it makes me very sceptical for reliability; may be not nice to write and to read but it is how I fell. I may be biased and I don't mean bad to anyone writing this, I know how quality is hard to achieve and Pharo teams did great endeavour in many aspects. Le 17/02/2017 Ã 22:15, Dale Henrichs a Ã©crit : > Again, thanks for detailed info ... > > The fact that you loaded Seaside3.1.x is good enough for my purposes > .. the fact that Seaside3.2 is getting installed implies that there is a > hard dependency on Seaside in one of the projects (Magritte3 perhaps?) > ... odd that ConfigurationOfSeaside3 wasn't downloaded this time around > --- Can you get the package version of ConfigurationOfSeaside3 that's in > the image after the `Metacello new` loads?... I'll have to dive into the > configurations now ... -- Dr. Geo http://drgeo.eu

Feb. 18, 2017

Re: [Pharo-users] Model Smalltalk Projects

by Thierry Goubier

Le 18/02/2017 Ã 14:19, horrido a Ã©crit : > Someone interested in Smalltalk would like to examine (assess) some "model > Smalltalk projects" from, say, GitHub. He would like to see the code quality > and versatility of the language. Can anyone suggest some projects he could > look at? I don't want to point him to weak projects. Thanks. I'd say Seaside on GitHub: https://github.com/SeasideSt/Seaside. I also like FileTree (https://github.com/dalehenrich/filetree) for the fact it supports with CI a significant number of targets and versions on each target. > (He's a Scala specialist, if you want to know.) As long as he is ready to recognize that Smalltalk code has the same patterns as Scala without the types (*), he should be fine. (*) Except for the patterns that only exists to cope with the type system, obviously... Regards, Thierry > > > -- > View this message in context: http://forum.world.st/Model-Smalltalk-Projects-tp4934898.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 18, 2017

Re: [Pharo-users] Team programming with Smalltalk

by Hilaire

Building the image from the shell is what I do for DrGeo release. For development environment it is more in flux but likely should be done. Any recommended reading on that specific point? Hilaire Le 18/02/2017 Ã 12:54, Pierce Ng a Ã©crit : > Nowadays we are encouraging building images from configs from the CLI or > programmatically, no? Some have mentioned starting with a freshly baked image > every day. In my case, I took a fresh image, into which GitFileTree loaded > cleanly, then loaded my working stuff through their configs that I've been > maintaining. -- Dr. Geo http://drgeo.eu

Feb. 18, 2017