February 2017 - Pharo-users

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

by Ben Coman

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] Model Smalltalk Projects

by Alexandre Bergel

I would say Roassal. Alexandre > Le 18 fÃ©vr. 2017 Ã 10:19, horrido <horrido.hobbies(a)gmail.com> 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. > > (He's a Scala specialist, if you want to know.) > > > > -- > 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

Model Smalltalk Projects

by horrido

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. (He's a Scala specialist, if you want to know.) -- 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] Issue with Iceberg

by Pierce Ng

On Fri, Feb 17, 2017 at 10:48:10AM -0300, Alexandre Bergel wrote: > Getting the latest unstable VM is a bit mysterious. Where to get it? Maybe on bintray: https://bintray.com/opensmalltalk/vm/cog/201702150128#files Now I don't know whether these are meant to be "unstable" per se. :-) Pierce

Feb. 18, 2017

SHA256/512 Password Hashing for Pharo 5

by Pierce Ng

Hi all, I've updated my SHA256/512 password hashing library from NativeBoost to the Pharo 5 FFI, added an authentication database that uses in-image persistence and a very simple user interface written in Spec. GH: https://github.com/PierceNg/PasswordCrypt/ Blog post: http://www.samadhiweb.com/blog/2017.02.18.shacrypt.html Pierce

Feb. 18, 2017

Re: [Pharo-users] Team programming with Smalltalk

by Pierce Ng

On Fri, Feb 17, 2017 at 06:27:59PM +0100, Hilaire wrote: > Entropies always comes with interacting 'living' system. Good point. I just tried loading GitFileTree into a Pharo 5 image that I've been using for a while. The image had, to use your term, collected enough entropy such that the loading failed and the VM hung. > GNU Smalltalk took an original approach: it ships a minimal image you > don't modify and you install code on top of it. So really you never save > your image, entropies remains constant over time. This approach is not > really possible with Pharo. 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. Pierce

Feb. 18, 2017

Re: [Pharo-users] Team programming with Smalltalk

by itlists＠schrievkrom.de

Am 17.02.2017 um 18:51 schrieb Esteban A. Maringolo: > I've used ENVY for a couple of years, and marginally used Store. Store > is nothing compared with ENVY, ENVY is far superior. Store is like > Monticello, but as such it lacks the "Configuration Map" part of it, > that is offered by Metacello in Pharo/Squeak/GemStone. > > However I find ENVY to be too cumbersome for an agile way of working. And another point is, that the way of ENVYs thinking is also available in the tools they offer for the developer (let it be VW 2.5.2 or VASmalltalk). Same tools on all platforms. This way of thinking is also introduced in the kind of browsers you have - which offers different ways of views on your projects. For me the most and strongest point in the ENVY-Browsers area is the ApplicationBrowser. Its shows you only the part of the image of a specific application (package) , which are new classes introduced by you in this application (package) - but also all the extension methods you added in this application (package) to classes. That means - programmers can stay for the whole life of a project - in only this kind of browsers. A wonderful way of viewing the image. Sadly this is gone or simply only badly implemented. E.g. in Pharo you can select a package - fine, but to know, what has been extended in this package ?. The name of the method categories also define in which package this method is located in. Make a type error and the method goes into a different package and you will not recognize it. Solutions born by the idea: how can we make it simple to have a solution this evening - and these solutions survive over the years. ENVY for the first time used ? Well I remember, that I was crazy about this tool - all this versioning, prerequisites etc ... but now after 20 years ? I'm used to the tools available on the Smalltalk market - but really nice versioning (with several platforms): ENVY is the way to go. And the original version had several user interactions implemented - which have been defined by VASmalltalk (e.g. change the developer role and make this or that in one click). ENVY is also the tool, where I have so much confidence with, because over the last 20 years I've never seen crashes and data losses. A strong point for a closed-source software repository. Marten -- Marten Feldtmann

Feb. 18, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Hilaire

The configuration of seaside is the same before and after the 'Monticello new' loads. #278 It match the fact you don't see a ConfigurationOfSeaside3 download in the transcript. As I wrote in a previous email, if Seaside is not installed, the install of Voyage doesn't trigger a Seaside install. Don't know if that specific may help. Thanks Le 17/02/2017 Ã 22:15, Dale Henrichs a Ã©crit : > 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. 17, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Dale Henrichs

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 ... Dale On 02/17/2017 12:44 PM, Hilaire wrote: > Hi Dale, > > Thanks for your detailed suggestions. I follow instructions, here the > report bellow. > > Installed newest Metacello, then Voyage with new style: > > Metacello new > baseline: 'Metacello'; > repository: 'github://dalehenrich/metacello-work:master/repository'; > get. > Metacello new > baseline: 'Metacello'; > repository: 'github://dalehenrich/metacello-work:master/repository'; > onConflict: [:ex | ex allow]; > load. > > "Fetch from voyage repo at github" > Metacello new > repository: 'github://pharo-nosql/voyage/mc'; > baseline: 'Voyage'; > load: 'mongo tests'. > > It still have the same error, do an upgrade of Seaside. > Enclosed is the transcript for both Metacello and Voyage install. > > Seaside installed was 3.1.x. I don't know the x digit, it is not > documented in an obvious way :( > > Hope it helps > > Thanks > > Hilaire >

Feb. 17, 2017

Re: [Pharo-users] Latest Voyage for Pharo4

by Hilaire

Hi Dale, Thanks for your detailed suggestions. I follow instructions, here the report bellow. Installed newest Metacello, then Voyage with new style: Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; get. Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; onConflict: [:ex | ex allow]; load. "Fetch from voyage repo at github" Metacello new repository: 'github://pharo-nosql/voyage/mc'; baseline: 'Voyage'; load: 'mongo tests'. It still have the same error, do an upgrade of Seaside. Enclosed is the transcript for both Metacello and Voyage install. Seaside installed was 3.1.x. I don't know the x digit, it is not documented in an obvious way :( Hope it helps Thanks Hilaire -- Dr. Geo http://drgeo.eu

Feb. 17, 2017