Re: [Pharo-dev] [Moose-dev] [ann] gtmondrian

Super super cool. > On 9 Dec 2017, at 08:14, Tudor Girba wrote: > > Hi, > > We are happy to announce GT Mondrian, a graph visualization engine built on > top of Bloc. > > It is similar to the original Mondrian and the Mondrian from Roassal, but it > is different in

[Pharo-dev] [ann] gtmondrian

Hi, We are happy to announce GT Mondrian, a graph visualization engine built on top of Bloc. It is similar to the original Mondrian and the Mondrian from Roassal, but it is different in that it is built directly out of Bloc elements. This is interesting because it allows us to combine typical

Re: [Pharo-dev] Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager

Ok I see quite sophisticated. I did not have the time to check. Did you explain this in the class comments? Tx thomas. On Fri, Dec 8, 2017 at 10:57 AM, Thomas Dupriez wrote: > HaltManager proposes the deactivation by metalink even on self halt because > you

Re: [Pharo-dev] Text Indentation in Pharo editor

> Am 08.12.2017 um 21:24 schrieb Tudor Girba : > > Hi Stef, > > Do you get the debugger issue even in a plain Pharo image? > I do Norbert > Doru > > >> On Dec 8, 2017, at 3:40 PM, Stephane Ducasse wrote: >> >> I would love to have Ctrl E and

Re: [Pharo-dev] Text Indentation in Pharo editor

Hi Stef, Do you get the debugger issue even in a plain Pharo image? Doru > On Dec 8, 2017, at 3:40 PM, Stephane Ducasse wrote: > > I would love to have Ctrl E and Ctrl A. > And yes we should not be different for the sake of it. > For the moment the reason is simple:

[Pharo-dev] [Pharo 7.0-dev] Build #373: 20713 Cleanup RBRefactoringChangeTests

There is a new Pharo build available! The status of the build #373 was: SUCCESS. The Pull Request #594 was integrated: "20713 Cleanup RBRefactoringChangeTests" Pull request url: https://github.com/pharo-project/pharo/pull/594 Issue Url: https://pharo.fogbugz.com/f/cases/20713 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #372: 20842-create-clear-image-entry-point-

There is a new Pharo build available! The status of the build #372 was: SUCCESS. The Pull Request #592 was integrated: "20842-create-clear-image-entry-point-" Pull request url: https://github.com/pharo-project/pharo/pull/592 Issue Url: https://pharo.fogbugz.com/f/cases/20842 Build Url:

Re: [Pharo-dev] How to get rid of empty XML nodes?

> Am 08.12.2017 um 14:21 schrieb Stephane Ducasse : > > Hi monty > > >> On Fri, Dec 8, 2017 at 9:03 AM, monty wrote: >> By "empty XML nodes," do you mean whitespace-only string nodes? > > Yes > >> Those are included because all in-element

Re: [Pharo-dev] Text Indentation in Pharo editor

I would love to have Ctrl E and Ctrl A. And yes we should not be different for the sake of it. For the moment the reason is simple: we are full of work and even more. FYI: I'm starting at regular crash of the VM and regular superbad behavior of the debugger (like hundred of debuggers, like

Re: [Pharo-dev] How to get rid of empty XML nodes?

Hi monty On Fri, Dec 8, 2017 at 9:03 AM, monty wrote: > By "empty XML nodes," do you mean whitespace-only string nodes? Yes > Those are included because all in-element whitespace is assumed significant > by the spec: https://www.w3.org/TR/xml/#sec-white-space I know.

[Pharo-dev] [Pharo 7.0-dev] Build #371: 20734-Nested-Structures-using-Platform-longs-fails

There is a new Pharo build available! The status of the build #371 was: SUCCESS. The Pull Request #519 was integrated: "20734-Nested-Structures-using-Platform-longs-fails" Pull request url: https://github.com/pharo-project/pharo/pull/519 Issue Url:

[Pharo-dev] Report period: 24 November 2017 to 8 December 2017

Report period: 24 November 2017 to 8 December 2017 * 20734-Nested-Structures-using-Platform-longs-fails >> Adding implementation of platform dependent longs in FFIExternalStructureReferenceHandle. >> >> Fixes

[Pharo-dev] [Pharo 7.0-dev] Build #370: 20847 Super setUp need to be called in various test classes (Part 2)

There is a new Pharo build available! The status of the build #370 was: SUCCESS. The Pull Request #593 was integrated: "20847 Super setUp need to be called in various test classes (Part 2)" Pull request url: https://github.com/pharo-project/pharo/pull/593 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #369: 20840 Super setUp need to be called in various test classes (Part 1)

There is a new Pharo build available! The status of the build #369 was: SUCCESS. The Pull Request #590 was integrated: "20840 Super setUp need to be called in various test classes (Part 1)" Pull request url: https://github.com/pharo-project/pharo/pull/590 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #368: 20838 Super setUp need to be called in System-SessionManager package tests

There is a new Pharo build available! The status of the build #368 was: SUCCESS. The Pull Request #588 was integrated: "20838 Super setUp need to be called in System-SessionManager package tests" Pull request url: https://github.com/pharo-project/pharo/pull/588 Issue Url:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #367: 20839 Super setUp need to be called in NECompletion-Tests

A note: It seems we do not get mails like this for all PR merges. E.g. yesterday I merged around 12 pull requests, but we got only 5 messages to the list. This seems to happen when merges happen very quickly… to be analysed. Marcus > On 8 Dec 2017, at 10:42,

Re: [Pharo-dev] Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager

HaltManager proposes the deactivation by metalink even on self halt because you may want to deactivate the halt without changing the source code and completely recompiling the method. Thomas Le 07/12/2017 à 21:00, Stephane Ducasse a écrit : Thanks Thomas and you put screenshots so this is

Re: [Pharo-dev] Text Indentation in Pharo editor

On 8 December 2017 at 11:37, Sean P. DeNigris wrote: > Torsten Bergmann wrote > > so we do it with different shortcuts than regular editors > > I wonder if it makes sense to allow the standard shortcut. The current one > is a bit like playing twister ;) > We should be

[Pharo-dev] [Pharo 7.0-dev] Build #367: 20839 Super setUp need to be called in NECompletion-Tests

There is a new Pharo build available! The status of the build #367 was: SUCCESS. The Pull Request #589 was integrated: "20839 Super setUp need to be called in NECompletion-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/589 Issue Url:

Re: [Pharo-dev] How to get rid of empty XML nodes?

By "empty XML nodes," do you mean whitespace-only string nodes? Those are included because all in-element whitespace is assumed significant by the spec: https://www.w3.org/TR/xml/#sec-white-space The exception is if the element is declared in the DTD as only having element children ("element