- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] List editor spec widget

by Benjamin

On 15 Mar 2014, at 22:39, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone. > > I wander if there is already something like the list editing buttons in OS X i.e. â+â and â-â buttons that either open a dialog with another list that allows to select what to add, or remove selected items from the list. (example on screenshot). I would answer ânot yetâ :) Feel free to submit one :P If you have questions, I will be glad to answer them, and to help you to propose such a widget, reusable enough so we can add it to the spec widgets :) Ben

March 15, 2014

NBOpenGL on Windows

by Nicolai Hess

Is there a working version (maybe with examples) for NBOpenGL on Windows?

March 15, 2014

List editor spec widget

by Yuriy Tymchuk

Hi everyone. I wander if there is already something like the list editing buttons in OS X i.e. â+â and â-â buttons that either open a dialog with another list that allows to select what to add, or remove selected items from the list. (example on screenshot). Yes I know that this should be trivial, but Iâm just starting with spec, so it would be nice to have some helpers. Cheers Uko

March 15, 2014

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

by Ben Coman

Sean P. DeNigris wrote: > I'm glad we're re-inventing the tools! And, I'm struggling with this tool in > its current form... > > As others have mentioned, the "class" pseudo-variable is confusing, but here > are some that I find worse: > - The receiver does not change with the selection. For me, this was a key > feature of the explorer. > Can you try https://pharo.fogbugz.com/f/cases/13086/ cheers -ben > - It does not properly update e.g. if you are inspecting a class containing > a dictionary and add an item to the dictionary, collapsing and expanding the > dictionary node does not show the added item. It seems you must open an > entirely new inspector. > - If you toggle from EyeTreeInspector to EyeInspector, your code in the > bottom pane is lost > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/EyeTreeInspector-not-ready-for-prime-time-tp4748966.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >

March 15, 2014

Roassal 3D empty windows

by Nicolai Hess

Hi, what could be the reason, that any Roassal3d example from the Roassal3DTutorial.pdf only shows white empty windows? I loaded ConfigurationOfRoassal3d-RonieSalgado.10 and (Smalltalk at: #ConfigurationOfRoassal3d) loadDevelopment Any ideas? regards Nicolai

March 15, 2014

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