Re: [Pharo-dev] code loading performance

On Fri, Dec 6, 2019 at 5:08 PM George Ganea wrote: > Hi all, > > Currently loading GToolkit takes quite some time (arount 18 minutes at the > best of times) we were wondering if there’s been any attempts at improving > code loading times in Metacello/Monticello. Or mabye there are some ideas >

[Pharo-dev] [Pharo 8.0] Build #1048: 5323-5320-Code-completion-failure-on-method-name

There is a new Pharo build available! The status of the build #1048 was: SUCCESS. The Pull Request #5330 was integrated: "5323-5320-Code-completion-failure-on-method-name" Pull request url: https://github.com/pharo-project/pharo/pull/5330 Issue Url:

Re: [Pharo-dev] code loading performance

Thank you Sven, we’re already skipping writing to the epicea log, I’m now wondering can we also skip the notifications or not really? Cheers, George > On 6 Dec 2019, at 19:01, Sven Van Caekenberghe wrote: > > Yes, some improvements are needed. > > There are many steps: > > - downloading

Re: [Pharo-dev] code loading performance

Hi Vincent, I will definitely try it out and report back. Thank you! George > Hi Georges, > > There have been quite some improvements those last weeks on the performance > of loading classes and methods. But we are still waiting for the > https://github.com/pharo-project/pharo/pull/5292 >

Re: [Pharo-dev] code loading performance

Yes, some improvements are needed. There are many steps: - downloading the code (networking) - loading the code (file io) - compiling the code - writing to the changes file - writing to the epicea log - system notifications - reactions to those system notifications BTW, doing a cleanup for

[Pharo-dev] [Pharo 8.0] Build #1047: Fixed issue #5271

There is a new Pharo build available! The status of the build #1047 was: SUCCESS. The Pull Request #5327 was integrated: "Fixed issue #5271" Pull request url: https://github.com/pharo-project/pharo/pull/5327 Issue Url:

Re: [Pharo-dev] code loading performance

--- Begin Message --- Hi Georges, There have been quite some improvements those last weeks on the performance of loading classes and methods. But we are still waiting for the https://github.com/pharo-project/pharo/pull/5292 to be integrated. And you have to encapsulate the loading code into:

[Pharo-dev] code loading performance

Hi all, Currently loading GToolkit takes quite some time (arount 18 minutes at the best of times) we were wondering if there’s been any attempts at improving code loading times in Metacello/Monticello. Or mabye there are some ideas on how one might start doing something like this? Cheers,

[Pharo-dev] About package deprecation

--- Begin Message --- Hi all, As everyone knows, the BlueInk and GTRecorder packages have been removed from Pharo8.0 quite rapidly https://github.com/pharo-project/pharo/issues/5217. And it breaks the loading of other projects on Pharo8.0, like Roassal2. Some claims that those packages

Re: [Pharo-dev] [Pharo 8.0] Build #1040: [easyReview] fixing comment typos

Maybe this? https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pending%20pull%20request%20and%20branch%20Pipeline/detail/Pharo8.0/1040/pipeline : Error: Bad BitBlt arg (Fraction?); proceed to convert. GrafPort(Object)>>error: GrafPort(BitBlt)>>copyBits

[Pharo-dev] [Pharo 8.0] Build #1046: 5300-Traits-categories-are-not-updated-when-rebuilding-classes

There is a new Pharo build available! The status of the build #1046 was: SUCCESS. The Pull Request #5301 was integrated: "5300-Traits-categories-are-not-updated-when-rebuilding-classes" Pull request url: https://github.com/pharo-project/pharo/pull/5301 Issue Url: