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

NewList without Icons

by Nicolai Hess

Hi, anyone knows how to use NewList without icons. Background: I have a collection with 5000 entries, every entry is a list of 20 strings. Inspecting this collection works, but scrolling the left pane of the inspector window is awfully slow. This is unexpected, as the only changing visual parts are the collection indices. For exampel, inspect the following collection: (1 to:5000) collect:[:x | (1 to:20) collect:[:t| t asString] ]. Dragging the scrollbar (or only dragging the window) is slow. Ok, there are many entries, but now, change this method (return nil instead of accessing the cache) NewList>>#iconForItem:at: ^nil "^ iconCache at: anItem ifAbsentPut: [ (self model iconForItem: anItem at: anIndex) asMorph ]" scrolling is smooth. The problem is, accessing the iconCache calls #hash on anItem, which is an IndexedEyeElement and this calls hash on its index AND on the value (the string array). The funny thing is, eyeinspector does not provide any icons at all. Therefore, is there a way to create the NewList and tell it to NEVER ask for icons? regards Nicolai

May 20, 2014

Re: [Pharo-dev] Pharo contribution plot plugin update

by Yuriy Tymchuk

Thank you! On 20 May 2014, at 17:48, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Done! > > Le 20 mai 2014 Ã 16:55, Yuriy Tymchuk a Ã©crit : > >> Hi, >> >> I donât have access to jenkins config, but it looks like the Plot Plugin[1] is not latest version. Can someone please update because they added support for matrix jobs. >> >> Uko >> >> >> [1] https://wiki.jenkins-ci.org/display/JENKINS/Plot+Plugin >

May 20, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Jimmie Houchin

On 05/20/2014 04:00 PM, Esteban A. Maringolo wrote: > 2014-05-20 17:21 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org>: > >> If we are prepared to see it failing, it does not really matter, it's in the >> contract... >> The only problem is to be aware of this contract and avoid negative >> impression. >> Maybe an advanced menu triggered by some preference? > > Or a one liner: > Smalltalk upgrade > > Possible with a warning (muteable) to avoid unintended executions, and > enable unattended (i.e. scripted) upgrades. > > Regards. Or even also something like Smalltalk snapshotAndUpgrade or Smalltalk saveImageAndUpgrade That way the images current state is saved or snapshotted and if the upgrade messes everything up, you are back to where you were before the upgrade. Just a thought. Jimmie

May 20, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Sergi Reyner

2014-05-20 22:00 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2014-05-20 17:21 GMT-03:00 Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com>: > > > If we are prepared to see it failing, it does not really matter, it's in > the > > contract... > > The only problem is to be aware of this contract and avoid negative > > impression. > > Maybe an advanced menu triggered by some preference? > > Or a one liner: > Smalltalk upgrade > > Possible with a warning (muteable) to avoid unintended executions, and > enable unattended (i.e. scripted) upgrades. > > Regards. > > +1!

May 20, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Esteban A. Maringolo

2014-05-20 17:21 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > If we are prepared to see it failing, it does not really matter, it's in the > contract... > The only problem is to be aware of this contract and avoid negative > impression. > Maybe an advanced menu triggered by some preference? Or a one liner: Smalltalk upgrade Possible with a warning (muteable) to avoid unintended executions, and enable unattended (i.e. scripted) upgrades. Regards.

May 20, 2014

Re: [Pharo-dev] Aconcagua Hashing Bug?

by Sean P. DeNigris

Maximiliano Taborda wrote > Seeing the same with aconcagua > ... > teaspoons := BaseUnit named: 'teaspoons'. > aHalfTeaspoon := Measure amount: 1/2 unit: teaspoons. > anotherHalfTeaspoon := Measure amount: 0.5 unit: teaspoons. > > "#hash" > aHalfTeaspoon hash = anotherHalfTeaspoon hash "this evaluate to true" > > So, I don't see where is the bug. It seems to only appear when comparing measures with derived units... baseUnit := BaseUnit named: 'tablespoon'. unit := ProportionalDerivedUnit baseUnit: baseUnit conversionFactor: 1/3 named: 'teaspoon'. m1 := Measure amount: 1/2 unit: unit. m2 := Measure amount: 0.5 unit: unit. m1 hash = m2 hash. "this evaluate to false" ----- Cheers, Sean -- View this message in context: http://forum.world.st/Aconcagua-Hashing-Bug-tp4759622p4759745.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 20, 2014

Re: [Pharo-dev] Grant for MetaRepoForPharo30

by Sean P. DeNigris

