Re: [Pharo-dev] Do we kill the catalog?

[Sven Van Caekenberghe]

> On 24 Apr 2018, at 00:49, monty  wrote:
> 
> +1.
> 
> Replacing is sometimes necessary (Sven's stream work is an obvious example), 
> but I don't see why Nautilus had to be junked rather than gradually evolved 
> into Calypso. And I don't see why the catalog can't be gradually evolved into 
> something better. Killing it off would be discouraging to the users who went 
> through the trouble of adding #catalogXXX methods to their configs and 
> publishing them to the meta repos. Why would they bother adopting whatever 
> replaces the catalog if they think it will just get killed off too?
> 
> ___
> montyos.wordpress.com

Nice blog, BTW!

Your XML work is much appreciated.

>> Sent: Sunday, April 22, 2018 at 9:29 AM
>> From: "Torsten Bergmann" 
>> To: pharo-dev@lists.pharo.org
>> Cc: "Pharo Development List" 
>> Subject: Re: [Pharo-dev] Do we kill the catalog?
>> 
>> Hi Stef,
>> 
>> do not worry - I'm fully relaxed. It is you - who suggested to kill the 
>> catalog - without having 
>> or proposing a suitable alternative yet. If you want to route the thread to 
>> talking about "idiots" 
>> and "assholes" you go offtopic and I guess I have nothing more to contribute 
>> to the discussion.
>> 
>> If it was not clear from my writing: I only expressed my wish that we should 
>> better improve it 
>> instead of killing it. That's all.
>> 
>> Because anytime we have a better idea we get more disruptive in what we 
>> provide ... and this 
>> leads to the unfortunate situation:
>> 
>> - that we replace our own stuff with newer ones again and again (which can 
>> but must not be good
>>   as things get more diverse and complicated over time)
>> - that users have to know how things historically have been progressed to 
>> find its way 
>>   through Pharo (including the terms and tools we use)
>> 
>> I would not see this as a rant - but rather a true effect we can spot on 
>> many places in our 
>> ecosystem already. 
>> 
>> Long story short: I would vote for the "fix" if the sole other option is to 
>> "remove".  
>> 
>> Bye
>> T.
>> 
>> 
>>> Gesendet: Samstag, 21. April 2018 um 15:31 Uhr
>>> Von: "Stephane Ducasse" 
>>> An: "Pharo Development List" 
>>> Betreff: Re: [Pharo-dev] Do we kill the catalog?
>>> 
>>> Torsten
>>> 
>>> Sometimes you should relax. Because if you remember I pushed the
>>> catalog (in fact I love it and we need a much more powerful one)
>>> and I even improved it. I made it better to automatically add MC 
>>> repositories.
>>> Of course Thierry is exagerating.
>>> 
>>> Now we should fix or remove it. Simple no?
>>> 
>>> Now you can rant in your corner thinking that I'm asshole.
>>> This is ok for me.
>>> 
>>> Stef
>>> 
>>> On Sat, Apr 21, 2018 at 3:06 PM, Torsten Bergmann  wrote:
 Even there is no learning from the past - it's deja vu all over again...
 
 
> Gesendet: Freitag, 20. April 2018 um 08:53 Uhr
> Von: "Stephane Ducasse" 
> An: "Pharo Development List" 
> Betreff: Re: [Pharo-dev] Do we kill the catalog?
> 
> Hi torsten
> 
> the wise shows the moon, the idiot sees his finger.
> 
> Stef
> 
> 
> On Thu, Apr 19, 2018 at 10:38 AM, Torsten Bergmann  wrote:
>> Now today you had loading trouble with Smacc from Catalog ... and now 
>> directly want to
>> kill catalog. Wow!
>> 
>> Sometimes I have the impression that our community tries to reinvent 
>> itself each day
>> doing it differently (but not only better) instead of extending, 
>> improving and supporting
>> what we have have done before. Which sometimes is good ... but not 
>> always.
>> 
>> Thx
>> T.
>> 
>>> Gesendet: Donnerstag, 19. April 2018 um 08:42 Uhr
>>> Von: "Stephane Ducasse" 
>>> An: "Pharo Development List" 
>>> Betreff: [Pharo-dev] Do we kill the catalog?
>>> 
>>> Hi guys
>>> 
>>> What do we do with it?
>>> What alternatives?
>>> 
>>> Stef
>>> 
>>> 
>> 
> 
> 
 
>>> 
>>> 
>> 
>> 
> 

Re: [Pharo-dev] Do we kill the catalog?

[monty]

+1.

Replacing is sometimes necessary (Sven's stream work is an obvious example), 
but I don't see why Nautilus had to be junked rather than gradually evolved 
into Calypso. And I don't see why the catalog can't be gradually evolved into 
something better. Killing it off would be discouraging to the users who went 
through the trouble of adding #catalogXXX methods to their configs and 
publishing them to the meta repos. Why would they bother adopting whatever 
replaces the catalog if they think it will just get killed off too?

___
montyos.wordpress.com


> Sent: Sunday, April 22, 2018 at 9:29 AM
> From: "Torsten Bergmann" 
> To: pharo-dev@lists.pharo.org
> Cc: "Pharo Development List" 
> Subject: Re: [Pharo-dev] Do we kill the catalog?
>
> Hi Stef,
> 
> do not worry - I'm fully relaxed. It is you - who suggested to kill the 
> catalog - without having 
> or proposing a suitable alternative yet. If you want to route the thread to 
> talking about "idiots" 
> and "assholes" you go offtopic and I guess I have nothing more to contribute 
> to the discussion.
> 
> If it was not clear from my writing: I only expressed my wish that we should 
> better improve it 
> instead of killing it. That's all.
> 
> Because anytime we have a better idea we get more disruptive in what we 
> provide ... and this 
> leads to the unfortunate situation:
> 
>  - that we replace our own stuff with newer ones again and again (which can 
> but must not be good
>as things get more diverse and complicated over time)
>  - that users have to know how things historically have been progressed to 
> find its way 
>through Pharo (including the terms and tools we use)
> 
> I would not see this as a rant - but rather a true effect we can spot on many 
> places in our 
> ecosystem already. 
> 
> Long story short: I would vote for the "fix" if the sole other option is to 
> "remove".  
> 
> Bye
> T.
> 
> 
> > Gesendet: Samstag, 21. April 2018 um 15:31 Uhr
> > Von: "Stephane Ducasse" 
> > An: "Pharo Development List" 
> > Betreff: Re: [Pharo-dev] Do we kill the catalog?
> >
> > Torsten
> > 
> > Sometimes you should relax. Because if you remember I pushed the
> > catalog (in fact I love it and we need a much more powerful one)
> >  and I even improved it. I made it better to automatically add MC 
> > repositories.
> > Of course Thierry is exagerating.
> > 
> > Now we should fix or remove it. Simple no?
> > 
> > Now you can rant in your corner thinking that I'm asshole.
> > This is ok for me.
> > 
> > Stef
> > 
> > On Sat, Apr 21, 2018 at 3:06 PM, Torsten Bergmann  wrote:
> > > Even there is no learning from the past - it's deja vu all over again...
> > >
> > >
> > >> Gesendet: Freitag, 20. April 2018 um 08:53 Uhr
> > >> Von: "Stephane Ducasse" 
> > >> An: "Pharo Development List" 
> > >> Betreff: Re: [Pharo-dev] Do we kill the catalog?
> > >>
> > >> Hi torsten
> > >>
> > >> the wise shows the moon, the idiot sees his finger.
> > >>
> > >> Stef
> > >>
> > >>
> > >> On Thu, Apr 19, 2018 at 10:38 AM, Torsten Bergmann  
> > >> wrote:
> > >> > Now today you had loading trouble with Smacc from Catalog ... and now 
> > >> > directly want to
> > >> > kill catalog. Wow!
> > >> >
> > >> > Sometimes I have the impression that our community tries to reinvent 
> > >> > itself each day
> > >> > doing it differently (but not only better) instead of extending, 
> > >> > improving and supporting
> > >> > what we have have done before. Which sometimes is good ... but not 
> > >> > always.
> > >> >
> > >> > Thx
> > >> > T.
> > >> >
> > >> >> Gesendet: Donnerstag, 19. April 2018 um 08:42 Uhr
> > >> >> Von: "Stephane Ducasse" 
> > >> >> An: "Pharo Development List" 
> > >> >> Betreff: [Pharo-dev] Do we kill the catalog?
> > >> >>
> > >> >> Hi guys
> > >> >>
> > >> >> What do we do with it?
> > >> >> What alternatives?
> > >> >>
> > >> >> Stef
> > >> >>
> > >> >>
> > >> >
> > >>
> > >>
> > >
> > 
> > 
> 
> 

Re: [Pharo-dev] [squeak-dev] How to yellow click with two buttons without changing mouse settings?

[Eliot Miranda]

Hi Marcel,

On Sun, Apr 22, 2018 at 11:24 PM, Marcel Taeumel 
wrote:

> Hi Jakob,
>
> do: "HandMorph showEvents: true" then do CTRL+RED/LEFT. You will see that
> you get, in fact, a yellow click. I think that there is code that checks
> for "control pressed" first to show the different menu. So, we do emulate
> that yellow-click in the VM, but we keep the "control pressed"-flag. So,
> the event state is different, even though you get "event
> yellowButtonPressed = true" both times.
>
> To sum up some prior thoughts on this topic:
> 1) The VM should not provide this single-button-mouse behavior but the
> image should.
> 2) The event filters to simulate those yellow/blue clicks are already
> possible in the image. We do it with mouse-wheel vs. CTRL+up/down already.
> 3) A good transformation for CTRL+RED in such a single-button-mouse mode
> would be YELLOW and not CTRL+YELLOW.
>
> Anyway, this is not an easy fix or decision to make. :-)
>

