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

2017-01-31 Thread Denis Kudriashov
2017-01-30 15:29 GMT+01:00 Denis Kudriashov : > 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

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread Thierry Goubier
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 : > > On Jan 30, 2017, at 3:57 PM, Alexandre Bergel > wrote: > > > > > > The problem is still pre

[Pharo-dev] Form/Spec based UI's in GT inspector extensions

2017-01-31 Thread Torsten Bergmann
Hi, there are a lot of examples for GT inspector extensions in the image. I've seen #tree(s), #list(s) or #table like UI's are used. Even a #text or an "image" displaying a morph (using #form keyword sent to the given composite). It is very easy to provide extension methods to adopt the inspe

[Pharo-dev] Pharo 6 update catalog entries

2017-01-31 Thread Torsten Bergmann
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 t

[Pharo-dev] [pharo-project/pharo-core] a1d73b: 60365

2017-01-31 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a1d73b1704d27971ef636f12e05f999c6ef7eb78 https://github.com/pharo-project/pharo-core/commit/a1d73b1704d27971ef636f12e05f999c6ef7eb78 Author: Jenkins Build Server Date: 2017-01-31 (Tue, 31 Jan 2017

[Pharo-dev] [pharo-project/pharo-core]

2017-01-31 Thread GitHub
Branch: refs/tags/60365 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread Pavel Krivanek
Very nice tool. I think it cannot find objects pointed only by a stack of some processes so it may be handy to put them to the global space. Smalltalk globals at: #Stacks put: ((Process allInstances collect: [:p | (p suspendedContext) ifNotNil: #stack ]) reject: #isNil) asOrderedCollection. (Small

Re: [Pharo-dev] Form/Spec based UI's in GT inspector extensions

2017-01-31 Thread Tudor Girba
Hi, Indeed, this is a nice observation. We currently have basic support for handling forms: - GLMSpecPresentation offers a basic integration of Spec widgets inside Glamour. This ships with the Pharo image. - GLMMagrittePresentation allows us to take a Magritte-described object and render it thr

Re: [Pharo-dev] Two listener sockets on same port

2017-01-31 Thread Henrik Johansen
> On 30 Jan 2017, at 21:13 , Denis Kudriashov wrote: > > > 2017-01-30 20:25 GMT+01:00 Sven Van Caekenberghe >: > Well, you should do your utmost best to prevent the situation in the first > place (use startup/shutdown behaviour correctly). > > I remember I had those prob

Re: [Pharo-dev] Two listener sockets on same port

2017-01-31 Thread Sven Van Caekenberghe
> On 31 Jan 2017, at 11:56, Henrik Johansen > wrote: > > >> On 30 Jan 2017, at 21:13 , Denis Kudriashov wrote: >> >> >> 2017-01-30 20:25 GMT+01:00 Sven Van Caekenberghe : >> Well, you should do your utmost best to prevent the situation in the first >> place (use startup/shutdown behaviour

Re: [Pharo-dev] Two listener sockets on same port

2017-01-31 Thread Denis Kudriashov
2017-01-31 11:56 GMT+01:00 Henrik Johansen : > IIRC, behaviour is different on all three platforms: > - Linux raises error > I got same behaviour on Debian as on Mac. It assigns different port

[Pharo-dev] [pharo-project/pharo-core]

2017-01-31 Thread GitHub
Branch: refs/tags/60366 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 605aea: 60366

2017-01-31 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 605aea3271c974e38784e70c39e4ae1009be9c4d https://github.com/pharo-project/pharo-core/commit/605aea3271c974e38784e70c39e4ae1009be9c4d Author: Jenkins Build Server Date: 2017-01-31 (Tue, 31 Jan 2017

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread 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

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread 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 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 i

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

2017-01-31 Thread 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 wh

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

2017-01-31 Thread 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 r

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

2017-01-31 Thread 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

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread Pavel Krivanek
2017-01-31 13:42 GMT+01:00 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

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

2017-01-31 Thread Gabriel Cotelli
https://pharo.fogbugz.com/f/cases/19636/UI-is-black-and-white-in-Windows ​

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

2017-01-31 Thread 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 : > https://pharo.fogbugz.com/f/cases/19636/UI-is-black-and-white-in-Windows > > > ​ >

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

2017-01-31 Thread Gabriel Cotelli
Nice, I will test it when the image is ready :) On Tue, Jan 31, 2017 at 10:24 AM, Pavel Krivanek 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 G

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

2017-01-31 Thread Gabriel Cotelli
Still happens with 60367 image. On Tue, Jan 31, 2017 at 10:24 AM, Pavel Krivanek 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 :

[Pharo-dev] [pharo-project/pharo-core]

2017-01-31 Thread GitHub
Branch: refs/tags/60367 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] c14c16: 60367

2017-01-31 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c14c1611ee92e5bdac7f8adad3a1b1ab49f70386 https://github.com/pharo-project/pharo-core/commit/c14c1611ee92e5bdac7f8adad3a1b1ab49f70386 Author: Jenkins Build Server Date: 2017-01-31 (Tue, 31 Jan 2017

Re: [Pharo-dev] [Ann] Calypso update: method browser and better UI

2017-01-31 Thread Denis Kudriashov
2017-01-31 1:20 GMT+01:00 Stephan Eggermont : > Nice! > > * white toolbar (according to theme background color) >> > > That doesn't work well. Don't mix styles like this, that is > confusing. > Why? It was by intention. Idea to make toolbar with same color as main table panels. And they have de

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread John Brant
On 01/31/2017 04:02 AM, Pavel Krivanek wrote: Very nice tool. I think it cannot find objects pointed only by a stack of some processes so it may be handy to put them to the global space. Smalltalk globals at: #Stacks put: ((Process allInstances collect: [:p | (p suspendedContext) ifNotNil: #st

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

