August 2013 - Pharo-dev - lists.pharo.org

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

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

by ClÃ©ment Bera

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*

Aug. 12, 2013

Re: [Pharo-dev] [update 3.0] #30330

by Martin Dias

Aug. 12, 2013

[update 3.0] #30330

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/… 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion

Aug. 12, 2013

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

by StÃ©phane Ducasse

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. 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 >> >> > >

Aug. 12, 2013

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

by ClÃ©ment Bera

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). > > > > 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 >> >> > >

Aug. 12, 2013

Re: [Pharo-dev] Bag enhancements

by Esteban Lorenzano

#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