What would be relatively straight-forward is to add an image property flag
alongside the ones in the image flag word such as "floats in platform
order", "processPreemptionYields", etc in vm parameter 48.  This flag would
tell the VM not to do any event modifications (or at least no mouse button
swapping).  And then we could at least experiment with allowing the image
to perform event modification, making this a preference, etc, before some
fine day in the future, transitioning away from VM support for event
modification in a major release.  Thoughts?


> Best,
> Marcel
>
> Am 21.04.2018 14:35:43 schrieb Jakob Reschke :
> Hello,
>
> I downloaded a VM (64 bit Cog Spur Windows) and a fresh trunk image
> separately and have not changed any mouse button settings yet (swap
> mouse buttons preference is on and neither 1 button mouse nor 3 button
> mouse are selected in the VM preferences menu). My notebook does not
> have a middle "mouse" button and the right button currently does a
> blue click (opens the halo).
>
> In this default setting, is there any way to do a yellow click?
>
> I get the morph menu with ctrl+left click and in list morphs and on
> the world I can invoke the menu with the Esc key, but I did not find a
> modifier+button combination that would work universally to emulate a
> yellow click. Have I missed it?
>
> After disabling swap mouse buttons, right click becomes a yellow
> click. But when the preference is on, both right click and alt+left
> click produce a blue click. So with a two button mouse it seems that
> nothing is actually swapped, but one button is unavailable
> altogether...
>
> A simple solution would be to turn the preference off by default.
>
> Kind regards,
> Jakob
>
>
>
>
>


