Re: [Pharo-dev] Pharo-dev Digest, Vol 46, Issue 17

Hi Lukas, When replying to a digest, please delete everything unrelated to the post you are replying to. Its easy to miss doing this in some mail clients that by default hide the included text. Check this link. Its hard to identify what was your response...

Re: [Pharo-dev] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

Thanks a lot Brad ! It'd be great if you could kindly urge others to vote for me as well. Looking forward to the valuable support from all Best Jigyasa Grover -- View this message in context:

Re: [Pharo-dev] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

I voted Brad Selfridge 913-269-2385 > On Feb 17, 2017, at 12:57 PM, Jigyasa Grover > wrote: > > Dear All > > It feels delighted to be nominated as finalist for *Red Hat International > Women in Open Source Academic Awards 2017* owing to my significant >

[Pharo-dev] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

Dear All It feels delighted to be nominated as finalist for *Red Hat International Women in Open Source Academic Awards 2017* owing to my significant contributions to the open source community spanning various organisations & projects viz FOSSASIA, Pharo/Smalltalk, European Smalltalk Users Group

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

Branch: refs/tags/60400 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 358123: 60400

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

Re: [Pharo-dev] FileTree

Oh really ? My school is Ecole Supérieur Polytechnique (ESP). I want to rewrite the pharoCandle in the FileTree format but i don't know where to start. Jonathan 2017-02-17 16:37 GMT+01:00 Serge Stinckwich : > On Fri, Feb 17, 2017 at 3:06 PM, Jonathan Khalil

Re: [Pharo-dev] FileTree

On Fri, Feb 17, 2017 at 3:06 PM, Jonathan Khalil wrote: > Hi everyone, > > I'm Jonathan, student in master, from Dakar, Sénégal and i will be working > with stephane ducasse's team for my internship. Great Jonathan. Where are you located ? My research team is working in Senegal

[Pharo-dev] Metacello and big Github repositories

Hi, as already mentioned in GT Event Recorder help, current Pharo version does not support ZIP signature that is used for large files. That starts to be Metacello issue as soon as you need to work with some large Git repository because Metacello firstly downloads the repository working copy in

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

On Fri, Feb 17, 2017 at 1:48 PM, Cyril Ferlicot D. wrote: > Le 17/02/2017 à 13:31, Clément Bera a écrit : > > > > > > It may solve part of the problem. > > > > Another problem is that tenure heuristics needs to be changed when > > allocating lots of long-lived objects.

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

Le 17/02/2017 à 13:31, Clément Bera a écrit : > > > It may solve part of the problem. > > Another problem is that tenure heuristics needs to be changed when > allocating lots of long-lived objects. One needs to implement a GCPolicy > object in the image and use it from the application code...

Re: [Pharo-dev] 17240 Spur, when saving an image, it never shrinks

On Fri, Feb 17, 2017 at 12:05 PM, Cyril Ferlicot D. < cyril.ferli...@gmail.com> wrote: > Le 17/02/2017 à 07:17, Clément Bera a écrit : > > The full GC is indeed much faster as the previous compaction algorithm > > was very slow. But unless you were executing memory intensive code in > > very

[Pharo-dev] [Issue Tracker][Pharo5] Please check issues tagged Pharo5

Hello, We have still 9 issues that are tagged with the Pharo5 Milestone. Please everyone who either submitted the issue or was involved in the discussions: - Is this issue still relevant? - Is it maybe fixed in Pharo6? - Is is important enough to require a backport to

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

Branch: refs/tags/60399 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [Pharo6][Issue Tracker] Please check older issues

Current Status: Open Issues:625 For Pharo6: 125 > On 16 Feb 2017, at 11:02, Marcus Denker wrote: > > Hi, > > The issue tracker is at 632 open issues. > > https://pharo.fogbugz.com/f/filters/57/All-newest-first > > Please check

Re: [Pharo-dev] Pharo-dev Digest, Vol 46, Issue 17

"Send Pharo-dev mailing list submissions to pharo-dev@lists.pharo.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.org or, via email, send a message with subject or body 'help' to pharo-dev-requ...@lists.pharo.org

Re: [Pharo-dev] Code Completion in Pharo

Beside regular Smalltalk completion I personally would like to see also support for custom templates in the code completion (similar to what Eclipse provides, see https://www.youtube.com/watch?v=zqm4CB1BX6Y).

[Pharo-dev] [pharo-project/pharo-core] e4d05f: 60398

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

[Pharo-dev] [pharo-project/pharo-core] f71d05: 60397

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

Re: [Pharo-dev] 2 seconds default time limit for tests

I moved issue to Pharo 7 2017-02-16 13:33 GMT+01:00 Denis Kudriashov : > Hi. > > In Pharo 6 we introduced time limit for tests. Currently it is set to 1 > minute by default. And concrete test cases or single tests can redefine it > with suitable value. There is also setting

Re: [Pharo-dev] Code Completion in Pharo

Hi lukas Nice to see you here. I would start to look at the code and clean what is strange. - Did you test the difference between the two algorithms? - Did you play with NECPreferences? - I would like to see what is the difference between the NOC class and the NECclass - I would like to

Re: [Pharo-dev] debugger evaluator tab for temporary variables

2017-02-17 10:36 GMT+01:00 Ben Coman : > Seems like you misread my idea (3am syndrome again?) > You wouldn't need to select "self". > The idea is in the first (left hand) pane you would flip from the > [Variables] to an [Evaluator] tab > this hiding all variables but having

Re: [Pharo-dev] debugger evaluator tab for temporary variables

On Fri, Feb 17, 2017 at 4:55 PM, Denis Kudriashov wrote: > > 2017-02-17 3:01 GMT+01:00 Ben Coman : >> >> A minor irritation with the debugger is that the [Evaluator] tab is >> only for the object of the selected instance variable. > > > Evaluator

Re: [Pharo-dev] debugger highlighting objects up the stack

2017-02-17 2:41 GMT+01:00 Ben Coman : > Just a brief throw away idea to share before it floats off on its own, > it could be useful from the debugger being able to select a variable, > and for the object it contains, ask the debugger to highlight up the stack > where that

Re: [Pharo-dev] debugger evaluator tab for temporary variables

2017-02-17 9:55 GMT+01:00 Denis Kudriashov : > Do you won't Ah, I still sleep. Do you want? :)

Re: [Pharo-dev] debugger evaluator tab for temporary variables

2017-02-17 3:01 GMT+01:00 Ben Coman : > A minor irritation with the debugger is that the [Evaluator] tab is > only for the object of the selected instance variable. > Evaluator appears only when you select something in table. It could be any object which can have inst vars

Re: [Pharo-dev] debugger evaluator tab for temporary variables

Good point. Please open an issue for this and add Andrei and I to it. Cheers, Doru > On Feb 17, 2017, at 3:01 AM, Ben Coman wrote: > > A minor irritation with the debugger is that the [Evaluator] tab is > only for the object of the selected instance variable. > > IIUC,