January 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Latest image and VM on Windows looks monochromatic

by Gabriel Cotelli

Nice, I will test it when the image is ready :) On Tue, Jan 31, 2017 at 10:24 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Solution on the way: > > https://pharo.fogbugz.com/f/cases/19635/DisplayScreen-has-depth-1-on-Linux > > evaluate "DisplayScreen initialize" to fix your image > > 2017-01-31 14:19 GMT+01:00 Gabriel Cotelli <g.cotelli(a)gmail.com>: > >> https://pharo.fogbugz.com/f/cases/19636/UI-is-black-and-white-in-Windows >> >> >> â >> > >

Jan. 31, 2017

Re: [Pharo-dev] Latest image and VM on Windows looks monochromatic

by Pavel Krivanek

Solution on the way: https://pharo.fogbugz.com/f/cases/19635/DisplayScreen-has-depth-1-on-Linux evaluate "DisplayScreen initialize" to fix your image 2017-01-31 14:19 GMT+01:00 Gabriel Cotelli <g.cotelli(a)gmail.com>: > https://pharo.fogbugz.com/f/cases/19636/UI-is-black-and-white-in-Windows > > > â >

Jan. 31, 2017

Latest image and VM on Windows looks monochromatic

by Gabriel Cotelli

https://pharo.fogbugz.com/f/cases/19636/UI-is-black-and-white-in-Windows â

Jan. 31, 2017

Re: [Pharo-dev] Memory leaks

by Pavel Krivanek

2017-01-31 13:42 GMT+01:00 stepharong <stepharong(a)free.fr>: > Thanks John > > For the record we are investigating a leak on points. > In pharo 60 we discovered that in certain images I could have 300 000 or > more points. :) > Now marcus was analysing the problems with pavel and we had the impression > that > some of the points may have been tenured too fast. > > Pavel shows that every 5 ms we get a new point. > The problem in fact is not in this increasing amount of Point instances because they are garbage collected after about 2 minutes. The problem is in the FreeTypeCache. -- Pavel > > Stef > > > > On Tue, 31 Jan 2017 05:00:47 +0100, John Brant <brant(a)refactoryworkers.com> > wrote: > > I donât know if there is an existing object reference crawler, but I >> ported mine from VW. It finds the shortest paths so it is good for finding >> the reference that is causing the memory leak. >> MCHttpRepository >> location: 'http://www.smalltalkhub.com/m >> c/JohnBrant/ReferenceFinder/main' >> user: '' >> password: ââ >> Once loaded, you can evaluate something like "ReferenceFinder >> findPathToInstanceOf: MyClassâ. That will return a reference path or nil >> if no path exists from the Smalltalk global to an instance of MyClass. If >> you want to find a path to a particular instance, you can use >> âReferenceFinder findPathTo: myInstâ. >> > > > -- > Using Opera's mail client: http://www.opera.com/mail/ > >

Jan. 31, 2017

Re: [Pharo-dev] Pharo 6 update catalog entries

by Pierce Ng

On Tue, Jan 31, 2017 at 10:44:04AM +0100, Torsten Bergmann wrote: > in preparation of upcoming Pharo 6 release we already should do a pass on > all our external loadable projects: > > You should do the same with your projects! Updated ConfigOfGlorp and ConfigOfGlorpSQLite for Pharo 6. Tested on 60365, all tests pass. Thanks for the push. Pierce

Jan. 31, 2017

Re: [Pharo-dev] Odd (and wrong) implementation of Float>>sign

by stepharong

**TX** Without bug entry it will get lost in the noise and stress. Stef > At Stef's request, I've opened case 19629 on this issue. > > On 01/27/2017 11:14 PM, Andres Valloud wrote: >>> The 2007 update of 10967 is somewhat more helpful. It replaces the >>> "sign" operation with one called "signum" which returns 1, -1, or NaN. >>> It returns 1 for positive zero and positive infinity, and -1 for >>> negative zero and negative infinity. If given a qNaN, it returns a >>> qNaN. >>> If given a signaling NaN, it returns a qNaN but notifies the >>> application >>> of an "invalid" situation. >> >> That's ISO 10967. However, IEEE-758-2008 specifies implementations >> shall provide isSignMinus(x). This operation is true if and only if x >> has negative sign, and applies to zeros and NaNs. >> >> IMO, values that operate according to IEEE-758-2008 should behave as >> specified by IEEE-758-2008 by default. The ISO 10967 standard seems >> more of a layer on top of things like IEEE-758-2008, because it's a >> standard for language agnostic arithmetic. >> >> So, shouldn't #sign behave as in IEEE-758-2008? >> >> ^self isSignMinus ifTrue: [-1] ifFalse: [1] > > I think that defining #sign this way would add to the confusion. > > IEEE-754 does not define a "sign" operation. ANSI Smalltalk and ISO/IEC > 10967 do, so it makes sense to provide a #sign that conforms to those > standards -- answering -1, 0, or 1. > > IEEE-754 does define an isSignMinus operation, answering true or false, > so it makes sense to provide that operation in addition to the ones > specified by the other standards. > >> >> It looks like the real question is whether Float's methods are merely >> renaming IEEE-758-2008 functionality (if yes, why rename at all and add >> to the confusion?), ISO 10967 functionality, or are something else >> entirely (e.g. Smalltalk provided behavior in the context of the >> Smalltalk experience). > > First and foremost, Smalltalk. The ANSI Smalltalk numeric spec is based > on 10967, but that standard lacks some operations found in IEEE-754. But > those have different names anyway, so it's easy in this case to comply > with *both* standards. > > Regards, > > -Martin > -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 31, 2017

Re: [Pharo-dev] Working with critiques in Calypso

by stepharong

super cool On Tue, 31 Jan 2017 09:56:08 +0100, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > And here screenshots of Calypso with critiques: > > > > > â > â > > 2017-01-31 9:52 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >> 2017-01-30 15:29 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >>>>> You will see new Calypso-Plugins-Critic-Browser package. I add >>>>> decorators support to TextEditorTool. And critic plugin just adds >>>>> CriticDecorator into required tools. >>> Sadly it is not working. Critiques are not shown somehow.I leave it >>> for you to fix it. Probably reason is that full tool morph is prepared >>> in background. So critiques are added when morph is not in World.I >>> hope you can find solution. >> >> And to get working critiques disable background tabs: >> >>> ClyBrowserTabTool>>addInto: aBrowser >>> >>> containerTab := TabMorph >>> label: self defaultTitle >>> icon: self defaultIcon >>> morph: self. >>> self build. >>> >>> containerTab when: #tabDeleted send: #tabDeleted to: self. >>> containerTab model: self. >>> >>> aBrowser addTab: containerTab >>> >> So question why it is not working when morph is built from background >> process? > -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 31, 2017

Re: [Pharo-dev] Pharo 6 update catalog entries

by stepharong

+1 Argh I should do mine :) > Hi, > in preparation of upcoming Pharo 6 release we already should do a pass on > all our external loadable projects: > - load them into Pharo 6 to see if they could be loaded cleanly > (due to automatic transformation of deprecated messages your packages > get dirty when converted) > - check if they are already/still working in Pharo 6 by using them > - check that the tests are running in Pharo 6 > - check that we have a proper config with catalog methods and > that the latest config is in the MetaRepoForPharo60 repository > http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo60 > I did a pass over most projects I implemented or contributed to > and we now have much more Pharo 6 based projects in catalog: > - Units, Artefact > - EventRecorder, Bugzilla, PunQlite, HubCap, VistaCursors, INIFile > - Pomodoro, DesktopManager, QuickAccess, WebBrowser, MessageFlowBrowser > - ScriptManager (now with icons) > - Tealight, Teapot, Nginx, NPMJS, GitHubAPI, FogBugz > - OSWindows, OSOSX, OSUnix, OSLinuxCentOS, OSLinuxUbuntu, OSRaspbian > - ... > You should do the same with your projects! > Also if you have a project on SqueakSource, STHub or GitHub that > is not yet in the catalog it would be good to provide a > ConfigurationOf... > with a catalog description. Using Versionner it is easy to create one > or generate the required catalog methods. > This would give more visibility to your projects! > Thanks > T. -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 31, 2017

Re: [Pharo-dev] Memory leaks

by stepharong

thierry we have pointersTo and I imagine that it is not good enough. Do you confirm? Stef On Tue, 31 Jan 2017 10:00:39 +0100, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi John, > > thanks for that tool. Have found a leak that I have been chasing like > forever... I would vote to integrate that into the base image. > > Regards, > > Thierry > > 2017-01-31 5:00 GMT+01:00 John Brant <brant(a)refactoryworkers.com>: >>> On Jan 30, 2017, at 3:57 PM, Alexandre Bergel >>> <alexandre.bergel(a)me.com> wrote: >>> >>> >>> The problem is still present. >>> Looking at the pointers >>> >>> There was an object reference crawler no? I remember someone worked on >>> this? I tried sending #pointersTo but I without much success on >>> identifying the cause of this >>leak. >>> >>> Any idea? >>> >> >> I donât know if there is an existing object reference crawler, but I >> ported mine from VW. It finds the shortest paths so it is good for >> finding the reference that is causing the >>memory leak. >> >> MCHttpRepository >> location: >> 'http://www.smalltalkhub.com/mc/JohnBrant/ReferenceFinder/main' >> user: '' >> password: ââ >> >> Once loaded, you can evaluate something like "ReferenceFinder >> findPathToInstanceOf: MyClassâ. That will return a reference path or >> nil if no path exists from the Smalltalk >>global to an instance of >> MyClass. If you want to find a path to a particular instance, you can >> use âReferenceFinder findPathTo: myInstâ. >> >> In the past, Iâve found that NECController and some compiler >> infrastructure (I forget the class) have been culprits for memory leaks >> with their caches. >> >> >>>> John Brant > -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 31, 2017

Re: [Pharo-dev] Memory leaks

by stepharong

Thanks John For the record we are investigating a leak on points. In pharo 60 we discovered that in certain images I could have 300 000 or more points. :) Now marcus was analysing the problems with pavel and we had the impression that some of the points may have been tenured too fast. Pavel shows that every 5 ms we get a new point. Stef On Tue, 31 Jan 2017 05:00:47 +0100, John Brant <brant(a)refactoryworkers.com> wrote: > I donât know if there is an existing object reference crawler, but I > ported mine from VW. It finds the shortest paths so it is good for > finding the reference that is causing the memory leak. > MCHttpRepository > location: > 'http://www.smalltalkhub.com/mc/JohnBrant/ReferenceFinder/main' > user: '' > password: ââ > Once loaded, you can evaluate something like "ReferenceFinder > findPathToInstanceOf: MyClassâ. That will return a reference path or > nil if no path exists from the Smalltalk global to an instance of > MyClass. If you want to find a path to a particular instance, you can > use âReferenceFinder findPathTo: myInstâ. -- Using Opera's mail client: http://www.opera.com/mail/

Jan. 31, 2017