- Pharo-dev - lists.pharo.org

Athens based game worked on windows and pharo 60 :)

by stepharong

Hi esteban Today during the labs at the university, we verified with the latest VM on windows that the athens based game that the students were improving is working with Pharo 60 (while some weeks ago when they tried it did not). Stef --

March 10, 2017

Re: [Pharo-dev] Catalog projects in Spotter

by stepharong

On Fri, 10 Mar 2017 20:38:27 +0100, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2017-03-10 20:18 GMT+01:00 stepharong <stepharong(a)free.fr>: >> Torsten >> >> Why are you full of bad energy? >> Having a setting is perfectly ok. Why all this bad energy. > > The problem is not having a setting, the problem is to have *two* > distinct settings for the same thing. Yes and this can be fixed to have only one. I do not see the problem. And I'm in favor to have one and I was never against it. Stef > > >> >> Do you think that this is nice to hear that I push solution for fucking >> african idiots? >> I spent so much time writing and producing solutions for newbies. >> I just spent three months fixing the Pharo by example book and THIS IS >> NOT MY JOB. >> Do you think that writing a full mooc that we can use to promote Pharo >> all over the world >> is not important? I was not in the mood to write it. For my CV a mooc >> is nothing. >> Zero impact. >> You see when people evaluate my CV I got feedback like >> "stephane is a brillant researcher but he is focusing too much >> on poor languages." >> And many other things. >> So now you can be aggressive and pissed. I decided long time ago that I >> do Pharo for positive >> energy. Now if you do not like what I'm doing I cannot do much. >> >> Stef >> >> >> >> >>> Uko wrote: >>>> If there is a rule not to duplicate preferences, why is catalog not >>>> following it? >>> >>> Because at the time when I implemented it for catalog there was no >>> other setting. >>> >>> The enabling/disabling for all GT extension was introduced later. Also >>> the confusing >>> default was introduced later (with the more hidden spotter extension >>> disabled and >>> leaving the Catalog setting enabled) leading to this whole mess. >>> >>> To be honest I dont care or respond anymore on the whole issue because >>> as we now know from >>> the long discussion the only outcome is that: >>> >>> <sarcasm> >>> - most of us should be knowledgable enough to know that two settings >>> exist >>> - most of us should become experts in fixing deficencies with startup >>> scripts >>> - most of us should accept that we have to hide features as deep as >>> possible in the settings tree >>> - most of us should accept that we have to make it as complicated as >>> possible to load catalog projects >>> - most of us should accept that we can display and access anything in >>> spotter except catalog projects >>> - most of us should accept that Pharo videos get broken and never >>> match reality >>> - most of us should continue to "rest in their comfort zone" >>> - most of us should continue to be "an egoist instead of being an >>> adult" >>> - most of us should be allowed to speak up only when they presented >>> Pharo at a university >>> - most of us should start working with slow networks >>> </sarcasm> >>> >>> Fixing it by removing Spotter and Catalog completely from Pharo would >>> possibly be the >>> best solution. Anyone up for a slice? >>> >>> Bye >>> T. >>> >> >> >> --Using Opera's mail client: http://www.opera.com/mail/ >> > -- Using Opera's mail client: http://www.opera.com/mail/

March 10, 2017

Re: [Pharo-dev] Catalog projects in Spotter

by Nicolai Hess

2017-03-10 20:18 GMT+01:00 stepharong <stepharong(a)free.fr>: > Torsten > > Why are you full of bad energy? > Having a setting is perfectly ok. Why all this bad energy. > The problem is not having a setting, the problem is to have *two* distinct settings for the same thing. > > Do you think that this is nice to hear that I push solution for fucking > african idiots? > I spent so much time writing and producing solutions for newbies. > I just spent three months fixing the Pharo by example book and THIS IS NOT > MY JOB. > Do you think that writing a full mooc that we can use to promote Pharo all > over the world > is not important? I was not in the mood to write it. For my CV a mooc is > nothing. > Zero impact. > You see when people evaluate my CV I got feedback like > "stephane is a brillant researcher but he is focusing too much on > poor languages." > And many other things. > So now you can be aggressive and pissed. I decided long time ago that I do > Pharo for positive > energy. Now if you do not like what I'm doing I cannot do much. > > Stef > > > > > Uko wrote: >> >>> If there is a rule not to duplicate preferences, why is catalog not >>> following it? >>> >> >> Because at the time when I implemented it for catalog there was no other >> setting. >> >> The enabling/disabling for all GT extension was introduced later. Also >> the confusing >> default was introduced later (with the more hidden spotter extension >> disabled and >> leaving the Catalog setting enabled) leading to this whole mess. >> >> To be honest I dont care or respond anymore on the whole issue because as >> we now know from >> the long discussion the only outcome is that: >> >> <sarcasm> >> - most of us should be knowledgable enough to know that two settings >> exist >> - most of us should become experts in fixing deficencies with startup >> scripts >> - most of us should accept that we have to hide features as deep as >> possible in the settings tree >> - most of us should accept that we have to make it as complicated as >> possible to load catalog projects >> - most of us should accept that we can display and access anything in >> spotter except catalog projects >> - most of us should accept that Pharo videos get broken and never match >> reality >> - most of us should continue to "rest in their comfort zone" >> - most of us should continue to be "an egoist instead of being an adult" >> - most of us should be allowed to speak up only when they presented >> Pharo at a university >> - most of us should start working with slow networks >> </sarcasm> >> >> Fixing it by removing Spotter and Catalog completely from Pharo would >> possibly be the >> best solution. Anyone up for a slice? >> >> Bye >> T. >> >> > > -- > Using Opera's mail client: http://www.opera.com/mail/ > >

March 10, 2017

Re: [Pharo-dev] Catalog projects in Spotter

by stepharong

Torsten Why are you full of bad energy? Having a setting is perfectly ok. Why all this bad energy. Do you think that this is nice to hear that I push solution for fucking african idiots? I spent so much time writing and producing solutions for newbies. I just spent three months fixing the Pharo by example book and THIS IS NOT MY JOB. Do you think that writing a full mooc that we can use to promote Pharo all over the world is not important? I was not in the mood to write it. For my CV a mooc is nothing. Zero impact. You see when people evaluate my CV I got feedback like "stephane is a brillant researcher but he is focusing too much on poor languages." And many other things. So now you can be aggressive and pissed. I decided long time ago that I do Pharo for positive energy. Now if you do not like what I'm doing I cannot do much. Stef > Uko wrote: >> If there is a rule not to duplicate preferences, why is catalog not >> following it? > > Because at the time when I implemented it for catalog there was no other > setting. > > The enabling/disabling for all GT extension was introduced later. Also > the confusing > default was introduced later (with the more hidden spotter extension > disabled and > leaving the Catalog setting enabled) leading to this whole mess. > > To be honest I dont care or respond anymore on the whole issue because > as we now know from > the long discussion the only outcome is that: > > <sarcasm> > - most of us should be knowledgable enough to know that two settings > exist > - most of us should become experts in fixing deficencies with startup > scripts > - most of us should accept that we have to hide features as deep as > possible in the settings tree > - most of us should accept that we have to make it as complicated as > possible to load catalog projects > - most of us should accept that we can display and access anything in > spotter except catalog projects > - most of us should accept that Pharo videos get broken and never > match reality > - most of us should continue to "rest in their comfort zone" > - most of us should continue to be "an egoist instead of being an > adult" > - most of us should be allowed to speak up only when they presented > Pharo at a university > - most of us should start working with slow networks > </sarcasm> > > Fixing it by removing Spotter and Catalog completely from Pharo would > possibly be the > best solution. Anyone up for a slice? > > Bye > T. > -- Using Opera's mail client: http://www.opera.com/mail/

March 10, 2017

Re: [Pharo-dev] image not opening.

by Cyril Ferlicot

On ven. 10 mars 2017 at 18:42, stepharong <stepharong(a)free.fr> wrote: > We found the problem with Guillermo and this may be a problem of the last > VM. > > The image got its starting window size really small: some pixels on some > pixles. > So may be the metadata of the image are systematically corrupted. > > Hi > > I have a jenkins that produce an image that does not start > when I try to open it locally. > > Now if I take the image and load the "same" configuration I get a working > image > > I have not idea how to debug that. > > Stef > > > > > -- > Using Opera's mail client: http://www.opera.com/mail/ > If it can help: here is the build: https://ci.inria.fr/pharo-contribution/job/OOnoz/ > <http://www.opera.com/mail/> > It is happening in almost all Pharo 6 builds -- Cheers Cyril Ferlicot

