Re: [Pharo-dev] Baseline/Configuration loading bars

I would guess the problem with doing this pervasively is (IIUC) that Configurations are self-contained/self-bootstrapping so each Configurationhas its own copy of #load (I've no access to an Image to check right now) Perhaps it could be a use case for metalinks. When Configurations are loaded,

Re: [Pharo-dev] [Pharo-users] potentially useful diagrams

Thanks Stef. They will be very useful. I presume the simpler one is for projects you own, and the other is contributing to third-party projects. It would be good to be explicit by adding such a title to distinguish them. If your software allows, it might be enhanced by: * adding sequence numbers

Re: [Pharo-dev] Stuck trying to contribute

I'm in the process to push out of the cliff all the material I have written and not released over the year. On Tue, Oct 31, 2017 at 12:27 PM, Sven Van Caekenberghe wrote: > > >> On 31 Oct 2017, at 11:52, Stephane Ducasse wrote: >> >> Sven >> >> have a

Re: [Pharo-dev] Baseline/Configuration loading bars

Agreed! On Tue, Oct 31, 2017 at 9:42 PM, Jan Blizničenko wrote: > Hello > > I have never paid any attention to following thing, but now I use Pharo to > teach students object oriented programming and there is one thing that I > realized how very bad is from user experience

[Pharo-dev] Baseline/Configuration loading bars

Hello I have never paid any attention to following thing, but now I use Pharo to teach students object oriented programming and there is one thing that I realized how very bad is from user experience perspective: When I am loading package with lots of dependencies, like Moose or Seaside, it may

Re: [Pharo-dev] [Iceberg] Couple of bugs/problems on Iceberg

4) OK, here is a more heavy issue I keep reviewing that PR and it looks like NOT all commits changes are being correctly diffED in the UI. For example, look at the attached picture of commit 3ca50bb with description "Ignore 7th field of lsof". As you can see, it shows NO diff no changes, empty

[Pharo-dev] [Pharo 7.0-dev] Build #248: 20599 make kernel independent of deprecated file stream

There is a new Pharo build available! The status of the build #248 was: SUCCESS. The Pull Request #415 was integrated: "20599 make kernel independent of deprecated file stream" Pull request url: https://github.com/pharo-project/pharo/pull/415 Issue Url:

Re: [Pharo-dev] Github API on github

Hi, This looks interesting. Maybe I should migrate Thermite into using some of this bindings. In Thermite I am using my custom wrapper for the GitHub API, Best regards, Ronie 2017-10-30 13:50 GMT-03:00 Torsten Bergmann : > Hi Guille, > > nice. Instead of just two we can merge

[Pharo-dev] [Pharo 7.0-dev] Build #247: 20609-defaultBackgroundColor-should-be-removed-from-Object

There is a new Pharo build available! The status of the build #247 was: SUCCESS. The Pull Request #414 was integrated: "20609-defaultBackgroundColor-should-be-removed-from-Object" Pull request url: https://github.com/pharo-project/pharo/pull/414 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #246: 20155-Browse-implementers-of-in-Nautilus-doesnt-parse-source-code-properly-for-methods-in-a-block

There is a new Pharo build available! The status of the build #246 was: FAILURE. The Pull Request #410 was integrated: "20155-Browse-implementers-of-in-Nautilus-doesnt-parse-source-code-properly-for-methods-in-a-block" Pull request url: https://github.com/pharo-project/pharo/pull/410

[Pharo-dev] [Pharo 7.0-dev] Build #245: 18391-Debugger must guard against actions on process termination

There is a new Pharo build available! The status of the build #245 was: SUCCESS. The Pull Request #409 was integrated: "18391-Debugger must guard against actions on process termination" Pull request url: https://github.com/pharo-project/pharo/pull/409 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #244: 20581-Manually-resolved-dependencies-in-manifests-need-update

There is a new Pharo build available! The status of the build #244 was: SUCCESS. The Pull Request #391 was integrated: "20581-Manually-resolved-dependencies-in-manifests-need-update" Pull request url: https://github.com/pharo-project/pharo/pull/391 Issue Url:

Re: [Pharo-dev] [IMPORTANT] STOP THE WORLD: Please do not contribute today, we are going to migrate to tonel

