January 2014 - Pharo-users - lists.pharo.org

Commits of two last week
by Pharo4Stef Jan. 27, 2014

Jan. 27, 2014

http://association.pharo.org/web/weekly/Commits-Jan-1

2 1

Pharoers in San Francisco
by Pharo4Stef Jan. 26, 2014

Jan. 26, 2014

Hi guys I will visit San francisco and I was wondering if some of you are living there. Because we could meet. Stef

1 0

New version of Artefact
by Olivier Auverlot Jan. 24, 2014

Jan. 24, 2014

Hi, I released a new version of Artefact. The new version supports opacity effect. http://smalltalkhub.com/#!/~RMoD/Artefact/ <http://smalltalkhub.com/#%21/%7ERMoD/Artefact/> Best regards Olivier ;-)

2 3

ConfigurationOfNacl
by HernÃ¡n Morales Durand Jan. 24, 2014

Jan. 24, 2014

I have added ConfigurationOfNacl to Pharo 3 repository. You can load it using the Configuration Browser. Nacl is a cryptolibrary based in libsodium. The binding for Pharo/Squeak ( http://www.eighty-twenty.org/index.cgi/tech/smalltalk/nacl-for-squeak-and-p…) was written by Tony-Garnock Jones. The Configuration automatically download and uncompress the compiled library file. I have tested under Windows and Linux, all tests passes. But I do not own a Mac (I'm really open to donations :) so if anyone may test the configuration under Mac it would be nice. Cheers, HernÃ¡n

2 4

Filing in code by script
by Esteban A. Maringolo Jan. 22, 2014

Jan. 22, 2014

Sometimes I need to patch a simple method and I don't want to upload a whole new image to the server (unless until I have CI). How can I file in some code in the startup script? Today I start my server with: $ nohup pharo server.image startup.st What should I add to startup to file in a few chunks of code from a patches.st file? Is CodeImporter evaluateFileNamed: 'patches.st' the right way to do it? Should I use absolute file paths? Should I consider something else? Regards. Esteban A. Maringolo

2 1

36 issues for Pharo3....
by Marcus Denker Jan. 22, 2014

Jan. 22, 2014

Hi, There are 36 issues tagged for Pharo3: https://pharo.fogbugz.com/f/filters/64/3-0-TODO Please, everyone (and even please those people who always assume that these emails âeveryoneâ means âeveryone but meâ): -> Have a look at the list of issues -> Is there any bug missing you need to have fixed till the release? -> Is any of the entries more of a ânice to haveâ than a real requirement? -> Can you help with one of those issues? Marcus

1 0

Re: [Pharo-users] FOSDEM Smalltalk Devroom
by Stephan Eggermont Jan. 21, 2014

Jan. 21, 2014

Hi Rafael, if you are going to be there the whole time, would you be so kind to help out with the video recordings? Stephan

3 2

Fwd: [Pharo-dev] [JOB] [Academia] Tenured Researcher Positions at Inria
by Marcus Denker Jan. 20, 2014

Jan. 20, 2014

Begin forwarded message: > Tenured Researcher Positions at INRIA > ======================== > > The yearly competition for Inria research positions started. (Deadline: Feb 14th) > RMoD is looking for researchers to apply for joining our team at Lille/France with > permanent (tenured) positions: > > CR2 "Young graduate scientist" > http://www.inria.fr/en/institute/recruitment/offers/young-graduate-scientis… > - a doctorate (or equivalent degree) > - formally no other research experience required, in practice the competition > is very hard and a strong academic CV is needed on a level that requires, > besides a very good PhD, at least1-2 years of post-doctoral research. > > CR1 "Young experienced scientist" > http://www.inria.fr/en/institute/recruitment/offers/senior-researcher/ > - a doctorate (or equivalent degree) > - 4 years of research experience. > - very strong academic CV. > > DR2 "Senior researcher" > http://www.inria.fr/en/institute/recruitment/offers/senior-researcher/ > - a doctorate (or equivalent degree) > - at least 8 years experience in research > - very strong academic CV. > > > The positions are tenured after a probation period of 12 Months. > > Duties > --------- > -> Research (No teaching) > -> Help manage the Research Group. > -> Be involved with the self-governance of the Inria Lab and Inria as a whole. > -> Guide PhD Students > (And therefore get a french habilitation to be able to formally supervise PhD students) > -> Help acquiring additional funds for PhD Students, Postdocs and Engineers > -> Transfer of research results to the real world. > (this means: making things real is valued. Not just paper writing) > > > About Lille and Inria: > --------------------------- > -> Lille is located in the north of france. > (one hour from Paris, 1h20 from London, 35 min from Brussels, by train) > -> French food, combined with good Belgium beer. > -> RMoD: http://rmod.lille.inria.fr > -> INRIA Lille: http://www.inria.fr/lille/ > -> INRIA in General: http://www.inria.fr/en/institute/inria-in-brief/key-figures > -> Lille: > - http://en.wikipedia.org/wiki/Lille > - http://wikitravel.org/en/Lille > > Interested? Please contact > Marcus Denker <marcus.denker(a)inria.fr> > and > StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >

1 0

Re: [Pharo-users] find used deprecated methods when moving from pharo2 to pharo3
by Stephan Eggermont Jan. 20, 2014

Jan. 20, 2014

What you can do is load your code in a Moose image, and tell it to calculate the invocations In deprecationFinder I used findDeprecationsFor: aVersion in: aProject | mooseModel | mooseModel := (MooseMonticelloHTTPImporter new setRepositoryCache: aProject monticelloRepository; importFileNamed: (aVersion at: #filename)). mooseModel allInvocations do: [ :each| aProject addInvocation: each inVersion: aVersion ] and addInvocation: aFAMIXInvocation inVersion: aDictionary |sigs| self signatures add: aFAMIXInvocation signature. sigs := aDictionary at: #signatures ifAbsentPut: Set new. sigs add: aFAMIXInvocation signature. monticelloRepository ^ MCSmalltalkhubRepository owner: self owner project: self projectName You can then at least check if methods with the same signature are still in the Pharo3 image If you use a Pharo2 based Moose to build the list, youâll be able to resolve more invocations Stephan

1 0

Re: [Pharo-users] FOSDEM Smalltalk Devroom
by Stephan Eggermont Jan. 20, 2014

Jan. 20, 2014

Sorry for the delay. I was a bit more away from home than expected. https://fosdem.org/2014/schedule/track/smalltalk/ Stephan

2 1