March 10, 2017

Re: [Pharo-dev] image not opening.

by stepharong

We found the problem with Guillermo and this may be a problem of the last VM. The image got its starting window size really small: some pixels on some pixles. So may be the metadata of the image are systematically corrupted. > Hi > I have a jenkins that produce an image that does not start > when I try to open it locally. > > Now if I take the image and load the "same" configuration I get a > working image > > I have not idea how to debug that. > > Stef -- Using Opera's mail client: http://www.opera.com/mail/

March 10, 2017

Re: [Pharo-dev] [Pharo-users] What is the craziest bug you ever face

by stepharong

Hi phil are the bug entered in fogbougz? Stef On Thu, 09 Mar 2017 22:11:13 +0100, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Figuring out why my image balloons to 500+ megs and is not shrinking > despite new compactor was a nice one + fact that it took 2 minutes to > start. > > Fixed yesterday with the help of Clement and Pavel. > > First, there was a massive leak of memory from the devtools. > > https://gist.github.com/philippeback/39c63bb5aa26b79098511cdfea4fea7e > fixed it (got the image back to 130 megs, which was ok given the amount > of loaded code). > > Then looking at the startup times to find out the culprit: > > https://gist.github.com/philippeback/9b6645c62b4cda7c0d4559880fbbe40f > > Save/Stop/Start and then inspect LOG11. > > This gaves us entry related to FT2Settings talking the lion share of the > delay. Looks like this was because it was refreshing fonts at startup. > On my Windows box is was 650 font >entries. On Ben's Linux this was > 1500+. > Ben advised to change this > > FTHandle>>pvtDestroyHandle,try commenting out the last statement... > FT2HandleallSubInstancesDo: [ :each | (handleToRelease = each handle) > ifTrue: [ each beNull ] ] > > This indeed made things faster even with the setting. No proof that will > be not leading to more trouble b/c this code supports the workaround for > FT2Handle duplicates (that FT2 >bug alone deserves a cake too by itself). > > So, things are back to normal now in that image and nothing had to do > with my own code. > > Thx again for the help. And compactor works wonderfully indeed. Note > that current figures in the VM Stats are completely bogus at places and > need to be rewritten/recomputed >since we are using Spur and things are > not the way they used to be. I took plenty of notes from what Clement > told me. Hope to integrate that into the MemoryMonitor at one >point. > > Phil > > > -- Using Opera's mail client: http://www.opera.com/mail/

March 10, 2017

Re: [Pharo-dev] Fwd: Where are the Metacello ConfigurationOfYourProject supposed to be?

by stepharong

Nicolas Since a couple of years already we have one MetaRepo per version MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo60' user: 'StephaneDucasse' password: '' MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo50' user: 'StephaneDucasse' password: '' MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo40' user: 'StephaneDucasse' password: '' MCSmalltalkhubRepository owner: 'Pharo' project: 'MetaRepoForPharo30' user: 'StephaneDucasse' password: '' You see it is in place since Pharo 30 :). We are working on a single place (web site) to publish packages but also the package metadata. The problem right now is that we cannot verify/publish a configuration without loading it. The idea is to have kind of distributions of packages working and validated vs. a folder full of possible packages I hated so much the squeak catalog because 5 times on 6 nothing worked. Stef

March 10, 2017

Pharo Association event listing updated

by Marcus Denker

Hi, I added all events (tech talks, sprints, pharodays) that will happen till June here: https://association.pharo.org/events Marcus

March 10, 2017

Re: [Pharo-dev] image not opening.

by Cyril Ferlicot D.

On 10/03/2017 15:27, Stephane Ducasse wrote: > Hi > > I have a jenkins that produce an image that does not start > when I try to open it locally. > > Now if I take the image and load the "same" configuration I get a > working image > > I have not idea how to debug that. > > Stef Hi, I have the same problem, only on the Pharo 6 builds. And sometimes it crash while launching the tests. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

March 10, 2017