March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] method Quest :)

by Pharo4Stef

Now I can merge dictionaries in a nice way testMergeWithNonOverlappingKeys "self run: #testMerge" | d d2 d3 | d := Dictionary new at: #x put: #(x y z) ; at: #y put: #(e f g ) ; at: #a put: #(a b c); yourself. d2 := Dictionary new at: #x put: #(x y z) ; at: #y put: #( h i j) ; yourself. d3 := d merge: d2 onKeyConflictDoValues: [ :aValue :anotherValue | (aValue, anotherValue) asSet asOrderedCollection ]. self assert: (d3 at: #y) equals: #(e f g h i j). self assert: (d3 at: #a) equals: #(a b c ). self assert: (d3 at: #x) equals: #(x y z).

March 15, 2014

Re: [Pharo-dev] method Quest :)

by Pharo4Stef

I have to think if the asSet is needed too. In fact I want in addition intersectionAndDifferences: aColl because I want to be able to define nicely merge: aDict onKeyConflictDoValues: aBlock as follow | d d2 | d := #(1 3 4 5 ) groupedBy: #even. d2 := #(10 31 41 50 ) groupedBy: #even. d merge: d2 onKeyConflictDoValues: [ :aValue :anotherValue | (aValue, anotherValue) asSet asOrderedCollection ] Because manipulating dictionaries whose values are collections is boring. Stef On 14 Mar 2014, at 23:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Are the final #asArray conversions always needed ? > If not, it would be more efficient not to do them every time, no ? > > On 14 Mar 2014, at 22:19, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> something like that >> >> diffs: aCollection >> "Answer the set theoretic differences of two collections. The first element of the result is the difference from the perspective of the receiver and the second element the difference from the perspective of the argument." >> >> "#(a b c d e f) diffs: #(a b z k) #(#a #b #c #d #e #f) >> { #(#f #d #e #c) . #(#k #z)} >> " >> "{ self difference: aCollection . aCollection difference: self }" >> >> | receiver another | >> receiver := self asSet. >> another := aCollection asSet. >> self do: [ :each | >> (another includes: each) >> ifTrue: [ receiver remove: each. >> another remove: each ]]. >> ^ { receiver asArray . another asArray} >> > >

March 15, 2014

Just a reminder

by Friedrich Dominicus

That if you the developers of Phar change things many have to follow and it comes to things like this: "protocol: version dependent" platformName "After Squeak version 3.6, #platformName was moved to SmalltalkImage Some versions of Pharo move this to OSPlatform and issue deprecation warnings about the other usages. The original idiom (Squeak 3.6 and earlier) is the sensible default, but here we attempt to support other implementations if the sensible default is not available." "OSProcess platformName" (Smalltalk respondsTo: #platformName) ifTrue: [^ Smalltalk platformName]. self isPharo3AndLater ifTrue: [ ^ (Smalltalk perform: #os) name ]. ^ (((Smalltalk hasClassNamed: #OSPlatform) and: [(Smalltalk at: #OSPlatform) respondsTo: #platformName]) ifTrue: [Smalltalk at: #OSPlatform] ifFalse: [((Smalltalk classNamed: 'SmalltalkImage') ifNil: [^ Smalltalk osVersion]) current]) platformName Now how many do have to follow through all this? So well yes in the end it means not thinking about compatibility costs a lot thereafter....

March 15, 2014

Re: [Pharo-dev] pharo sound should be working

by Nicolai Hess

2014-03-14 21:43 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > so I committed some changes to allow soundplugin to work on the pharovm. > can you please download and test in your platforms? > Works on windows > > (remember, in linux you need libasound2 dependency installed) > it does not work on linux Ubuntu 12.04.2 LTS (I have installed libasound2). Why don't we include the pulse config again and build the vm-sound-pulse module as well? As I described it in the issue 12493, vm-sound-oss is buildable too. But current linux distribution don't provide the older OSS sound system. (it worked for me with ubuntu 10.04 but not with 12.04) > > cheers, > Esteban > >

March 14, 2014

Re: [Pharo-dev] method Quest :)

by Sven Van Caekenberghe

Are the final #asArray conversions always needed ? If not, it would be more efficient not to do them every time, no ? On 14 Mar 2014, at 22:19, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > something like that > > diffs: aCollection > "Answer the set theoretic differences of two collections. The first element of the result is the difference from the perspective of the receiver and the second element the difference from the perspective of the argument." > > "#(a b c d e f) diffs: #(a b z k) #(#a #b #c #d #e #f) > { #(#f #d #e #c) . #(#k #z)} > " > "{ self difference: aCollection . aCollection difference: self }" > > | receiver another | > receiver := self asSet. > another := aCollection asSet. > self do: [ :each | > (another includes: each) > ifTrue: [ receiver remove: each. > another remove: each ]]. > ^ { receiver asArray . another asArray} >

March 14, 2014

Re: [Pharo-dev] method Quest :)

by Pharo4Stef

something like that diffs: aCollection "Answer the set theoretic differences of two collections. The first element of the result is the difference from the perspective of the receiver and the second element the difference from the perspective of the argument." "#(a b c d e f) diffs: #(a b z k) #(#a #b #c #d #e #f) { #(#f #d #e #c) . #(#k #z)} " "{ self difference: aCollection . aCollection difference: self }" | receiver another | receiver := self asSet. another := aCollection asSet. self do: [ :each | (another includes: each) ifTrue: [ receiver remove: each. another remove: each ]]. ^ { receiver asArray . another asArray}

March 14, 2014

pharo sound should be working

by Esteban Lorenzano

Hi, so I committed some changes to allow soundplugin to work on the pharovm. can you please download and test in your platforms? (remember, in linux you need libasound2 dependency installed) cheers, Esteban

March 14, 2014

Re: [Pharo-dev] FileSystem-Git status update

by Esteban Lorenzano

On 14 Mar 2014, at 13:00, Vincent Blondeau <vincent.blondeau(a)polytech-lille.net> wrote: > Le 14/03/2014 11:11, Max Leske a Ã©crit : >> Hi everyone >> >> I promised to keep you posted about the progress, so here goes: >> >> - Esteban and I worked together yesterday and we got callbacks working >> - I will now do some cleanup so that its actually possible to work on libgit2 (some bindings have changed between versions 0.18 and 0.20 and I need to find out which) >> - Esteban and I will sit together again on Monday and prepare work for others / implement the object model on top of libgit2. I hope that we can separate tasks so that multiple people can work in parallel >> >> In my opinion we should be able to create local repositories, perform commits, switch branches and do checkouts by tuesday next week. Optimistically, fetch and push should also work by the end of the week. >> But thatâs really just conjecture and Iâll keep you all posted. >> >> Just a reminder: at the moment we are working to get Git running with NativeBoost *at all*. Plans for abstraction, Monticello <-> Git, Github etc. should certainly be discussed, but donât expect those things to be there at the end of next week. >> >> Max >> >> > That's seems cool ! > > As you will use NativeBoost, do you plan to do it works under Windows 7 ? yep. Guysâ¦ the default answer to that is always: yes. Any package/addition is useless if it does not works in all the supported platforms (with possible exception of mobile platforms). Said soâ¦ you always has to start from some placeâ¦ :) Esteban > > Vincent >

March 14, 2014

Re: [Pharo-dev] FileSystem-Git status update

by Pharo4Stef

excellent! Keep pushing. On 14 Mar 2014, at 11:11, Max Leske <maxleske(a)gmail.com> wrote: > Hi everyone > > I promised to keep you posted about the progress, so here goes: > > - Esteban and I worked together yesterday and we got callbacks working > - I will now do some cleanup so that its actually possible to work on libgit2 (some bindings have changed between versions 0.18 and 0.20 and I need to find out which) > - Esteban and I will sit together again on Monday and prepare work for others / implement the object model on top of libgit2. I hope that we can separate tasks so that multiple people can work in parallel > > In my opinion we should be able to create local repositories, perform commits, switch branches and do checkouts by tuesday next week. Optimistically, fetch and push should also work by the end of the week. > But thatâs really just conjecture and Iâll keep you all posted. > > Just a reminder: at the moment we are working to get Git running with NativeBoost *at all*. Plans for abstraction, Monticello <-> Git, Github etc. should certainly be discussed, but donât expect those things to be there at the end of next week. > > Max

March 14, 2014

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

by Pharo4Stef

thanks sven. > > On 13 Mar 2014, at 22:35, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Should I make a slice ? > > I have grouped all my suggested solutions and then some more in > > https://pharo.fogbugz.com/f/cases/13076/Optimize-the-information-displayed-… > > Sven

March 14, 2014