Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Do you think professional developers who use Pharo all day like crashes or hangs ? We are all the same here, we want a stable system. It is not certain that the catalog download is the problem. This specific feature that you think should only be enabled by those who want it (you call them

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

> On 08 Jul 2016, at 12:21, stepharo wrote: > > > > Le 8/7/16 à 11:44, Sven Van Caekenberghe a écrit : >> Do you think professional developers who use Pharo all day like crashes or >> hangs ? We are all the same here, we want a stable system. >> >> It is not certain that

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Le 8/7/16 à 11:44, Sven Van Caekenberghe a écrit : Do you think professional developers who use Pharo all day like crashes or hangs ? We are all the same here, we want a stable system. It is not certain that the catalog download is the problem. This specific feature that you think should

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Do you think professional developers who use Pharo all day like crashes or hangs ? We are all the same here, we want a stable system. It is not certain that the catalog download is the problem. This specific feature that you think should only be enabled by those who want it (you call them

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Again again and again: How many times do you see students having Pharo frozen because the internet connection in the classroom is fleaky. Apparently turning off these people is not an issue to you. Perfect but it is one for me. For your productivity boost why can't you click on one setting

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

I have to add here… solution is bad, because now projects are not shown EVEN if I activate it in settings :( > On 06 Jul 2016, at 12:28, Esteban Lorenzano wrote: > > yes, I do not agree either but is true there where problems. > but IMO this would be solved just by

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Hi Ben, On Wed, Jul 6, 2016 at 5:16 PM, Ben Coman wrote: > On Thu, Jul 7, 2016 at 2:19 AM, Sven Van Caekenberghe > wrote: > > I'll try once more to explain. > > > > You like the catalog, don't you ? It was your idea in the first place. > With this feature

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

On Thu, Jul 7, 2016 at 2:19 AM, Sven Van Caekenberghe wrote: > I'll try once more to explain. > > You like the catalog, don't you ? It was your idea in the first place. With > this feature you can just type XML, CSV, JSON or whatever and it will suggest > a couple of catalog

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

+1 On Wed, Jul 6, 2016 at 8:19 PM, Sven Van Caekenberghe wrote: > I'll try once more to explain. > > You like the catalog, don't you ? It was your idea in the first place. > With this feature you can just type XML, CSV, JSON or whatever and it will > suggest a couple of catalog

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

I'll try once more to explain. You like the catalog, don't you ? It was your idea in the first place. With this feature you can just type XML, CSV, JSON or whatever and it will suggest a couple of catalog projects that you can install with just one click, no need to open any tool you don't

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Who vote to put it in? Seriously I think that my main concern is about getting Pharo stable in any occasion and not giving a bad impression of the system. I takes enough time to build traction and such glitches can spoil our effort in no time. "Yes Pharo froze." So it would be nice to

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

> On 06 Jul 2016, at 13:51, Andrei Chis wrote: > > > On Wed, Jul 6, 2016 at 12:28 PM, Esteban Lorenzano > wrote: > yes, I do not agree either but is true there where problems. > but IMO this would be solved just by putting a timeout in 1-2s

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

On Wed, Jul 6, 2016 at 12:28 PM, Esteban Lorenzano wrote: > yes, I do not agree either but is true there where problems. > but IMO this would be solved just by putting a timeout in 1-2s (and then > run in background, and cache results) > not turning it off. > in for my

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

yes, I do not agree either but is true there where problems. but IMO this would be solved just by putting a timeout in 1-2s (and then run in background, and cache results) not turning it off. in for my experience, turning something off is equivalent to remove the feature (but then is worst,

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

> On 06 Jul 2016, at 10:12, Sven Van Caekenberghe wrote: > > >> On 06 Jul 2016, at 09:52, GitHub wrote: >> >> 18674 Turn spotter catalog off by default >> https://pharo.fogbugz.com/f/cases/18674 > > We did not agree on this, at all, there was no public

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

> On 06 Jul 2016, at 09:52, GitHub wrote: > > 18674 Turn spotter catalog off by default > https://pharo.fogbugz.com/f/cases/18674 We did not agree on this, at all, there was no public discussion, no vote.

[Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ec7b0efd3372758bb785c059576ee2264986477b https://github.com/pharo-project/pharo-core/commit/ec7b0efd3372758bb785c059576ee2264986477b Author: Jenkins Build Server Date: