December 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Nautilus with inline QA?

by Denis Kudriashov

2016-12-01 14:44 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > yes, the critiques are inlined. In fact I just needed to add 1 line of >> code, a the solution used in the MessageBrowser can be reused. > > > Could you show this line? Full method will be better :)

Dec. 1, 2016

Re: [Pharo-dev] [Pharo-users] Pharo 5 and retina displays in 2016?

by Tim Mackinnon

To give people a better view of this - here is the Pharo image next to the mail client (Iâm not sure if the screen captures really do it justice as when you scale them down in a picture everything looks fine - however if I zoom into that bottom corner in a second image it might make it more obvious). I think this has been a problem brewing for a while, but if most contributors donât have retina screens (although they are getting much more common now) then I guess it goes unnoticed. I suspect in the next few years, as people start replacing machines - it will gain more visibility. I find it quite distracting when switching from mail or other apps to Pharo and then you notice the fuzziness. Maybe if you spend a few hours in the code you might adjust. Tim The following is the bottom corner zoom in to show what I mean by fuzzy: > On 30 Nov 2016, at 23:53, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 30/11/16 20:32, Sven Van Caekenberghe wrote: >> Maybe, but the thing is, you are looking at it half size, in some >> sense, when it is on a Retina display. Anyway, to me, it is OK, but >> my eyes are no longer what they used to be. I can imagine young >> people being more sensitive to it. > > Nah, it just is blurry. I've played a bit with krono's vm, and it is > a very noticable difference. Much better readable and less tiring. > And you mostly only notice when trying to go back from HiDPI to low. > > Stephan > >

Dec. 1, 2016

Re: [Pharo-dev] Nautilus with inline QA?

by Denis Kudriashov

2016-12-01 10:12 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > yes, the critiques are inlined. In fact I just needed to add 1 line of > code, a the solution used in the MessageBrowser can be reused. Could you show this line?

Dec. 1, 2016

Re: [Pharo-dev] Set internal array size

by Christophe Demarey

Thanks for this great explanation Henrik. Nevertheless, my question is still valid. Why Set new will give me an internal array of 5 elements while Set new: 1 will give me an internal array of 7 elements? Shouldnât Set new give an internal of 7 elements as it looks like the minimal array size for a set? Also I would expect Set new: 0 to give me an empty internal array. It explicitly ask an empty Set. A further call to #add: will increase its size as expected. > Le 1 dÃ©c. 2016 Ã 13:25, Henrik Nergaard <henrik.nergaard(a)uia.no> a Ã©crit : > > Hashed collections keep a portion of the available memory empty (usually 25%) as a partition mechanism to increase lookup speed. > > âNormal arrayâ > | col | > > col := Smalltalk allClassesAndTraits asArray. > > [ col includes: 8; includes: Morph ] bench. "'366.853 per second'" > > âNormal set ~75% loadâ > | set | > > set := Smalltalk allClassesAndTraits asSet. > > [ set includes: 8; includes: Morph ] bench. "'4,700,967 per second'" > > > âSet forced to have ~100% loadâ > | array fullLoadSet | > > array := Smalltalk allClassesAndTraits asSet asArray , #(nil). > fullLoadSet:= Set basicNew. > fullLoadSet > instVarNamed: #array put: array; > instVarNamed: #tally put: array size. > > [ fullLoadSet includes: 8; includes: Morph ] bench. "'215.157 per second'" > > > Best regards, > Henrik > > > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Christophe Demarey > Sent: Thursday, December 1, 2016 11:49 AM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] Set internal array size > > Hi, > > I just discovered a funny thing. > If you create a Set with Set new, you will get a Set with an internal array of 5 elements (hardcoded in Set class>>#new). > If you ask explicitly a Set for one or no element: Set new: 0 (or a number between 0 and 5), you will get an internal array of 7 elements. > This behavior is a bit strange. Either we always need at least 7 elements and we need to update Set class>>#new, either the method Set class>>#sizeFor: should be updated. > > WDYT? > > Christophe

Dec. 1, 2016

Re: [Pharo-dev] [Pharo-users] Pharo 5 and retina displays in 2016?

by Stephan Eggermont

On 01/12/16 08:18, Sven Van Caekenberghe wrote: > From a distance (not knowing anything about it), it seems that HDi > support was considered not important. Else more people would work on > it to fix its teething problems, no ? No, it was consider very important, second only to spur (64). Stephan

Dec. 1, 2016

Re: [Pharo-dev] Nautilus with inline QA?

by Mariano Martinez Peck

