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

Can't Log In to CI
by Sean P. DeNigris April 13, 2015

April 13, 2015

Did something change in the last 12 hours? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Can-t-Log-In-to-CI-tp4819109.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

7 6

Nautilus: Why is Search Field Pre-filled?
by Sean P. DeNigris April 13, 2015

April 13, 2015

What is the rationale? I don't like it. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-Why-is-Search-Field-Pre-filled-tp4819003.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

5 10

Problem during the loading of setting on Pharo 4
by Ferlicot D. Cyril April 12, 2015

April 12, 2015

Hi ! I use Pharo Launcher and each time I open a new Pharo 4 image, this image load my Pharo 4 settings. But since the version 40601 when Pharo load the settings i've an error: "MessageNotUnderstood: GTPlayBook class>> customDirectory:". If others have the same problem i'll open a bug repport.

3 2

Pillar package dependency
by Johan Brichau April 12, 2015

April 12, 2015

Hi all, Can someone give me access to the Pillar repository or fix the issue below? I was trying to play around with Pier3 (which uses Pillar) but immediately hit an issue. When loading: Metacello new configuration: 'Pier3'; version: #'release3.1'; load. And then opening localhost:8080 pier gives you a DNU on MacOSXPlatform>>pillarLineEnding The issue is that the code of Pillar-Model (which is loaded by Pier) is dependent on Pillar-ExporterCore (which contains the method above). I think two things need to be done: - move the #pillarLineEnding method to the Pillar-Model - move the #pillarLineEnding method from Platform class to GRPlatform class to ease porting to other Smalltalks thanks Johan

3 2

Add MetaRepoForPharo40 to default repository group
by Sean P. DeNigris April 12, 2015

April 12, 2015

Why not? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Add-MetaRepoForPharo40-to-default-repository-group-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 3