+100! Doru > On Oct 31, 2017, at 11:50 AM, Stephane Ducasse > wrote: > > Tx guys! > > > On Tue, Oct 31, 2017 at 11:09 AM, Esteban Lorenzano > wrote: >> Hi, >> >> Subject says pretty much all: we are going to handle the migration to Tonel >>

[Pharo-dev] [Pharo 7.0-dev] Build #243: 20584-SortFunction-should-not-use-block-in-collator

There is a new Pharo build available! The status of the build #243 was: SUCCESS. The Pull Request #412 was integrated: "20584-SortFunction-should-not-use-block-in-collator" Pull request url: https://github.com/pharo-project/pharo/pull/412 Issue Url:

Re: [Pharo-dev] Stuck trying to contribute

> On 31 Oct 2017, at 11:52, Stephane Ducasse wrote: > > Sven > > have a look at the TipsAndTricks new booklet available at > http://books.pharo.org. There is a configuration for iceberg that sets and > reduce > the pain for me. Ah, OK, found it. Thanks. Nice

Re: [Pharo-dev] Stuck trying to contribute

Sven have a look at the TipsAndTricks new booklet available at http://books.pharo.org. There is a configuration for iceberg that sets and reduce the pain for me. Stef On Tue, Oct 31, 2017 at 10:51 AM, Esteban Lorenzano wrote: > > > On 31 Oct 2017, at 10:37, Guillermo

Re: [Pharo-dev] [IMPORTANT] STOP THE WORLD: Please do not contribute today, we are going to migrate to tonel

Tx guys! On Tue, Oct 31, 2017 at 11:09 AM, Esteban Lorenzano wrote: > Hi, > > Subject says pretty much all: we are going to handle the migration to Tonel > today. > It will be more or less like this: > > - we will merge all mergable pull requests. > - we will close

[Pharo-dev] [IMPORTANT] STOP THE WORLD: Please do not contribute today, we are going to migrate to tonel

Hi, Subject says pretty much all: we are going to handle the migration to Tonel today. It will be more or less like this: - we will merge all mergable pull requests. - we will close not-mergable ones and we will ask to re-submit with new format later. - we will do a PR with the conversion

[Pharo-dev] [Pharo 7.0-dev] Build #242: 20602 file locator local directory should be inside image directory

There is a new Pharo build available! The status of the build #242 was: SUCCESS. The Pull Request #419 was integrated: "20602 file locator local directory should be inside image directory" Pull request url: https://github.com/pharo-project/pharo/pull/419 Issue Url:

Re: [Pharo-dev] Stuck trying to contribute

> On 31 Oct 2017, at 10:37, Guillermo Polito wrote: > > If you give me precise instructions I can update the post :) precise instructions is: - do not use https, use ssh - if you do not follow our recommendation and you insist on use https, add your credentials

Re: [Pharo-dev] Stuck trying to contribute

> On 31 Oct 2017, at 10:37, Guillermo Polito wrote: > > If you give me precise instructions I can update the post :) I am still learning, trying to understand all aspects, I am hardly ready to tell others what to do. Another question: after doing a full cycle

Re: [Pharo-dev] Stuck trying to contribute

If you give me precise instructions I can update the post :) On Mon, Oct 30, 2017 at 10:03 PM, Sven Van Caekenberghe wrote: > I think I succeeded: > > https://pharo.fogbugz.com/f/cases/20613/Improve-some-UUID-comments > https://github.com/pharo-project/pharo/pull/420 > > It does

[Pharo-dev] [Pharo 7.0-dev] Build #241: 20613-Improve-some-UUID-comments

There is a new Pharo build available! The status of the build #241 was: SUCCESS. The Pull Request #420 was integrated: "20613-Improve-some-UUID-comments" Pull request url: https://github.com/pharo-project/pharo/pull/420 Issue Url: https://pharo.fogbugz.com/f/cases/20613 Build Url:

Re: [Pharo-dev] Layout for placing widgets

On 28-10-17 16:26, Stephane Ducasse wrote: I was reading ... I will see if I can load cassowary in Pharo. I could get the squeaksource cassowary for morphic working without a problem, just needed some extensions and fixes for changes we made in Pharo. Stephan