June 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Highlighting with pillar (html)

by Alexandre Bergel

Weirâ¦ same result. No highlight for meâ¦ :-( Alexandre > On Jun 6, 2017, at 3:58 AM, phil(a)highoctane.be wrote: > > Is > > [[[lanÂguaÂge=ÂSmaÂlltalk > g := RTGrapher new. > > ds := RTData new. > ds points: 'What a beautiful day' substrings. > ds y: [ :aString | aString size ]. > g add: ds. > > g > ]]] > > any better? > > Phil > > On Tue, Jun 6, 2017 at 9:19 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I have the following script: > > -=-=-=-=-=-=-=-=-=-=-=-= > Any objects may be provided in place of this array. For example: > > [[[ > g := RTGrapher new. > > ds := RTData new. > ds points: 'What a beautiful day' substrings. > ds y: [ :aString | aString size ]. > g add: ds. > > g > ]]] > -=-=-=-=-=-=-=-=-=-=-=-= > > And it produces: > <Screenshot 2017-06-06 03.06.06.png> > > > Any idea where there is no syntax highlighting? In some other part of the document I go get syntax highlighting. > How bizarreâ¦ > > Alexandre >

June 7, 2017

Re: [Pharo-dev] OSProcess behaves wrong on Mac OS Sierra - Pharo 6

by Cyrille Delaunay

Perfect, thank you Eliot 2017-06-06 23:41 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Cyrille, > > > On Jun 6, 2017, at 7:21 AM, Cyrille Delaunay <cy.delaunay(a)gmail.com> > wrote: > > Hello, > > I am running a Pharo 6 image (Latest update: #60498) on a mac sierra > machine (10.12.1). > I loaded version 4.6.4 of OSProcess (which is the one loaded with stable > version of CommandShell project). > > I expected these methods to tell that I am running on a "mac unix" system: > > OSProcess class >> isNonUnixMac > OSProcess class >> isUnix > OSProcess class >> isUnixMac > > But they all answer that i am running on a "non unix mac" system. > > Problem seems to come from the following check to decide if a mac > platform is "unix mac" : > > *(self platformName = 'Mac OS') and: [numericOsVersion >= 1000]* > > In my case, numericOsVersion is '10.12.1' asInteger, which gives 10 => > "non unix" > > > I broke this last week by changing getSystemAttribute: 1002 to answer e.g. '10.12.1' > instead of '1095' which the old code (Mac call Gestalt IIRC) always > returned. > > I fixed it today by changing getSystemAttribute: 1002 to answer > e.g. '1012.1' instead of '10.12.1', so '1012.1' asNumber >= 1000 once > again. Apologies for the inconvenience. The next VMs which are built > automatically should be fixed. > > -- > Cyrille Delaunay > > > > _,,,^..^,,,_ (phone) > -- Cyrille Delaunay

June 7, 2017

Re: [Pharo-dev] [Moose-dev] CFP - IWST 2017 - Deadline 16th June

by Anne Etien

Dear Smalltalker colleagues, This is a kind reminder of IWST 2017 submission deadline that will occur on 16th June (next Friday). The ACM DL endorsement and the best papers awards by Lam Research Corporation have been confirmed. Two tracks (research and industrial) this year. All details can be found bellow. Donât hesitate to submit a paper. Kind regards, Anne Etien Le 13 avr. 2017 Ã 10:59, jannik.laval(a)gmail.com a Ã©crit : > 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_… > > 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 athttp://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 > > ------------------- > 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, UniversitÃ© LumiÃ¨re Lyon 2 > laboratoire DISP > +33 4 78 77 43 06 > http://www.jannik-laval.eu > http://www.phratch.com > http://www.approchealpes.info > > > Garanti sans virus. www.avast.com > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

June 7, 2017

Re: [Pharo-dev] GitHub package management beta

by Max Leske

Yes please! > On 7 Jun 2017, at 03:16, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > 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. The 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 7, 2017

Re: [Pharo-dev] GitHub package management beta

by phil＠highoctane.be

phil(a)highoctane.be On Wed, Jun 7, 2017 at 3:16 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > 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. The > 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 7, 2017

Github package management beta

by Eliot Miranda

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 7, 2017

Re: [Pharo-dev] New and richer halt messages

by Ben Coman

Nice idea. On Wed, Jun 7, 2017 at 5:34 AM, Henrik Nergaard <draagren(a)outlook.com> wrote: > A simple way of having a "onlyMe" type is to throw another type of error > and wrap the code execution with an #on:do: catching and resuming Halt. > > Here is an example: > > ----------------------------------------------- > > | cls | > > cls := Halt subclass: #CustomHalt. > > cls class compile: 'onlyCustomHaltDuring: aBlock > This sending #class to a Class confused me for a bit. I wonder if these might be useful, just aliased to #class... cls classSide compile: 'onlyCustomHaltDuring: aBlock cls meta compile: 'onlyCustomHaltDuring: aBlock cheers -ben aBlock on: Halt - CustomHalt do: [ :ex | ex resume ] > '. > > cls class compile: 'example > self onlyCustomHaltDuring: [ > 0 crLog. > Halt now. > 1 crLog. > Halt once. > 2 crLog. > CustomHalt now. > 3 crLog. > ] > '. > > cls example > ----------------------------------------------- > > Best regards, > > Henrik > ------------------------------ > *Fra:* Pharo-dev <pharo-dev-bounces(a)lists.pharo.org> pÃ¥ vegne av Stephane > Ducasse <stepharo.self(a)gmail.com> > *Sendt:* 5. juni 2017 20:57:43 > *Til:* Pharo Development List > *Emne:* Re: [Pharo-dev] New and richer halt messages > > Could be but I like to have message too. Relying too much on tools is > good but when suddently do not have tools because you are in a minimal > kernel then having 3 extra messages should like a good win win situation. > > Stef > > On Mon, Jun 5, 2017 at 4:06 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > > > > On Mon, Jun 5, 2017 at 5:01 PM, Stephane Ducasse < > stepharo.self(a)gmail.com> > > wrote: > >>> > >>> About > >>> Halt only does not convey anything to me. > >>> Halt onlyMe means clearly what is it > >> > >> > >> To me it seems strange/awkward that code in one method will change > global > >> debugging state, > >> and it would feel better via direct UI action to add a metalink (IIUC > how > >> that would work.) > >> Plus also a global GUI tool to manage breakpoints/metalinks would be > good. > >> > >> Yes but when you need you need it. > >> Else what is the alternative: > >> - remove all the halt during the execution. > >> - execute yours > >> - put back the halt if something wrong happens. > >> > >> or > >> - create manually a global. > >> - rewrite all your halt to depend on this global > >> - turn on and off the global to get the desired effects... > > > > > > or hypothetically something like... right-click code and menu select > "break > > here, disable others" > > > > cheers -ben > > > >> > >> Tedious, cumbersome and boring. > >> We can do better. > >> > >> > >> > >> > >> > >> On Mon, Jun 5, 2017 at 4:09 AM, Ben Coman <btc(a)openinworld.com> wrote: > >>> > >>> > >>> > >>> On Mon, Jun 5, 2017 at 5:06 AM, Stephane Ducasse > >>> <stepharo.self(a)gmail.com> wrote: > >>>> > >>>> What we should consider is that well packaged methods can be in > Object. > >>>> The problem is when method in Object are used everywhere and that they > >>>> have nothing to do there. > >>>> > >>>> About > >>>> Halt only does not convey anything to me. > >>>> Halt onlyMe means clearly what is it > >>> > >>> > >>> To me it seems strange/awkward that code in one method will change > global > >>> debugging state, > >>> and it would feel better via direct UI action to add a metalink (IIUC > how > >>> that would work.) > >>> Plus also a global GUI tool to manage breakpoints/metalinks would be > >>> good. > >>> > >>> > >>>> > >>>> For the > >>>> Halt ifTest > >>>> Halt ifNotTest > >>>> > >>>> Why not. But I would prefer to be really clear. > >>>> I would prefer > >>>> > >>>> Halt ifInsideTest > >>>> Halt ifOutsideTest > >>> > >>> > >>> These sound good. > >>> cheers -ben > >>> > >>>> > >>>> > >>>> Because we are not about a couple of characters. > >>>> > >>>> Stef > >>>> > >>>> > >>>> > >>>> On Sun, Jun 4, 2017 at 3:09 PM, Cyril Ferlicot D. > >>>> <cyril.ferlicot(a)gmail.com> wrote: > >>>>> > >>>>> Le 04/06/2017 Ã 11:40, Peter Uhnak a Ã©crit : > >>>>> > But then I wouldn't be able to write 1halt. :( > >>>>> > > >>>>> > Peter > >>>>> > > >>>>> > >>>>> You can still add some startup script :) > >>>>> > >>>>> I have one compiling a "h" method in object calling halt to be able > to > >>>>> write "1h" :) > >>>>> > >>>>> -- > >>>>> Cyril Ferlicot > >>>>> https://ferlicot.fr > >>>>> > >>>>> http://www.synectique.eu > >>>>> 2 rue Jacques PrÃ©vert 01, > >>>>> 59650 Villeneuve d'ascq France > >>>>> > >>>> > >>> > >> > > > >

June 7, 2017

Re: [Pharo-dev] [ Pillar ] Plumbing travis + github => pdf delivered to you

by Ben Coman

This is really nice. Thanks Damien. Is it possible for the book title to appear in the PDF filename. At [1] it is "book.spiral.pdf", which I guess might conflict if someone wants to download other books to the same folder. Both [3] & [4] are "book.pdf". cheers -ben On Wed, Jun 7, 2017 at 2:48 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks Damien Pollet now we have a new pdf inside git hub each time you > commit. > > Here are two examples > [1] https://github.com/SquareBracketAssociates/Booklet-Smacc/releases > [2] https://github.com/SquareBracketAssociates/Booklet-Glorp/releases > > I'm going to do that for all the booklets and books :) > > Stef > > [3] https://github.com/SquareBracketAssociates/Booklet-uFFI/releases [4] https://github.com/SquareBracketAssociates/Booklet-Mocking/releases

June 7, 2017

GitHub package management beta

by Eliot Miranda

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. The 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 7, 2017

Re: [Pharo-dev] please test download for Pharo 6.0

by Martin Dias

Hi, same as Alexandre here: curl get.pharo.org/64 | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 232 100 232 0 0 425 0 --:--:-- --:--:-- --:--:-- 424 bash: line 1: syntax error near unexpected token `newline' bash: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">' However, no problem with wget -O- get.pharo.org/64 | bash, nor 32 bits. I'm on linux and followed command-line instructions in http://pharo.org/download. MartÃn On Wed, May 31, 2017 at 11:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 31 May 2017, at 16:40, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > Hi Esteban, > > Thanks for pushing this! > > I tried the script: > /tmp> curl get.pharo.org/64 | bash > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 232 100 232 0 0 538 0 --:--:-- --:--:-- --:--:-- > 539 > bash: line 1: syntax error near unexpected token `newline' > bash: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">' > /tmp> > > I got an error > > > I said zeroconf will not work yet (is not yet moved) ;) > > Esteban > > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 31, 2017, at 10:18 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > Hello, > > we are getting ready for release. > please take a minute to review: > > http://pharo.org/STAGE.download > > (notice that zerconf download will not work because it is not yet movedâ¦ > so #stable will download current stable version which is 5.0) > > cheers, > Esteban > > > >

June 6, 2017