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

Re: [Pharo-dev] flatCollect:

by StÃ©phane Ducasse

On Nov 4, 2013, at 9:40 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Indeed, it would be great to have a polymorphic message for constructing collections. In the meantime, there are three flatCollect: methods: doru do you have an example of what you mean ? For flaCollect: I let you discuss because I'm not enough concentrated but I was when we worked on it long time ago. > > Collection>>flatCollect: aBlock > "Evaluate aBlock for each of the receiver's elements and answer the > list of all resulting values flatten one level. Assumes that aBlock returns some kind > of collection for each element. Equivalent to the lisp's mapcan" > > | stream | > self isEmpty ifTrue: [ ^ self copy ]. > stream := (self species new: 0) writeStream. > self do: [ :each | stream nextPutAll: (aBlock value: each) ]. > ^ stream contents > > Set>>flatCollect: aBlock > ^self flatCollectAsSet: aBlock > > SortedCollection>>flatCollect: aBlock > ^ self flatCollect: aBlock as: OrderedCollection > > Doru > > > On Mon, Nov 4, 2013 at 6:02 PM, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > Right. I hadn't looked closely enough at the Moose one. Actually, if you dig it a bit deeper, #writeStream isn't defined in the Collection hierarchy until you get to SequenceableCollection in any case, so the Moose version is defined too high. > > So, if there is a desire for #flatCollect: outside of SequenceableColleciton, then this should work (based on Moose version): > > Collection>>flatCollect: aBlock > "Evaluate aBlock for each of the receiver's elements and answer the > list of all resulting values flatten one level. Assumes that aBlock returns some kind > of collection for each element. Equivalent to the lisp's mapcan" > "original written by a. Kuhn and released under MIT" > > | result | > self isEmpty ifTrue: [ ^ self copy ]. > result := (self species new: 0). > self do: [ :each | result addAll: (aBlock value: each) ]. > ^ result > > > SequenceableCollection>>flatCollect: aBlock > "Evaluate aBlock for each of the receiver's elements and answer the > list of all resulting values flatten one level. Assumes that aBlock returns some kind > of collection for each element. Equivalent to the lisp's mapcan" > "original written by a. Kuhn and released under MIT" > > | stream | > self isEmpty ifTrue: [ ^ self copy ]. > ^self species streamContents: [ :stream | > self do: [ :each | stream nextPutAll: (aBlock value: each) ] > > > -Chris > On Mon, Nov 4, 2013 at 8:46 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Actually I am still confused about this, for example, > > Set new writeStream nextPut: 1; contents > > does not work, so for which non-sequenceable collections would the #flatCollect: code work ? > > I was thinking that maybe #streamContents: could be put higher up ? > If that would not be possible, why not ? > And how would the #flatCollect: code then work ? > > On 04 Nov 2013, at 17:36, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > > > On Sat, Nov 2, 2013 at 3:52 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Indeed, it would be more elegant, but streamContents: is only defined in SequeanceableCollection, so it is not generic enough. > > > > So, then use the generic one where it is defined (Collection), and a more specific one that Sven suggested in SequenceableCollection. > > > > -Chris > > > > Doru > > > > > > On Sat, Nov 2, 2013 at 11:21 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > BTW, it seems #flatten in 2.0 has become #flattened in 3.0 and that too might needs the #species > > > > Would it also not be better and more elegant to say > > > > self species streamContents: [ :stream | > > â¦ ] > > > > ? > > > > On 02 Nov 2013, at 09:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > > > > On 01 Nov 2013, at 23:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > > >> Hi, > > >> > > >> I see that Pharo 3.0 has a Collection>>flatCollect:. This is great as the method proved to be very valuable in the context of Moose. > > >> > > >> However, the current Pharo implementation is less ideal: > > >> > > >> Collection>>flatCollect: aBlock > > >> ^ Array streamContents: > > >> [:stream | > > >> self do: [:ea | stream nextPutAll: (aBlock value: ea)]] > > >> > > >> The Moose one is: > > >> Collection>>flatCollect: aBlock > > >> "Evaluate aBlock for each of the receiver's elements and answer the > > >> list of all resulting values flatten one level. Assumes that aBlock returns some kind > > >> of collection for each element. Equivalent to the lisp's mapcan" > > >> "original written by a. Kuhn and released under MIT" > > >> > > >> | stream | > > >> self isEmpty ifTrue: [ ^ self copy ]. > > >> stream := (self species new: 0) writeStream. > > >> self do: [ :each | stream nextPutAll: (aBlock value: each) ]. > > >> ^ stream contents > > >> > > >> The difference is in the type returned. The Pharo one always returns Array, while the Moose one returns a collection of the same species as the receiver. > > > > > > Sounds right, returning #species. > > > > > >> Does anyone have anything against the Moose implementation? > > >> > > >> Doru > > >> > > >> -- > > >> www.tudorgirba.com > > >> > > >> "Every thing has its own flow" > > > > > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 9, 2013

