Re: [Pharo-dev] what is the relationship between Float and its subclasses?

2016-02-01 Thread stepharo
What about something like that My instances hold 64-bit Floats in heap objects. This is the only representation on 32-bit systems. But on 64-bit systems SmallFloat64 holds a subset of the full 64-bit double-precision range in immediate objects. BoxedFloat64 is the classical VM Float, two

Re: [Pharo-dev] what is the relationship between Float and its subclasses?

2016-02-01 Thread stepharo
Tx nicolas I read SmallFloat64: My instances represent 64-bit Floats whose exponent fits in 8 bits as immediate objects. This representation is only available on 64-bit systems, not 32-bit systems. BoxedFloat64: My instances hold 64-bit Floats in heap objects. This is the only representat

Re: [Pharo-dev] what is the relationship between Float and its subclasses?

2016-02-01 Thread Nicolas Cellier
SmallFloat is like SmallInteger: immediate value encoded in oop, and it is only for 64 bits Spur VM. Boxed is the classical VM Float, two 4-bytes word allocated per Float, and is both for 32 bits VM and Float values not fitting in immediate format (3 bits have been stolen from exponent...). 2016-0

[Pharo-dev] what is the relationship between Float and its subclasses?

2016-02-01 Thread stepharo
Hi I'm updating Pharo by example and the relationship between Float and its subclasses is unclear to me. Do we only get instances of the subclasses now? I got that Boxed is only for 64 bits. But SmallFloat? The class comment is not really self describing. Stef

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Nicolai Hess
2016-02-01 16:40 GMT+01:00 stepharo : > so do we define a bug entry? > no, not needed. > > Le 1/2/16 10:51, Esteban Lorenzano a écrit : > > > On 01 Feb 2016, at 08:24, Nicolai Hess < > nicolaih...@gmail.com> wrote: > > > > 2016-01-31 21:52 GMT+01:00 Cyril Ferlicot Delbecque < > cyril.ferli...@

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread stepharo
so do we define a bug entry? Le 1/2/16 10:51, Esteban Lorenzano a écrit : On 01 Feb 2016, at 08:24, Nicolai Hess > wrote: 2016-01-31 21:52 GMT+01:00 Cyril Ferlicot Delbecquemailto:cyril.ferli...@gmail.com>>: On 31/01/2016 15:23, stepharo wrote: > H

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

2016-02-01 Thread GitHub
Branch: refs/tags/50561 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] afa2b4: 50561

2016-02-01 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: afa2b45f1e0ff28642f0f75e1616b02da6115a87 https://github.com/pharo-project/pharo-core/commit/afa2b45f1e0ff28642f0f75e1616b02da6115a87 Author: Jenkins Build Server Date: 2016-02-01 (Mon, 01 Feb 2016

Re: [Pharo-dev] Pharo contribution CI problem

2016-02-01 Thread Norbert Hartl
> Am 01.02.2016 um 12:31 schrieb Christophe Demarey > : > > > Le 1 févr. 2016 à 12:25, Norbert Hartl a écrit : > >> Christophe, >> >>> Am 01.02.2016 um 12:18 schrieb Christophe Demarey >>> : >>> >>> Hi Norbert, >>> >>> Le 1 févr. 2016 à 11:09, Norbert Hartl a écrit : >>> I created a

Re: [Pharo-dev] Pharo contribution CI problem

2016-02-01 Thread Christophe Demarey
Le 1 févr. 2016 à 12:31, Christophe Demarey a écrit : > > Le 1 févr. 2016 à 12:25, Norbert Hartl a écrit : > >> Christophe, >> >>> Am 01.02.2016 um 12:18 schrieb Christophe Demarey >>> : >>> >>> Hi Norbert, >>> >>> Le 1 févr. 2016 à 11:09, Norbert Hartl a écrit : >>> I created a new b

Re: [Pharo-dev] Pharo contribution CI problem

2016-02-01 Thread Christophe Demarey
Le 1 févr. 2016 à 12:25, Norbert Hartl a écrit : > Christophe, > >> Am 01.02.2016 um 12:18 schrieb Christophe Demarey >> : >> >> Hi Norbert, >> >> Le 1 févr. 2016 à 11:09, Norbert Hartl a écrit : >> >>> I created a new build on the pharo contribution CI. But regardless what I >>> enter in t

Re: [Pharo-dev] Pharo contribution CI problem

2016-02-01 Thread Norbert Hartl
Christophe, > Am 01.02.2016 um 12:18 schrieb Christophe Demarey > : > > Hi Norbert, > > Le 1 févr. 2016 à 11:09, Norbert Hartl a écrit : > >> I created a new build on the pharo contribution CI. But regardless what I >> enter in the axis for the PHARO variable the build is triggered with >> "

Re: [Pharo-dev] Pharo contribution CI problem

2016-02-01 Thread Christophe Demarey
Hi Norbert, Le 1 févr. 2016 à 11:09, Norbert Hartl a écrit : > I created a new build on the pharo contribution CI. But regardless what I > enter in the axis for the PHARO variable the build is triggered with > "default" as PHARO version. > > Any hints how to change that? Is this a bug? It is

Re: [Pharo-dev] Pharo contribution CI problem