2017-01-31 Thread Pavel Krivanek
60368 should be ok finally -- Pavel 2017-01-31 14:34 GMT+01:00 Gabriel Cotelli : > Still happens with 60367 image. > > On Tue, Jan 31, 2017 at 10:24 AM, Pavel Krivanek > wrote: > >> Solution on the way: >> >> https://pharo.fogbugz.com/f/cases/19635/DisplayScreen-has-de >> pth-1-on-Linux >> >> e

[Pharo-dev] [pharo-project/pharo-core] 2491ce: 60368

2017-01-31 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 2491ce182323d3cc5204f76de40602fe056bcc8d https://github.com/pharo-project/pharo-core/commit/2491ce182323d3cc5204f76de40602fe056bcc8d Author: Jenkins Build Server Date: 2017-01-31 (Tue, 31 Jan 2017

[Pharo-dev] [pharo-project/pharo-core]

2017-01-31 Thread GitHub
Branch: refs/tags/60368 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Off Topic: Children 3-13yr english program -- 4 weeks free access

2017-01-31 Thread Ben Coman
The kid's school year in Australia starts tomorrow (here in Australia) and another offer arrived. http://readingeggs.com.au/hp/ Mail me privately if you find this useful, so I can track if there is value in continuing to forward these offers. cheers -ben On Tue, Sep 27, 2016 at 4:17 PM, Ben Coman

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

2017-01-31 Thread Gabriel Cotelli
It works Ok. I will close the issue. On Tue, Jan 31, 2017 at 11:35 AM, Pavel Krivanek wrote: > 60368 should be ok finally > > -- Pavel > > 2017-01-31 14:34 GMT+01:00 Gabriel Cotelli : > >> Still happens with 60367 image. >> >> On Tue, Jan 31, 2017 at 10:24 AM, Pavel Krivanek < >> pavel.kriva...@

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread John Brant
On 01/31/2017 06:45 AM, stepharong wrote: thierry we have pointersTo and I imagine that it is not good enough. Do you confirm? #pointersTo appears to be the same as #allReferences and #allOwners in other Smalltalk implementations. These methods are terrible for finding the reason for the mem

[Pharo-dev] Fwd: PharoDays: Possible dates

2017-01-31 Thread Marcus Denker
Hi, I have updated the poll with some dates in May. If you can not come at any date but would be interested in general, please respond with the “can not make it” option. Marcus > Hello, > > First for the board only: We checked with Stef what dates would make sense > The best here is Ap

[Pharo-dev] Added Event for: Pharo Sprint March 3

2017-01-31 Thread denker
Hi, The next Pharo Sprint will be March 3. https://association.pharo.org/event-2451866 Infos can be update (e.g. if people organise other face-to-face meetings). Marcus

[Pharo-dev] Strange behaviour of GTInspector

2017-01-31 Thread Denis Kudriashov
Hi. It seams that click on cell with value of variable in GTInspector activates selection only when mouse moves. It feels like slow selection. It not happens when cell with name is clicked. Try inspect 10@30 and select 10 or 30 to see the problem.

Re: [Pharo-dev] Strange behaviour of GTInspector

2017-01-31 Thread Andrei Chis
Nice bug :) Most likely comes from GLMTreeMorphNodeModel>>#rowMorphForColumn: and GLMEditableLabelBrick. Right now GLMEditableLabelBrick uses an alarm to detect if the user double clicked on the column. Seems that the alarm is not triggered if the mouse does not move. Andrei On Tue, Jan 31, 201

Re: [Pharo-dev] Strange behaviour of GTInspector

2017-01-31 Thread Nicolai Hess
2017-01-31 17:05 GMT+01:00 Denis Kudriashov : > Hi. > > It seams that click on cell with value of variable in GTInspector > activates selection only when mouse moves. It feels like slow selection. > It not happens when cell with name is clicked. > > Try inspect 10@30 and select 10 or 30 to see the

Re: [Pharo-dev] [Ann] Calypso update: method browser and better UI

2017-01-31 Thread Stephan Eggermont
On 31/01/17 14:45, Denis Kudriashov wrote: 2017-01-31 1:20 GMT+01:00 Stephan Eggermont mailto:step...@stack.nl>>: Nice! * white toolbar (according to theme background color) That doesn't work well. Don't mix styles like this, that is confusing. Why? It was by intentio

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread Alexandre Bergel
Hi John, Your tool is truly a gem! Yesterday I spent a couple of hours using #pointersTo to track some Roassal objects. But I was unsuccessful. Your tool help me immediately spot kept references. In particular, the following invocation frees all the Roassal and Athens surface objects: Clipboa

Re: [Pharo-dev] [Ann] Calypso update: method browser and better UI

2017-01-31 Thread Denis Kudriashov
2017-01-31 18:53 GMT+01:00 Stephan Eggermont : > >> * white toolbar (according to theme background color) >> >> >> That doesn't work well. Don't mix styles like this, that is >> confusing. >> >> >> Why? It was by intention. Idea to make toolbar with same color as main >> table pa

Re: [Pharo-dev] Memory leaks

2017-01-31 Thread Torsten Bergmann
I created a config (in original repo and MetaRepoForPharo60) so it should be available In the morning in catalog already. Thanks to John for the nice tool and giving me access to the repo on sthub. Thx T.

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

2017-01-31 Thread Andres Valloud
Martin, On 1/30/17 16:41 , Martin McClure wrote: 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 fa