Re: [Pharo-dev] [Pharo-bugtracker] FogBugz (Case [Issue]2486) File System - Linux VM: Umlaute Ã¤Ã¶Ã etc in in file/directory names: UTF8 unicode problem?

by Marcus Denker

On 08 Nov 2013, at 19:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 08 Nov 2013, at 18:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> yes, you have re-validate for each new image version, since things might have changed in between ;) >> >> Note the tags on the left side: Validated in 30547, Validated in 30555, Validated in 30556, Validated in 30557, Validated in 30558, Validated in 30559 > > I understand, but they should be integrated, right ? > Instead of making noise in my mailbox ;-) > maybe this could be seen as a hint to have a look at the change and write a short not âYes, this is goodâ. Marcus

Nov. 8, 2013

Re: [Pharo-dev] [Pharo-bugtracker] FogBugz (Case [Issue]2486) File System - Linux VM: Umlaute Ã¤Ã¶Ã etc in in file/directory names: UTF8 unicode problem?

by Sven Van Caekenberghe

On 08 Nov 2013, at 18:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: > yes, you have re-validate for each new image version, since things might have changed in between ;) > > Note the tags on the left side: Validated in 30547, Validated in 30555, Validated in 30556, Validated in 30557, Validated in 30558, Validated in 30559 I understand, but they should be integrated, right ? Instead of making noise in my mailbox ;-) > On 2013-11-08, at 18:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> This had been verified 6 times, is that normal ? >> >> On 08 Nov 2013, at 18:25, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> wrote: >> >>> A FogBugz case was edited by Ulysse The Galactic Monkey From Outer Space. >>> >>> Case ID: 2486 >>> Title: Linux VM: Umlaute Ã¤Ã¶Ã etc in in file/directory names: UTF8 unicode problem? >>> Status: Resolved (Fix Reviewed by the Monkey) >>> Category: Bug >>> Project: File System >>> Area: 1. Pharo Image >>> Priority: 5 - Fix If Time >>> Milestone: Pharo3.0: 30/03/2014 >>> Assigned To: Penelope, Ulysse's wife >>> >>> URL: https://pharo.fogbugz.com/f/cases/2486 >>> >>> >>> Changes: >>> Added tag 'Validated in 30559'. >>> >>> >>> >>> You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&comma…) from this case. >>> >>> _______________________________________________ >>> Pharo-bugtracker mailing list >>> Pharo-bugtracker(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker >> >> > >

Nov. 8, 2013

Re: [Pharo-dev] [Pharo-bugtracker] FogBugz (Case [Issue]2486) File System - Linux VM: Umlaute Ã¤Ã¶Ã etc in in file/directory names: UTF8 unicode problem?

by Camillo Bruni

yes, you have re-validate for each new image version, since things might have changed in between ;) Note the tags on the left side: Validated in 30547, Validated in 30555, Validated in 30556, Validated in 30557, Validated in 30558, Validated in 30559 On 2013-11-08, at 18:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > This had been verified 6 times, is that normal ? > > On 08 Nov 2013, at 18:25, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> wrote: > >> A FogBugz case was edited by Ulysse The Galactic Monkey From Outer Space. >> >> Case ID: 2486 >> Title: Linux VM: Umlaute Ã¤Ã¶Ã etc in in file/directory names: UTF8 unicode problem? >> Status: Resolved (Fix Reviewed by the Monkey) >> Category: Bug >> Project: File System >> Area: 1. Pharo Image >> Priority: 5 - Fix If Time >> Milestone: Pharo3.0: 30/03/2014 >> Assigned To: Penelope, Ulysse's wife >> >> URL: https://pharo.fogbugz.com/f/cases/2486 >> >> >> Changes: >> Added tag 'Validated in 30559'. >> >> >> >> You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&comma…) from this case. >> >> _______________________________________________ >> Pharo-bugtracker mailing list >> Pharo-bugtracker(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker > >

Nov. 8, 2013

Re: [Pharo-dev] [Pharo-bugtracker] FogBugz (Case [Issue]2486) File System - Linux VM: Umlaute Ã¤Ã¶Ã etc in in file/directory names: UTF8 unicode problem?

by Sven Van Caekenberghe