-- 
_,,,^..^,,,_
best, Eliot

Re: [Pharo-dev] Esteban's ChangeLog week of 16 April 2018

[Alexandre Bergel]

Thanks Esteban. 
I really appreciate your log. 

Cheers,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



> On Apr 23, 2018, at 3:00 AM, esteba...@gmail.com wrote:
> 
> Hello!
> 
> This is my weekly ChangeLog, from 16 April 2018 to 22 April 2018.
> You can see it in a better format by going here: 
> http://log.smallworks.eu/web/search?from=16/4/2018=22/4/2018
> 
> ChangeLog
> =
> 
> 16 April 2018:
> --
> 
> *I finally updated Alien package into Pharo according to Torsten package 
> modifications.
> 
>This was [case: 20878](https://pharo.fogbugz.com/f/cases/20878)
> 
>And PR can be seen here: 
> [https://github.com/pharo-project/pharo/pull/1202](https://github.com/pharo-project/pharo/pull/1202)
> 
> 
> cheers! 
> Esteban
> 

[Pharo-dev] [Pharo 7.0-dev] Build #800: 20020-Collectionaverage-throw-a-ZeroDivide-when-the-collection-is-empty

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #800 was: SUCCESS.

The Pull Request #1230 was integrated: 
"20020-Collectionaverage-throw-a-ZeroDivide-when-the-collection-is-empty"
Pull request url: https://github.com/pharo-project/pharo/pull/1230

Issue Url: https://pharo.fogbugz.com/f/cases/20020
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/800/

[Pharo-dev] [Pharo 7.0-dev] Build #799: 21597 Deprecate initialColorInSystemWindow: as it has no sender

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #799 was: SUCCESS.

The Pull Request #1123 was integrated: "21597 Deprecate 
initialColorInSystemWindow: as it has no sender"
Pull request url: https://github.com/pharo-project/pharo/pull/1123

Issue Url: https://pharo.fogbugz.com/f/cases/21597
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/799/

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

[Marcus Denker]

> On 23 Apr 2018, at 12:47, Torsten Bergmann  wrote:
> 
> Hi Sven
> 
> if you like you can also use my 
> "https://github.com/astares/pharo-contributor; - at least 
> on Ubuntu (where I wrote, tested and use it)
> 
Ah, yes, this reminds me to  have a look at your contribution tool again, too. 
(Next week… after holidays).

Marcus

Re: [Pharo-dev] Using P3 to connect to CockroachDB

[p...@highoctane.be]

Excellent news!

Phil

On Mon, Apr 23, 2018 at 11:33 AM, Sven Van Caekenberghe 
wrote:

> Hi,
>
> Just a quick note: it is possible to use P3 (the lean and mean PostgreSQL
> client for Pharo using frontend/backend protocol 3.0,
> https://github.com/svenvc/P3) to connect to CockroachDB (an SQL database
> for global cloud services, an open source clone of Google Spannner,
> https://www.cockroachlabs.com) as it supports the same line protocol.
>
> Just make sure to load the latest version of P3 (and ZTimestamp when you
> are on Pharo 7).
>
> If you do their tutorial, you can set up your connection as follows:
>
>   P3Client url: 'psql://root@localhost:26257/bank'.
>
> Sven
>

Re: [Pharo-dev] Is Beacon still planned to be added to P7?

[Tudor Girba]

I hope so. Beacon is ready to be integrated, but I do not know if there is 
enough bandwidth right now due to the Iceberg work.

Doru

> On Apr 23, 2018, at 1:08 PM, Peter Uhnák  wrote:
> 
> Hi,
> 
> in several older discussions there was a mention of Beacon logger being added 
> to Pharo 7 (by default)... is that still the plan?
> 
> Thanks,
> Peter

--
www.tudorgirba.com
www.feenk.com

"It's not how it is, it is how we see it."

[Pharo-dev] Is Beacon still planned to be added to P7?

[Peter Uhnák]

Hi,

in several older discussions there was a mention of Beacon logger being
added to Pharo 7 (by default)... is that still the plan?

Thanks,
Peter

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

[Torsten Bergmann]

Hi Sven

if you like you can also use my "https://github.com/astares/pharo-contributor; 
- at least 
on Ubuntu (where I wrote, tested and use it)

- just clone the project
- use "download.sh" to download latest P7 automatically and started, it will 
also load a contribution 
  help book I did where all is explained

- For a quick start usually you just have to go to the very last help page of 
the appearing help tool and click 
  on 

CPTCloneTool run

  to automagically download and update you fork (after giving your Github 
username)

Then you can contribute as usual by having a branch for a bug number in Iceberg 
and so on. 

Side note:
=
Currently new Iceberg still has some trouble:
 - one has to discard the changes on Fuel (as there are none) after the 
automatic synch of the tool
 - one has to "LGitLibrary initialize" when one reopens a saved image (see 
start.sh), otherwise VM will crash
I already notfied Esteban.

For questions on my workflow with the tool: I'm usually available on Discord.

I'm sure there will also be an update of the official contribution tutorial and 
AFAIK Esteban
want to do some screencasts. 

Thx
T.


> Gesendet: Montag, 23. April 2018 um 11:38 Uhr
> Von: "Sven Van Caekenberghe" 
> An: "Pharo Development List" 
> Betreff: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?
>
> Hi,
> 
> I got the new Iceberg working on the latest Pharo 7 (used it to commit 
> something to P3) - authentication should be OK then I guess. It feels much 
> better.
> 
> I would like to try contributing to Pharo again.
> 
> Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo 
> been updated for the new Iceberg ?
> 
> Have things become simpler ?
> 
> I also forgot the easy/short git command to bring my fork up to date (if I 
> have to do this myself).
> 
> Sven
> 
> 
> 

[Pharo-dev] [Pharo 7.0-dev] Build #798: 21762-The-System-browser-world-menu-registration-should-be-done-in-Tool-Base-package

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #798 was: SUCCESS.

The Pull Request #1242 was integrated: 
"21762-The-System-browser-world-menu-registration-should-be-done-in-Tool-Base-package"
Pull request url: https://github.com/pharo-project/pharo/pull/1242

Issue Url: https://pharo.fogbugz.com/f/cases/21762
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/798/

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

[Marcus Denker]

>> 
>> we are finishing an iteration that will speed things up.
>> IMO it should be a lot simpler, but well. 
>> Tomorrow I will record a new “how to contribute”.
> 
> OK, I will wait a day or two.
> But please (someone) also write a short document.
> 

I will update the description with the content of the video 
(and I will makes sure that all outdate content is not linked to)

Marcus

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

[Sven Van Caekenberghe]

> On 23 Apr 2018, at 12:03, Esteban Lorenzano  wrote:
> 
> 
> 
>> On 23 Apr 2018, at 11:46, Marcus Denker  wrote:
>> 
>> 
>> 
>>> On 23 Apr 2018, at 11:38, Sven Van Caekenberghe  wrote:
>>> 
>>> Hi,
>>> 
>>> I got the new Iceberg working on the latest Pharo 7 (used it to commit 
>>> something to P3) - authentication should be OK then I guess. It feels much 
>>> better.
>>> 
>>> I would like to try contributing to Pharo again.
>>> 
>>> Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo 
>>> been updated for the new Iceberg ?
>>> 
>> No, not yet…
>> 
>>> Have things become simpler ?
>>> 
>> 
>> 
>> The ways that I found how to do it: no. But I need more input from Esteban, 
>> I am for sure doing things wrong.
>> (this is why I did not start to update the tutorial with the way I am doing 
>> PRs now)
> 
> we are finishing an iteration that will speed things up.
> IMO it should be a lot simpler, but well. 
> Tomorrow I will record a new “how to contribute”.

OK, I will wait a day or two.
But please (someone) also write a short document.

> Esteban
> 
>> 
>>  Marcus

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

[Esteban Lorenzano]

> On 23 Apr 2018, at 11:46, Marcus Denker  wrote:
> 
> 
> 
>> On 23 Apr 2018, at 11:38, Sven Van Caekenberghe  wrote:
>> 
>> Hi,
>> 
>> I got the new Iceberg working on the latest Pharo 7 (used it to commit 
>> something to P3) - authentication should be OK then I guess. It feels much 
>> better.
>> 
>> I would like to try contributing to Pharo again.
>> 
>> Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo 
>> been updated for the new Iceberg ?
>> 
> No, not yet…
> 
>> Have things become simpler ?
>> 
> 
> 
> The ways that I found how to do it: no. But I need more input from Esteban, I 
> am for sure doing things wrong.
> (this is why I did not start to update the tutorial with the way I am doing 
> PRs now)

we are finishing an iteration that will speed things up.
IMO it should be a lot simpler, but well. 
Tomorrow I will record a new “how to contribute”.

Esteban

> 
>   Marcus

[Pharo-dev] [Pharo 7.0-dev] Build #797: 21744-load-the-Deprecated70-as-the-very-latest-package

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #797 was: SUCCESS.

The Pull Request #1228 was integrated: 
"21744-load-the-Deprecated70-as-the-very-latest-package"
Pull request url: https://github.com/pharo-project/pharo/pull/1228

Issue Url: https://pharo.fogbugz.com/f/cases/21744
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/797/

Re: [Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

[Marcus Denker]

> On 23 Apr 2018, at 11:38, Sven Van Caekenberghe  wrote:
> 
> Hi,
> 
> I got the new Iceberg working on the latest Pharo 7 (used it to commit 
> something to P3) - authentication should be OK then I guess. It feels much 
> better.
> 
> I would like to try contributing to Pharo again.
> 
> Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo 
> been updated for the new Iceberg ?
> 
No, not yet…

> Have things become simpler ?
> 


The ways that I found how to do it: no. But I need more input from Esteban, I 
am for sure doing things wrong.
(this is why I did not start to update the tutorial with the way I am doing PRs 
now)

Marcus

[Pharo-dev] 'Contribute a fix to Pharo' for new Iceberg ?

[Sven Van Caekenberghe]

Hi,

I got the new Iceberg working on the latest Pharo 7 (used it to commit 
something to P3) - authentication should be OK then I guess. It feels much 
better.

I would like to try contributing to Pharo again.

Has https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo been 
updated for the new Iceberg ?

Have things become simpler ?

I also forgot the easy/short git command to bring my fork up to date (if I have 
to do this myself).

Sven

[Pharo-dev] Using P3 to connect to CockroachDB

[Sven Van Caekenberghe]

Hi,

Just a quick note: it is possible to use P3 (the lean and mean PostgreSQL 
client for Pharo using frontend/backend protocol 3.0, 
https://github.com/svenvc/P3) to connect to CockroachDB (an SQL database for 
global cloud services, an open source clone of Google Spannner, 
https://www.cockroachlabs.com) as it supports the same line protocol. 

Just make sure to load the latest version of P3 (and ZTimestamp when you are on 
Pharo 7).

If you do their tutorial, you can set up your connection as follows:

  P3Client url: 'psql://root@localhost:26257/bank'.

Sven

Re: [Pharo-dev] [Pharo 7.0-dev] Build #796: 21761-change-asDoItIn-to-asDoItForContext

[Marcus Denker]

For AST evaluation I continue to improve things step-by-step.

e.g. this PR

-  improves the method that wraps ASTs into doit-methods in the case where we 
want to execute for a certain context (#asDoItForContext: does all the magic of 
rewriting temps and adding a return)
-  OpalCompiler>>#parse was radically simplifies by using asDoItForContext: and 
#asDoit.
-  I started to rewrite all users of the #translate method of the compiler 
which will be deprecated later (as you can either use #parse or #compile).

More to come, step by step…


> On 23 Apr 2018, at 11:02, ci-pharo-ci-jenki...@inria.fr wrote:
> 
> There is a new Pharo build available!
>   
> The status of the build #796 was: SUCCESS.
> 
> The Pull Request #1241 was integrated: 
> "21761-change-asDoItIn-to-asDoItForContext"
> Pull request url: https://github.com/pharo-project/pharo/pull/1241
> 
> Issue Url: https://pharo.fogbugz.com/f/cases/21761
> Build Url: 
> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/796/

[Pharo-dev] [Pharo 7.0-dev] Build #796: 21761-change-asDoItIn-to-asDoItForContext

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #796 was: SUCCESS.

The Pull Request #1241 was integrated: 
"21761-change-asDoItIn-to-asDoItForContext"
Pull request url: https://github.com/pharo-project/pharo/pull/1241

Issue Url: https://pharo.fogbugz.com/f/cases/21761
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/796/

[Pharo-dev] [Pharo 7.0-dev] Build #795: 21761-change-asDoItIn-to-asDoItForContext

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #795 was: FAILURE.

The Pull Request #1241 was integrated: 
"21761-change-asDoItIn-to-asDoItForContext"
Pull request url: https://github.com/pharo-project/pharo/pull/1241

Issue Url: https://pharo.fogbugz.com/f/cases/21761
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/795/

[Pharo-dev] [Pharo 7.0-dev] Build #794: 21753-Integrate-Calypso-0112

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #794 was: FAILURE.

The Pull Request #1238 was integrated: "21753-Integrate-Calypso-0112"
Pull request url: https://github.com/pharo-project/pharo/pull/1238

Issue Url: https://pharo.fogbugz.com/f/cases/21753
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/794/

[Pharo-dev] Esteban's ChangeLog week of 16 April 2018

[estebanlm]

Hello!

This is my weekly ChangeLog, from 16 April 2018 to 22 April 2018.
You can see it in a better format by going here: 
http://log.smallworks.eu/web/search?from=16/4/2018=22/4/2018

ChangeLog
=

16 April 2018:
--

*I finally updated Alien package into Pharo according to Torsten package 
modifications.

This was [case: 20878](https://pharo.fogbugz.com/f/cases/20878)

And PR can be seen here: 
[https://github.com/pharo-project/pharo/pull/1202](https://github.com/pharo-project/pharo/pull/1202)


cheers! 
Esteban