Jenkins Not Compiling Launcher Chapter`
by Sean P. DeNigris April 12, 2015

April 12, 2015

https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/22/artif… only contains the .pillar file - no html, pdf, etc. Anyone know why? I nosed through the config, build script, and console output but didn't see anything obvious. Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Jenkins-Not-Compiling-Launcher-Chapter-tp4819089.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 1

Problem with asClass usage
by stepharo April 11, 2015

April 11, 2015

Hi We want to raise a strong warning against the extension of the use of asClass and friends. asClass should not be used in Pharo distribution. I will propose to deprecate it. We are working on dependency analysis, module system, remote debugging and asClass introduces lose class references and many related problems. I would like to remove this behavior because it is clear that it will just grow up and lead to deadcode and ugly dependencies. First, most of the time you can avoid to query Smalltalk globals at: and that BY CONSTRUCTION a software system should be built and it should define its own customization. Second, at least use self class environment at: #foo Why is it much much much better? because it does not rely on String class resolution and as such is much more modular. You do not want to have the resolution of a symbol related to the place where String is defined but on where your code is actually. Imagine that tomorrow your code is in its own module. Then you want to know from your code point of you if a binding exist not from the one of environment in which String is. here are some examples: ============================== quadrangleClass ^ 'QuadrangleForTesting' asClass Strange it simply breaks. Of course it broke the smallLint rule. ============================== Metacello should better define OSProcess as a dependent.Because it is not clear what will happen if if not there? extractRepositoryFrom: zipFile to: directory "unzip <zipFile> into <directory>" | out err proc errorMessage | out := FileStream forceNewFileNamed: '/tmp/zip.out'. err := FileStream forceNewFileNamed: '/tmp/zip.err'. errorMessage := ''. [ proc := #OSProcess asClass thisOSProcess forkJob: '/usr/bin/unzip' arguments: {'-u'. zipFile. '-d'. directory} environment: nil descriptors: (Array with: nil with: out with: err). ================== I do not get why we need this funky logic. openInBrickWindowLabeled: aLabel #GLMSystemWindowBrick asClassIfAbsent: [ ^ self asMorph openInWindow ]. ^ #GLMSystemWindowBrick asClass new label: aLabel; color: Color transparent; addBrickBack: ( GLMBrick new vSpaceFill window "Answer the receiver's window." #GLMWindowBrick asClassIfAbsent: [ ^ self ownerThatIsA: SystemWindow ]. ^ (self ownerThatIsA: #GLMWindowBrick asClass) ifNil: [ self ownerThatIsA: SystemWindow ] sendUsageData: aBoolean | settingsClass | settingsClass := #GTSpotterEventRecorderSettings asClassIfAbsent: [ ^ self ]. ^ settingsClass sendUsageData: aBoolean sendUsageData | settingsClass | settingsClass := #GTSpotterEventRecorderSettings asClassIfAbsent: [ ^ false ]. ^ settingsClass sendUsageData

9 13

23rd International Smalltalk Joint Conference - Call for Contributions
by stepharo April 11, 2015

April 11, 2015

Please distribute widely 23rd International Smalltalk Joint Conference - Call for Contributions Brescia, Italy from 13 to 17 July 2015 http://www.esug.org/Conferences/2015/ This call includes: Developer Forum Smalltalk Technology Award International Workshop http://www.esug.org/wiki/pier/Conferences/2015/International-Workshop-IWST_… Student Volunteer http://www.esug.org/wiki/pier/Conferences/2015/Student-volunteers Camp Smalltalk 12 July 2015 ---------------------------------------------------------------------- You can support the ESUG conference in many different ways: * Sponsor the conference. New sponsoring packages are described at http://www.esug.org/wiki/pier/About/BecomeSponsor * Submit a talk, a software or a paper to one of the events. See below. * Attend the conference. We'd like to beat the previous record of attendance (170 people at Amsterdam 2008)! * Students can get free registration and hosting if they enrol into the the Student Volunteers program. See below. Developers Forum: International Smalltalk Developers Conference ------------------------------------------------------------------------ We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45-60 min for hand-ons tutorial. The list of topics for the normal talks and tutorials includes, but is not limited to the following: * XP practices, Development tools, Experience reports * Model driven development, Web development, Team management * Meta-Modeling, Security, New libraries & frameworks * Educational material, Embedded systems and robotics * SOA and Web services, Interaction with other programming languages Teaching Pearls and Show us Your Business ----------------------------------------- - Show your business 10 min session (Get prepared!!) - Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15 min sessions aggregated. !! How to submit? -------------- Submissions deadline is 15 of May 2015 Notification of acceptance will be on done on the fly. More information at http://www.esug.org/conferences/2015 Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a request to Stephane.Ducasse at inria.fr AND USE THE following header [ESUG 2015 Developers]. Please follow the template below the email will be automatically processed! Subject: [ESUG 2015 Developers] + your name First Name: Last Name: Email where you can always be reached: Title: Type: Tutorial/Talk/Teaching Pearl Abstract: Bio: Any presentation not respecting this form will be discarded automatically International Workshop on Smalltalk Technologies ------------------------------------------------------------------------ Read the page: http://www.esug.org/wiki/pier/Conferences/2015/International-Workshop-IWST_… Technology Award Competition ------------------------------------------------------------------------ The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the conference. Developers of any Smalltalk-based software are welcome to compete. More information at http://www.esug.org/conferences/2015/ Student Volunteer Program ------------------------------------------------------------------------ If you are a student wanting to attend ESUG, have you considered being a student volunteer? Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. More information at http://www.esug.org/wiki/pier/Conferences/2015/ http://www.esug.org/wiki/pier/Conferences/2015/Student-volunteers We hope to see you there and have fun together. _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 03 59 57 78 50 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

UpdatedPharoByExample for 3.0, 4.0, 5.0
by Sean P. DeNigris April 10, 2015

April 10, 2015

Would it make sense to freeze the documentation for each image version? Maybe a branch per image? This way, people who choose/need to work with previous image versions have an accurate reference. From my limited Git experience it shouldn't be much extra work. ----- Cheers, Sean -- View this message in context: http://forum.world.st/UpdatedPharoByExample-for-3-0-4-0-5-0-tp4817514.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 7

Fwd: [Moose-dev] Re: Wrong version loaded using Metacello
by stephan April 10, 2015

April 10, 2015

-------- Forwarded Message -------- Subject: [Moose-dev] Re: Wrong version loaded using Metacello Date: Fri, 10 Apr 2015 17:10:54 +0200 From: Jan KurÅ¡ <kurs.jan(a)gmail.com> Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> To: Moose-related development <moose-dev(a)iam.unibe.ch> Hi Dale, That works for me! Do you have any idea, when will this fix appear in Pharo? Thank you for fixing this! Cheers, Jan On 9 April 2015 at 04:33, Dale Henrichs <dale.henrichs(a)gemtalksystems.com <mailto:dale.henrichs@gemtalksystems.com>> wrote: Jan, I believe that I've fixed the bug [1], but of course the proof will be in the pudding:) So If you could run the following Metacello update script in your image (this will work in pharo3.0 or pharo4.0) and make sure it works for you: 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 The proper package was loaded for me in my test in Pharo3.0: Ã Ã Ã Loaded -> PetitIndent-JanKurs.1 --- http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- cache Dale [1] https://github.com/dalehenrich/metacello-work/issues/339 On 04/08/2015 12:14 AM, Jan KurÃÂ¡ wrote: > Dale, Thank you for the information and your help. And honestly, I > am surprised as well :) > > Cheers, > Jan > > On 7 April 2015 at 23:21, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > Jan, > > This looks like a bug in MetacelloGoferPackage>>matches: ...Ã > I've submitted a bug[1] and will work on getting a patch out > as soon as I can ... I am a bit surprised that this particular > bug has remained hidden (or unreported) for so long, but it is > a good find ... thanks for provided the details I needed to > identify the problem ... > > Dale > > [1] https://github.com/dalehenrich/metacello-work/issues/339 > > > On 04/07/2015 09:08 AM, Jan KurÃÂ¡ wrote: >> Hi Dale, >> >> One can reproduce the behaviour by evaluating this in Pharo 3 >> or Pharo 4 image: >> >> Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >> Ã Ã Ã configurationOf: #PetitParser; load. >> >> (ConfigurationOfPetitParser project version: '1.10') load. >> >> The first command loads (in my case) >> ConfigurationOfPetitParser (JanKurs.68) >> >> When I evaluate: >> (ConfigurationOfPetitParser project version: '1.10') record >> asString. >> >> I get: >> a MetacelloNullRecordingMCSpecLoader(linear load : >> Ã Ã Ã linear load : 1.10 [ConfigurationOfPetitParser] >> Ã Ã Ã Ã Ã Ã load : ConfigurationOfGlamour >> Ã Ã Ã atomic load : 1.10 [ConfigurationOfPetitParser] >> Ã Ã Ã Ã Ã Ã load : PetitParser-JanKurs.262 >> Ã Ã Ã Ã Ã Ã load : PetitTests-JanKurs.67 >> Ã Ã Ã Ã Ã Ã Ã ... >> Ã Ã Ã Ã Ã Ã Ã ... >> Ã Ã Ã Ã Ã Ã load : PetitIslands-JanKurs.18 >> Ã Ã Ã Ã Ã Ã load : PetitIndent-JanKurs.1 >> Ã Ã Ã Ã Ã Ã load : Factorial-Language-lr.6 >> Ã Ã Ã Ã Ã Ã explicit load : Glamour >> Ã Ã Ã Ã Ã Ã Ã Ã Ã load : ConfigurationOfGlamour-AndreiChis.203 >> Ã Ã Ã Ã Ã Ã linear load : 3.0.6 [ConfigurationOfGlamour] >> Ã Ã Ã Ã Ã Ã Ã ... >> >> >> Yet if I really load, the transcript shows (see the full >> transcript in the attachement): >> >> >> Loading 1.10 of ConfigurationOfPetitParser... >> Fetched -> ConfigurationOfGlamour-AndreiChis.203 --- >> http://smalltalkhub.com/mc/Moose/Glamour/main/ --- >> http://smalltalkhub.com/mc/Moose/Glamour/main/ >> Loaded -> ConfigurationOfGlamour-AndreiChis.203 --- >> http://smalltalkhub.com/mc/Moose/Glamour/main/ --- >> /home/kursjan/tmp/pharo16/package-cache >> Fetched -> PetitParser-JanKurs.262 --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ >> Fetched -> PetitTests-JanKurs.67 --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ >> ... >> ... >> Fetched -> PetitIndent-JanKurs.11 --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ --- >> http://smalltalkhub.com/mc/Moose/PetitParser/main/ >> ... >> ... >> >> >> >> Cheers, >> Jan >> >> On 6 April 2015 at 23:23, Dale Henrichs >> <dale.henrichs(a)gemtalksystems.com >> <mailto:dale.henrichs@gemtalksystems.com>> wrote: >> >> Jan, >> >> I would really like to see the Transcript output for this >> load .... also I'd like to know which mcz version of >> ConfigurationOfPetitParser you are using ... I can guess, >> but there are often a number of different versions of >> configurations floating around and I don't want to waste >> time on a version that does not match the one that you >> are having trouble with ... >> >> Dale >> >> >> On 04/04/2015 03:01 AM, Jan KurÃÂ¡ wrote: >>> Hi All, >>> >>> In ConfigurationOfPetitParser, there is a stable version >>> 1.10 for Pharo 3.0 which says to load version >>> PetitIndent.JanKurs.1. >>> >>> version110: spec >>> Ã Ã Ã <version: '1.10' imports: #('1.6-baseline' )> >>> >>> Ã Ã Ã spec for: #'common' do: [ >>> >>> Ã Ã Ã .. >>> Ã Ã Ã package: 'PetitIndent' with: 'PetitIndent-JanKurs.1'; >>> Ã Ã Ã .. >>> >>> Yet, if I load the stable version from Pharo 3.0: >>> >>> Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; >>> Ã Ã Ã configurationOf: #PetitParser; load. >>> (ConfigurationOfPetitParser project version: '1.10') load. >>> >>> >>> >>> I got PetitIndent.JanKurs.11 loaded, which is very >>> unfortunate, since other packages are kept old. >>> >>> Does anyone knows why is this? >>> >>> Cheers, >>> Jan >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

1 0