This had been verified 6 times, is that normal ? On 08 Nov 2013, at 18:25, Pharo Issue Tracker <do-not-reply(a)pharo.fogbugz.com> wrote: > A FogBugz case was edited by Ulysse The Galactic Monkey From Outer Space. > > Case ID: 2486 > Title: Linux VM: Umlaute Ã¤Ã¶Ã etc in in file/directory names: UTF8 unicode problem? > Status: Resolved (Fix Reviewed by the Monkey) > Category: Bug > Project: File System > Area: 1. Pharo Image > Priority: 5 - Fix If Time > Milestone: Pharo3.0: 30/03/2014 > Assigned To: Penelope, Ulysse's wife > > URL: https://pharo.fogbugz.com/f/cases/2486 > > > Changes: > Added tag 'Validated in 30559'. > > > > You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&comma…) from this case. > > _______________________________________________ > Pharo-bugtracker mailing list > Pharo-bugtracker(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Nov. 8, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30559 Home: https://github.com/pharo-project/pharo-core

Nov. 8, 2013

[pharo-project/pharo-core] af944b: 30559

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: af944bcc0a7c3bacfb8e29a1e412ccdbb1fcc82f https://github.com/pharo-project/pharo-core/commit/af944bcc0a7c3bacfb8e29a1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-08 (Fri, 08 Nov 2013) Changed paths: M Collections-Unordered.package/Dictionary.class/instance/enumerating/valuesDo_.st A Files.package/SourceFileArray.class/instance/private/sourceDataPointers.st A Files.package/SourceFileArray.class/instance/source code management/protocolAt_.st A Files.package/SourceFileArray.class/instance/source code management/protocolAt_for_.st A Files.package/SourceFileArray.class/instance/source code management/sourceCodeAt_.st A Files.package/SourceFileArray.class/instance/source code management/sourcedDataAt_.st A Files.package/SourceFileArray.class/instance/source code management/timeStampAt_.st A Files.package/SourceFileArray.class/instance/source code management/timeStampAt_for_.st M NewList.package/NewList.class/instance/accessing/allowToSelect.st A NewList.package/NewList.class/instance/drag and drop/transferFor_from_.st A NewList.package/NewListAdapter.class/instance/drag and drop/transferFor_from_.st M NewList.package/NewListRenderer.class/instance/drag and drop/startDrag_.st M Polymorph-Widgets.package/PluggableTreeMorph.class/instance/morphic/startDrag_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/protocolAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/protocolAt_for_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/sourceCodeAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/sourceDataPointers.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/sourcedDataAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/timeStampAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/timeStampAt_for_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script215.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30559.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/FileList.class/instance/drag%27n%27drop/wantsDroppedMorph_event_inMorph_.st Log Message: ----------- 30559 12117 Fix NewList >> #allowToSelect to use new ValueHolder API https://pharo.fogbugz.com/f/cases/12117 12048 Incorporate Ring extension methods in SourceFileArray https://pharo.fogbugz.com/f/cases/12048 12104 Optimize Dictionary>>valuesDo:, part 2 https://pharo.fogbugz.com/f/cases/12104 12072 Get rid of last hardcoded references to TransferMorph https://pharo.fogbugz.com/f/cases/12072 http://files.pharo.org/image/30/30559.zip

Nov. 8, 2013

Re: [Pharo-dev] Pharo3 Theme not really active in CI built images

by Camillo Bruni

actually it is done on purpose, but not fully finished. Since by default the Menu uses gradients, which is quite inconsistent with the rest of the theme. The theme should change the menu background color to something brighter. On 2013-11-08, at 17:24, Torsten Bergmann <astares(a)gmx.de> wrote: > When I download a fresh Pharo3.0 Latest update: #30558 from CI > the menues look awfull (dark gray) since I think the theme is > not correctly initialized. > > Switching the theme or evaluating > > Pharo3Theme beCurrent > > fixes this easily. > > So there is no method to change, just some code to run. So I > dont think this can be fixed with a metacello slice. > > How can we run the above "do it" to correct the images? > > Thx > T. > > > > >

Nov. 8, 2013

Re: [Pharo-dev] Cannot find NativeBoost-Core-MarcusDenker.115

by Camillo Bruni

yes, the only thing that helps against this is regular maintenance :/ On 2013-11-08, at 16:38, Igor Stasenko <siguctua(a)gmail.com> wrote: > the ancestry info is broken without it.. and > having multiple versions lying over 3 different repositories is huge mess > 1. NB main repo > 2. Pharo 30 > 3. Pharo 20 > 4. inbox 30 > > .... > > > -- > Best regards, > Igor Stasenko.

Nov. 8, 2013

Pharo3 Theme not really active in CI built images

by Torsten Bergmann

When I download a fresh Pharo3.0 Latest update: #30558 from CI the menues look awfull (dark gray) since I think the theme is not correctly initialized. Switching the theme or evaluating Pharo3Theme beCurrent fixes this easily. So there is no method to change, just some code to run. So I dont think this can be fixed with a metacello slice. How can we run the above "do it" to correct the images? Thx T.

Nov. 8, 2013