On Tue, Jan 3, 2017 at 8:40 PM, Denis Kudriashov wrote:
>
> 2016-12-31 16:57 GMT+01:00 Ben Coman :
>>
>> Maybe it is the checkbox doubling the size of the whitespace (??) such
>> that it would be better placed to the right (??), or maybe I just need
>>
Hi Guille,
On Tue, Jan 3, 2017 at 1:40 PM, Guillermo Polito
wrote:
>
> On Tue, Jan 3, 2017 at 8:56 PM, Eliot Miranda
> wrote:
>>
>> On Tue, Jan 3, 2017 at 2:24 AM, Henrik Johansen <
>> henrik.s.johan...@veloxit.no> wrote:
>>
> [snip]
> 2)
On Tue, Jan 3, 2017 at 8:56 PM, Eliot Miranda
wrote:
>
>
> On Tue, Jan 3, 2017 at 2:24 AM, Henrik Johansen <
> henrik.s.johan...@veloxit.no> wrote:
>
>> It was my impression there was a procedure in place earlier for moving
>> methods from SmalltalkImage to classes with
On Tue, Jan 3, 2017 at 2:24 AM, Henrik Johansen <
henrik.s.johan...@veloxit.no> wrote:
> It was my impression there was a procedure in place earlier for moving
> methods from SmalltalkImage to classes with a more singular responsibility
> that ensures a smooth upgrade experience;
> 1) create
Thanks Guillermo.
@pharoers
I think that one of the key point to understand what we did is that we
decided not to go deep first to produce a minimal minimal image.
Because we have one: Guille produced candlelight and it is working on
Pharo and it can do beep and nothing else because it does
Hi Phil,
On Sat, Dec 31, 2016 at 10:14 AM, philippe.b...@highoctane.be <
philippe.b...@gmail.com> wrote:
> Isn't there a typo in the first exptession?
>
> Also the list contains a lot of RB things. What purpose do they have in a
> bootstrap image?
>
Yes, that is because the bootstrap image
2016-12-31 16:57 GMT+01:00 Ben Coman :
> Maybe it is the checkbox doubling the size of the whitespace (??) such
> that it would be better placed to the right (??), or maybe I just need
> to adapt.
>
In last version (dev) I push it to the right.
Also I moved extensions group
It was my impression there was a procedure in place earlier for moving methods
from SmalltalkImage to classes with a more singular responsibility that ensures
a smooth upgrade experience;
1) create accessor method on Smalltalk (if none of the existing are appropriate)
2) implement the old