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

> 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

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

+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

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

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

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

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

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

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:

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

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:

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

> 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

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

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

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

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

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

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 ?

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

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

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:

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

>> >> 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

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

> 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

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

> 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

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

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:

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

> 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

[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

[Pharo-dev] Using P3 to connect to CockroachDB

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,

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

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

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

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

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

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

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

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:

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

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