Hi Yuriy, This is much better!!! I have the Nautilus integration ON, but I admit I sometimes simply forget checking out that much below in the browser. It does not yet catch up my attention enough to watch it. Maybe it's simple that I am failing myself and compromise to watch. So......having this inline QA would really help me in that direction!! +999 Cheers, On Thu, Dec 1, 2016 at 7:27 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-12-01 10:19 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> yes please. >> this is a âfirst impressions countâ: no api change but UI change that >> makes our lives a bit better and pharo a bit cooler :) >> >> So: active by default, opening a the box in preferences. >> > > +1 > -- Mariano http://marianopeck.wordpress.com

Dec. 1, 2016

Re: [Pharo-dev] Set internal array size

by Sven Van Caekenberghe

Wow, great explanation/example ! > On 1 Dec 2016, at 13:25, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > > Hashed collections keep a portion of the available memory empty (usually 25%) as a partition mechanism to increase lookup speed. > > âNormal arrayâ > | col | > > col := Smalltalk allClassesAndTraits asArray. > > [ col includes: 8; includes: Morph ] bench. "'366.853 per second'" > > âNormal set ~75% loadâ > | set | > > set := Smalltalk allClassesAndTraits asSet. > > [ set includes: 8; includes: Morph ] bench. "'4,700,967 per second'" > > > âSet forced to have ~100% loadâ > | array fullLoadSet | > > array := Smalltalk allClassesAndTraits asSet asArray , #(nil). > fullLoadSet:= Set basicNew. > fullLoadSet > instVarNamed: #array put: array; > instVarNamed: #tally put: array size. > > [ fullLoadSet includes: 8; includes: Morph ] bench. "'215.157 per second'" > > > Best regards, > Henrik > > > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Christophe Demarey > Sent: Thursday, December 1, 2016 11:49 AM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] Set internal array size > > Hi, > > I just discovered a funny thing. > If you create a Set with Set new, you will get a Set with an internal array of 5 elements (hardcoded in Set class>>#new). > If you ask explicitly a Set for one or no element: Set new: 0 (or a number between 0 and 5), you will get an internal array of7 elements. > This behavior is a bit strange. Either we always need at least 7 elements and we need to update Set class>>#new, either the method Set class>>#sizeFor: should be updated. > > WDYT? > > Christophe

Dec. 1, 2016

Re: [Pharo-dev] Set internal array size

by Henrik Nergaard

Hashed collections keep a portion of the available memory empty (usually 25%) as a partition mechanism to increase lookup speed. "Normal array" | col | col := Smalltalk allClassesAndTraits asArray. [ col includes: 8; includes: Morph ] bench. "'366.853 per second'" "Normal set ~75% load" | set | set := Smalltalk allClassesAndTraits asSet. [ set includes: 8; includes: Morph ] bench. "'4,700,967 per second'" "Set forced to have ~100% load" | array fullLoadSet | array := Smalltalk allClassesAndTraits asSet asArray , #(nil). fullLoadSet:= Set basicNew. fullLoadSet instVarNamed: #array put: array; instVarNamed: #tally put: array size. [ fullLoadSet includes: 8; includes: Morph ] bench. "'215.157 per second'" Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Christophe Demarey Sent: Thursday, December 1, 2016 11:49 AM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] Set internal array size Hi, I just discovered a funny thing. If you create a Set with Set new, you will get a Set with an internal array of 5 elements (hardcoded in Set class>>#new). If you ask explicitly a Set for one or no element: Set new: 0 (or a number between 0 and 5), you will get an internal array of 7 elements. This behavior is a bit strange. Either we always need at least 7 elements and we need to update Set class>>#new, either the method Set class>>#sizeFor: should be updated. WDYT? Christophe

Dec. 1, 2016

[pharo-project/pharo-core]

by GitHub

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

Dec. 1, 2016

[pharo-project/pharo-core] e3c5ff: 60315

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e3c5ff705873a29fd229e88443c857ec041effad https://github.com/pharo-project/pharo-core/commit/e3c5ff705873a29fd229e884… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-12-01 (Thu, 01 Dec 2016) Changed paths: M AST-Core.package/RBBlockNode.class/instance/accessing/argumentNames.st M AST-Core.package/RBGlobalNode.class/README.md M AST-Core.package/RBMethodNode.class/instance/accessing/argumentNames.st M OpalCompiler-Core.package/OCRequestorScope.class/README.md M OpalCompiler-Tests.package/OCClosureTests.class/instance/testing/testBlockTemps.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60314.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60315.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60314.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60315.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60315 19411 improve comment RBGlobalNode for class variable https://pharo.fogbugz.com/f/cases/19411 19410 improve comment OCRequestorScope https://pharo.fogbugz.com/f/cases/19410 19400 argumentNames returns orderedCollection https://pharo.fogbugz.com/f/cases/19400 http://files.pharo.org/image/60/60315.zip

Dec. 1, 2016