- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Sven Van Caekenberghe

On 12 Aug 2013, at 18:09, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hi, Sven, > > i added my photo on gravatar site. > I don't know how to get url from that, except that it associated with > my google mail.. > else, same avatar on google+ site. Ahh, but you don't have to do anything then: just specify the correct email address (the one associated with the gravatar), and leave image out/blank and the super intelligent code will automagically do the right thing ! But you still have to give me an updated object... > On 12 August 2013 17:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Dear Fellow Pharoers, >> >> As some of you may know, we have a page listing Pharo Contributors >> >> http://www.pharo-project.org/community/contributors >> >> This page was manually constructed and urgently needs an update. >> Based on the code behind the Pharo Consultants page >> >> http://consultants.pharo.org >> >> we want a similar data driven, statically generated page for Pharo Contributors >> >> http://contributors.pharo.org >> >> the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. >> >> PharoContributor new >> name: 'StÃ©phane Ducasse'; >> id: 'stephaneducasse'; >> email: 'stephane.ducasse(a)inria.fr'; >> website: 'http://stephane.ducasse.free.fr/'; >> description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; >> image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; >> yourself >> >> PharoContributor new >> name: 'Camillo Bruni'; >> email: 'camillobruni(a)gmail.com'; >> description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; >> yourself >> >> Some notes: >> >> - id is only needed when your name contains non-ascii characters >> - email will default to pharo-dev(a)lists.pharo.org if missing >> - website will default to a Google search for your name if a URL is missing >> - image can be omitted if you have a Gravatar, else it becomes a smiley >> - images will be rescaled to fit in 128x128, the URL needs to remain accessible >> - description is a pure text String, no markup is allowed >> - the description does not have to be too formal >> - the page is statically generated, only then do changes take effect >> >> Regards, >> >> Sven, on behalf of the Pharo Board. >> >> PS: If you are curious, the code for generating this page can be found at >> >> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople >> >> > > > > -- > Best regards, > Igor Stasenko. >

Aug. 12, 2013

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Igor Stasenko

Hi, Sven, i added my photo on gravatar site. I don't know how to get url from that, except that it associated with my google mail.. else, same avatar on google+ site. On 12 August 2013 17:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Dear Fellow Pharoers, > > As some of you may know, we have a page listing Pharo Contributors > > http://www.pharo-project.org/community/contributors > > This page was manually constructed and urgently needs an update. > Based on the code behind the Pharo Consultants page > > http://consultants.pharo.org > > we want a similar data driven, statically generated page for Pharo Contributors > > http://contributors.pharo.org > > the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. > > PharoContributor new > name: 'StÃ©phane Ducasse'; > id: 'stephaneducasse'; > email: 'stephane.ducasse(a)inria.fr'; > website: 'http://stephane.ducasse.free.fr/'; > description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; > image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; > yourself > > PharoContributor new > name: 'Camillo Bruni'; > email: 'camillobruni(a)gmail.com'; > description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; > yourself > > Some notes: > > - id is only needed when your name contains non-ascii characters > - email will default to pharo-dev(a)lists.pharo.org if missing > - website will default to a Google search for your name if a URL is missing > - image can be omitted if you have a Gravatar, else it becomes a smiley > - images will be rescaled to fit in 128x128, the URL needs to remain accessible > - description is a pure text String, no markup is allowed > - the description does not have to be too formal > - the page is statically generated, only then do changes take effect > > Regards, > > Sven, on behalf of the Pharo Board. > > PS: If you are curious, the code for generating this page can be found at > > http://www.smalltalkhub.com/#!/~Pharo/PharoPeople > > -- Best regards, Igor Stasenko.

Aug. 12, 2013

Updating the Pharo Contributors listing

by Sven Van Caekenberghe

Dear Fellow Pharoers, As some of you may know, we have a page listing Pharo Contributors http://www.pharo-project.org/community/contributors This page was manually constructed and urgently needs an update. Based on the code behind the Pharo Consultants page http://consultants.pharo.org we want a similar data driven, statically generated page for Pharo Contributors http://contributors.pharo.org the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. PharoContributor new name: 'StÃ©phane Ducasse'; id: 'stephaneducasse'; email: 'stephane.ducasse(a)inria.fr'; website: 'http://stephane.ducasse.free.fr/'; description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; yourself PharoContributor new name: 'Camillo Bruni'; email: 'camillobruni(a)gmail.com'; description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; yourself Some notes: - id is only needed when your name contains non-ascii characters - email will default to pharo-dev(a)lists.pharo.org if missing - website will default to a Google search for your name if a URL is missing - image can be omitted if you have a Gravatar, else it becomes a smiley - images will be rescaled to fit in 128x128, the URL needs to remain accessible - description is a pure text String, no markup is allowed - the description does not have to be too formal - the page is statically generated, only then do changes take effect Regards, Sven, on behalf of the Pharo Board. PS: If you are curious, the code for generating this page can be found at http://www.smalltalkhub.com/#!/~Pharo/PharoPeople

Aug. 12, 2013

[update 3.0] #30331

by StÃ©phane Ducasse

Aug. 12, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 6 regressions found. KernelTests.Classes.ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription KernelTests.Classes.ClassTest.testClassRespectsPolymorphismWithTrait KernelTests.Numbers.NumberParsingTest.testNumberReadOnlyDigit KernelTests.Numbers.SqNumberParserTest.testFloatReadError KernelTests.Numbers.SqNumberParserTest.testIntegerReadFrom Tests.Release.ReleaseTest.testUndeclared

