[Pharo-dev] Bloc: Ominous Black External Window

Everything was working "okay" (although the examples seemed very slow to respond). Then, without apparent cause, now BlBasicExamples>>exampleGeometry (and all the other examples I tried) show a native window with blank (black) contents. Why is that happening and how does one debug something like

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

Good idea, but what I will also like is for QA to take advantage of the wasted space in the status bar and display info that is related to the line the cursor is currently located. If the cursor is not enables then QA can display its general info.

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

I think that I will start with having it disabled at the beginning. Because the current implementation of icon annotator does not work for classes and it is not asynchronous which means that for large classes and maybe for some methods it may be not efficient. Oh yes, and let’s not forget

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

You just need to add method annotateRubricText: self sourceTextModel to the end of AbstractNautilusUI>>#addIconStyle Definitely this is greatly possible because Markus has nice implementation of these icon annotations. Uko > On 1 Dec 2016, at 14:45, Denis Kudriashov

Re: [Pharo-dev] Set internal array size

The Set implementation requires the array to have a size > 0. (Set basicNew initialize: 0) add: #x "Error Zero Devide" Best regards, Henrik -Original Message- From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Christophe Demarey Sent: Thursday, December 1, 2016

Re: [Pharo-dev] Set internal array size

> Le 1 déc. 2016 à 15:04, Marcus Denker a écrit : > > The idea that a set is always created with a minimal size is because we > always add at least some elements not always. You know in some cases 80% of the time, your instances will have an empty Set and with some

Re: [Pharo-dev] Set internal array size

The idea that a set is always created with a minimal size is because we always add at least some elements to them. We at some point increased that size (from 3 to 5?). The difference comes from Set sizeFor: 1 ==> 7 HashedCollection>>#sizeFor: has a special case for small (<4) elements, while

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

2016-12-01 14:44 GMT+01:00 Denis Kudriashov : > 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 :)

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

2016-12-01 10:12 GMT+01:00 Yuriy Tymchuk : > 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?

Re: [Pharo-dev] Set internal array size

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

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

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

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

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

Re: [Pharo-dev] Set internal array size

Wow, great explanation/example ! > On 1 Dec 2016, at 13:25, Henrik Nergaard 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 :=

Re: [Pharo-dev] Set internal array size

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

[Pharo-dev] [pharo-project/pharo-core]

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

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

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e3c5ff705873a29fd229e88443c857ec041effad https://github.com/pharo-project/pharo-core/commit/e3c5ff705873a29fd229e88443c857ec041effad Author: Jenkins Build Server Date:

Re: [Pharo-dev] How to report website text bugs?

I found the transcript output from a few days ago when I did it - it was the following (which shows that initial error on the eval example) macta$ curl get.pharo.org | bash % Total% Received % Xferd Average Speed TimeTime Time Current Dload

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

Is there anything in the VM code beyond having to move more pixels around for the the bit blitting? macOS VM has the display split into zones and updates as needed. Of course, there are more bits to bang to the display but is this a reason for not having that working? I have no retina display,

[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

[Pharo-dev] Pharo Newsletter November16 ready

… we are really getting better to do a monthly newsletter. Target are people outside of the community (wo want to follow a bit but not read e.g. these lists). Just one day late. If you want to get the newsletter, subscribe here: http://eepurl.com/byhgL9 The

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

2016-12-01 10:19 GMT+01:00 Esteban Lorenzano : > 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

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

> On 1 Dec 2016, at 10:12, Yuriy Tymchuk wrote: > > Hi everyone, > > I suspect that many of people want to have their Nautilus transformed into > something like this: > > > yes, the critiques are inlined. In fact I just needed to add 1 line of code, > a the solution