Maximiliano Taborda wrote > I decided to not update the config from the aconcagua repo, and maintain > up > to date only the one in the meta repo Right now: - main repo has 3.1.1 and 3.1.4 - meta for 30 has 3.1.2 and 3.1.3 Maximiliano Taborda wrote > I don't see the point of "copy" the same package in more than one repo. Neither did I at first, but I've found through painful exprience that people find projects through all different routes, and if they stumble upon the main repo and load an out-dated config, they may write the project off as unmaintained or reach out for support before finding out that they have to go to metarepofor30 to get the latest config. Maximiliano Taborda wrote > is a craziness thinking in publish to more > than one repo the same config just in one action? That would be welcome. I've wished for that at times, and didn't get around to implementing it... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Grant-for-MetaRepoForPharo30-tp4755362p4759742.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 20, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Nicolas Cellier

2014-05-20 21:52 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi Nicolas, > > I completely agree with you. I was wondering what is the relevance of > having the âSoftware updateâ menu entry if it does not work? > > Maybe it should be simply removed? It will make menu shorter and less > error prone. > > Alexandre > > Well, I allways favoured updating to downloading and restarting from scratch - it's less involved, like I don't re-install a linux from scratch more than once or twice a year, and I'm sure I'm not alone. If we are prepared to see it failing, it does not really matter, it's in the contract... The only problem is to be aware of this contract and avoid negative impression. Maybe an advanced menu triggered by some preference? Nicolas -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 20, 2014, at 1:49 PM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > > > 2014-05-20 4:42 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > > Some students have also tried to update Pharo using the update stream. > Is this still used? Should nt it be removed > > > > Alexandre > > > > > > How I see it: > > > > Pharo team wants to perform deep changes into the system. > > Pharo team wants to perform those changes fast, and not be swamped like > they think squeak is > > (it sure was! but let's say that Squeak values backward compatibility > which is naturally a drag). > > > > It might be difficult/take a long time to find a way to perform these > changes in a reproducible way in customers' images. > > So the philosophy it let updateStream tools available, but do not bother > with update stream if it's too difficult. > > It's without any guaranty and I often saw it fail (once every few dozens > of updates...) > > > > I'd say keep it as is. > > > > Nicolas > > > > > > > Le 19-05-2014 Ã 15:49, kilon alios <kilon.alios(a)gmail.com> a Ã©crit : > > > > > > I felt adventurous today, so I said what the hell lets try to update > Pharo with the updater tool. So I used world menu navigated to system and > choose software update. And after a long download and method's compiling > the attached image appeared :) > > > > > > > > > > > > > > > <Screen Shot 2014-05-19 at 22.46.28.png> > > > > > > >

May 20, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Alexandre Bergel

Hi Nicolas, I completely agree with you. I was wondering what is the relevance of having the âSoftware updateâ menu entry if it does not work? Maybe it should be simply removed? It will make menu shorter and less error prone. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On May 20, 2014, at 1:49 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > 2014-05-20 4:42 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Some students have also tried to update Pharo using the update stream. Is this still used? Should nt it be removed > > Alexandre > > > How I see it: > > Pharo team wants to perform deep changes into the system. > Pharo team wants to perform those changes fast, and not be swamped like they think squeak is > (it sure was! but let's say that Squeak values backward compatibility which is naturally a drag). > > It might be difficult/take a long time to find a way to perform these changes in a reproducible way in customers' images. > So the philosophy it let updateStream tools available, but do not bother with update stream if it's too difficult. > It's without any guaranty and I often saw it fail (once every few dozens of updates...) > > I'd say keep it as is. > > Nicolas > > > > Le 19-05-2014 Ã 15:49, kilon alios <kilon.alios(a)gmail.com> a Ã©crit : > > > > I felt adventurous today, so I said what the hell lets try to update Pharo with the updater tool. So I used world menu navigated to system and choose software update. And after a long download and method's compiling the attached image appeared :) > > > > > > > > > > <Screen Shot 2014-05-19 at 22.46.28.png> > >

May 20, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Sven Van Caekenberghe

On 20 May 2014, at 19:49, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > 2014-05-20 4:42 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Some students have also tried to update Pharo using the update stream. Is this still used? Should nt it be removed > > Alexandre > > > How I see it: > > Pharo team wants to perform deep changes into the system. > Pharo team wants to perform those changes fast, and not be swamped like they think squeak is > (it sure was! but let's say that Squeak values backward compatibility which is naturally a drag). > > It might be difficult/take a long time to find a way to perform these changes in a reproducible way in customers' images. > So the philosophy it let updateStream tools available, but do not bother with update stream if it's too difficult. > It's without any guaranty and I often saw it fail (once every few dozens of updates...) > > I'd say keep it as is. Pretty good summary, maybe we should make it less accessible... > Nicolas > > > > Le 19-05-2014 Ã 15:49, kilon alios <kilon.alios(a)gmail.com> a Ã©crit : > > > > I felt adventurous today, so I said what the hell lets try to update Pharo with the updater tool. So I used world menu navigated to system and choose software update. And after a long download and method's compiling the attached image appeared :) > > > > > > > > > > <Screen Shot 2014-05-19 at 22.46.28.png> > >

May 20, 2014