Aug. 12, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 7 regressions found. KernelTests.Classes.ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription KernelTests.Classes.ClassTest.testClassRespectsPolymorphismWithTrait KernelTests.Numbers.NumberParsingTest.testNumberReadOnlyDigit KernelTests.Numbers.SqNumberParserTest.testFloatReadError KernelTests.Numbers.SqNumberParserTest.testIntegerReadFrom Tests.Release.ReleaseTest.testUndeclared Zinc.Zodiac.ZnHTTPSTests.testWikimedia

Aug. 12, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linu… 6 regressions found. KernelTests.Classes.ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription KernelTests.Classes.ClassTest.testClassRespectsPolymorphismWithTrait KernelTests.Numbers.NumberParsingTest.testNumberReadOnlyDigit KernelTests.Numbers.SqNumberParserTest.testFloatReadError KernelTests.Numbers.SqNumberParserTest.testIntegerReadFrom Tests.Release.ReleaseTest.testUndeclared

Aug. 12, 2013

Re: [Pharo-dev] Bag enhancements

by StÃ©phane Ducasse

Ok I will add instead of elementsAndOccurrencesDo: On Aug 12, 2013, at 9:40 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > #withOccurrencesDo: matches better the rest of the pharo system (#withIndexDo:, etc) :) > > On Aug 12, 2013, at 9:16 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> >> On Aug 12, 2013, at 1:49 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: >> >>> Why not #doWithOccurrences: ?? >> >> ok it was a proposal for a new selector :) >> >>> >>> Eg: >>> bag doWithOccurrences: [:element :count | "do something"] >>> >>> I dont'like the keysAndValuesDo: idea, is just an implementation detail. >>> >>> >>> On Sun, Aug 11, 2013 at 4:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Hi guys >>> >>> I was surprised to see the API of bag for iteration. >>> >>> I propose to add >>> >>> keysAndValuesDo: aBlock >>> "Iterate over the receiver and apply a two argument block on the element and its occurrences." >>> >>> contents associationsDo: [:assoc | aBlock value: assoc key value: assoc value ] >>> >>> and >>> >>> elementsAndOccurrencesDo: aTwoArgBlock >>> "Iterate over the receiver and apply a two argument block on the element and its occurrences." >>> >>> contents associationsDo: [:assoc | aTwoArgBlock value: assoc key value: assoc value ] >>> >>> Once we agree I will add a bug entry. >>> >>> Stef >>> >> >

Aug. 12, 2013

Re: [Pharo-dev] Bag enhancements

by Gabriel Cotelli

+1 Keep it consistent with the rest of the system. On Mon, Aug 12, 2013 at 4:40 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > #withOccurrencesDo: matches better the rest of the pharo system > (#withIndexDo:, etc) :) > > On Aug 12, 2013, at 9:16 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > On Aug 12, 2013, at 1:49 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > Why not #doWithOccurrences: ?? > > > ok it was a proposal for a new selector :) > > > Eg: > bag doWithOccurrences: [:element :count | "do something"] > > I dont'like the keysAndValuesDo: idea, is just an implementation detail. > > > On Sun, Aug 11, 2013 at 4:52 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> I was surprised to see the API of bag for iteration. >> >> I propose to add >> >> keysAndValuesDo: aBlock >> "Iterate over the receiver and apply a two argument block on the >> element and its occurrences." >> >> contents associationsDo: [:assoc | aBlock value: assoc key value: >> assoc value ] >> >> and >> >> elementsAndOccurrencesDo: aTwoArgBlock >> "Iterate over the receiver and apply a two argument block on the >> element and its occurrences." >> >> contents associationsDo: [:assoc | aTwoArgBlock value: assoc key >> value: assoc value ] >> >> Once we agree I will add a bug entry. >> >> Stef >> > > > >

Aug. 12, 2013

Re: [Pharo-dev] bug with new inspector?

by Erwan Douaille

[image: Images intÃ©grÃ©es 1] Not very beautifull but usefull. The thing is, the toolbar isn't in the debugger, so we have to use shortcuts 2013/8/12 ClÃ©ment Bera <clement.bera(a)inria.fr> > 2013/8/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> >> On Aug 12, 2013, at 10:15 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> >> wrote: >> >> 2013/8/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >>> >>> yeah it tries to do 'bag at: 1' which fails. How would look like a nice >>> bag inspector ? >>> >>> >>> same as set or dictionary >>> a bag is conceptually a collection of pair >>> >> >> Ok I will make a slice >> >>> >>> Now what would be nice is that we can have a default inspector that does >>> not interpret the structure. >>> >>> It exists, it is 'object basicInspect', or in the inspector, right click >> on self, then click on basicInspect. >> >>> >>> It would be also nice that when we dive into an object when we close the >>> window the system popup to the previous object >>> >> >> This happens when you don't dive but open a new window with Cmd+i, it is >> the old inspector workflow that still works on purpose. If it pops up the >> last object on close there is no advantage of dive instead of the old >> inspector that pops new windows. >> >> >>> because this is annoying to close the complete stack >>> we could have a shift or option variant that close everything. >>> >> >> I don't know. 10 days ago, Erwan did a tool bar for the inspector that >> may help (the slice is waiting in fix review needed). >> >> >> did you look at it? >> does it work? >> I will add it to the list of things I should look at. >> > > I've just had a quick look, it does not look very beautiful but it works > fine. > > I think we should integrate then people can improve it incrementally. It > is a nice first step. > > >> Stef >> >> >>> >>> >>> 2013/8/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> >>>> (Bag new add: 3 ; add: 3 ; add: 3 ; add: 2 ;yourself) inspect >>>> >>>> we got an error when trying to see the second element. >>>> >>>> >>>> Stef >>>> >>>> >>> >>> >> >> > > > -- > ClÃ©ment BÃ©ra > Mate Virtual Machine Engineer > BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq* > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Aug. 12, 2013