2016-02-01 Thread Christophe Demarey
Le 1 févr. 2016 à 12:36, Norbert Hartl a écrit : > >> Am 01.02.2016 um 12:31 schrieb Christophe Demarey >> : >> >> >> Le 1 févr. 2016 à 12:25, Norbert Hartl a écrit : >> >>> Christophe, >>> Am 01.02.2016 um 12:18 schrieb Christophe Demarey : Hi Norbert, Le 1

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Esteban Lorenzano
> On 01 Feb 2016, at 08:24, Nicolai Hess wrote: > > > > 2016-01-31 21:52 GMT+01:00 Cyril Ferlicot Delbecque >: > > > On 31/01/2016 15:23, stepharo wrote: > > Hi guys > > > > Thanks for this fix. > > I will start recording videos. > > > > Stef > > > > > In

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Cyril Ferlicot Delbecque
On 01/02/2016 09:01, Nicolai Hess wrote: > > > The problem is, that TextLink is a base class of the RubTextLink classes > and those of course are used during > styling. The debugger message is misleading (due to this awfull > #doesNotUnderstand redirection) but if you > look at the call stack,

[Pharo-dev] Pharo contribution CI problem

2016-02-01 Thread Norbert Hartl
I created a new build on the pharo contribution CI. But regardless what I enter in the axis for the PHARO variable the build is triggered with "default" as PHARO version. Any hints how to change that? Is this a bug? thanks, Norbert

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Nicolai Hess
2016-02-01 8:57 GMT+01:00 Cyril Ferlicot : > > > On Monday, 1 February 2016, Nicolai Hess wrote: > >> >> >> 2016-02-01 8:37 GMT+01:00 Cyril Ferlicot Delbecque < >> cyril.ferli...@gmail.com>: >> >>> >>> >>> On 01/02/2016 08:24, Nicolai Hess wrote: >>> > >>> > unlikely, many 'icon'-methods are now

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Cyril Ferlicot
On Monday, 1 February 2016, Nicolai Hess wrote: > > > 2016-02-01 8:37 GMT+01:00 Cyril Ferlicot Delbecque < > cyril.ferli...@gmail.com > >: > >> >> >> On 01/02/2016 08:24, Nicolai Hess wrote: >> > >> > unlikely, many 'icon'-methods are now rendered as 'unimplemeted' >> > methods, because >> > Them

Re: [Pharo-dev] Warning in Pharo 5

2016-02-01 Thread Andrei Chis
Currently GTDebugger doesn't work with the pre-debug window. I'll fix this shortly. Cheers, Andrei On Sun, Jan 31, 2016 at 6:58 PM, Cyril Ferlicot Delbecque < cyril.ferli...@gmail.com> wrote: > > On 31/01/2016 18:33, Esteban Lorenzano wrote: > > probably this is the default… which it should not!

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

2016-02-01 Thread Esteban Lorenzano
but layoutProperties are not immutable so if you receive an instance of NullLayoutProperties (singleton), and you do something like this: myMorph cellInset: 5, you has to check for correct properties anyway… that’s why is implemented as this: cellInset: aNumber "Layout specific. This

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Nicolai Hess
2016-02-01 8:37 GMT+01:00 Cyril Ferlicot Delbecque : > > > On 01/02/2016 08:24, Nicolai Hess wrote: > > > > unlikely, many 'icon'-methods are now rendered as 'unimplemeted' > > methods, because > > ThemeIcons uses #doesNotUnderstand indirection to create the named > > icons. And that seems to work

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Cyril Ferlicot Delbecque
On 01/02/2016 08:24, Nicolai Hess wrote: > > unlikely, many 'icon'-methods are now rendered as 'unimplemeted' > methods, because > ThemeIcons uses #doesNotUnderstand indirection to create the named > icons. And that seems to work > well. > And the error about > > RubShoutStylerDecorator(Object

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

2016-02-01 Thread Nicolai Hess
2016-01-31 21:52 GMT+01:00 Cyril Ferlicot Delbecque < cyril.ferli...@gmail.com>: > > > On 31/01/2016 15:23, stepharo wrote: > > Hi guys > > > > Thanks for this fix. > > I will start recording videos. > > > > Stef > > > > > In the last image I get errors all the time when I use unimplemented > me

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

2016-02-01 Thread stepharo
A good solution is to have share by default and instance-based when needed. For that use a classVariable to instantiate only one NullLayoutProperties use an instance variable that points to it by default one demand change the instance variable to point to a new created instance

Re: [Pharo-dev] Unused ugly morph methods...

2016-02-01 Thread stepharo
It is forbidden by contract :) 100% I like that What would be great is that we can create QA rules dedicated to Bloc and Brick. On Jan 31, 2016 9:31 PM, "stepharo" > wrote: I really hope that Bloc will forbid such systematic submorphs use because it lead

Re: [Pharo-dev] Rubric: spotter with preview leaks some memory

2016-02-01 Thread Nicolai Hess
2016-01-31 14:52 GMT+01:00 Nicolai Hess : > > > 2016-01-31 13:46 GMT+01:00 Tudor Girba : > >> Hi, >> >> Hmm. I work with Spotter with preview enabled all the time… but I do not >> seem to get to the point in which I have to kill the styling process. How >> do the signs look like (maybe I am not lo