Re: [Pharo-dev] Code Completion

2018-01-25 Thread Torsten Bergmann
Hi Myroslava, some infos:   Initially for Squeak there was "eCompletion" written by Ruben Bakker. According to the package "eCompletion is code completion inspired by eclipse", it required MCInstaller, Shout 4 and RoelTyper. http://uncomplex.net/ecompletion/ Back in Squeak "Shout" was used to

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

2018-01-25 Thread monty
See #removeAllFormattingNodes and its comment in the latest version. And instances of SAXHandler and subclasses are meant to be created with #on: (or another "instance creation" message), _not #new_, otherwise they won't be properly initialized. The class comment is clear about this, but I

Re: [Pharo-dev] Iceberg Loading issue

2018-01-25 Thread Vincent BLONDEAU
Hi Max, Yes, I tried that too: pulling the branch outside Pharo, set it to the 21124 branch head, then launch Pharo and run the pull of incoming commits from Pharo. Also, loading one commit at the time works, but you cannot do it for a lot of commits, the list of commits is very slow to

Re: [Pharo-dev] Iceberg Loading issue

2018-01-25 Thread Max Leske
Hi Vincent, Possibly a problem with updating FETCH_HEAD. Does it work when you perform only the pull operation from Pharo (i.e., check out the branch on the command line)? Cheers, Max On 26 January 2018 at 00:43:40, vincent.blond...@lamresearch.com ( vincent.blond...@lamresearch.com) wrote:

[Pharo-dev] Iceberg Loading issue

2018-01-25 Thread Vincent.Blondeau
Hi, I am encountering some problems with Iceberg on the latest version. I want to load the commits I just made on a branch on my Pharo fork, let's say "21124". I set the local repo to the current version of my Pharo image, i.e. the development branch (commit 0dbf86). Thanks to the iceberg

[Pharo-dev] Code Completion

2018-01-25 Thread Myroslava Romaniuk
Hi, I'm Myroslava Some of you might remember how last year I did GSoC and worked on Renraku / Quality Assistant with Yuriy. This year Stephane suggested several projects I could work on, and one of them is improving code completion in Pharo, in particular ecompletion. Could you recommend any

Re: [Pharo-dev] [Ann] Calypso in progress: Spotter menu and settings

2018-01-25 Thread Esteban Lorenzano
> On 25 Jan 2018, at 22:18, Esteban Lorenzano wrote: > > > >> On 25 Jan 2018, at 21:57, Stephane Ducasse wrote: >> >> Hi >> I like the navigation done with Spotter by esteban >> Now can we see the shortcuts? and get the notification when we do

Re: [Pharo-dev] [Ann] Calypso in progress: Spotter menu and settings

2018-01-25 Thread Esteban Lorenzano
> On 25 Jan 2018, at 21:57, Stephane Ducasse wrote: > > Hi > I like the navigation done with Spotter by esteban > Now can we see the shortcuts? and get the notification when we do not > use a shortcut because this is super nice to learn shortcuts. yes, that’s

Re: [Pharo-dev] [Ann] Calypso in progress: Spotter menu and settings

2018-01-25 Thread Stephane Ducasse
Hi I like the navigation done with Spotter by esteban Now can we see the shortcuts? and get the notification when we do not use a shortcut because this is super nice to learn shortcuts. On Thu, Jan 25, 2018 at 1:28 PM, Tudor Girba wrote: > Excellent work! > > Doru > > >> On

[Pharo-dev] 64 bit VM build problems: gl.h not found, or glRenderer conflicts

2018-01-25 Thread Alistair Grant
Hi, I'm attempting to build the 64 bit VM in a docker container on Ubuntu 16.04 installing the required packages using opensmalltalk-vm/.travis_install.sh, however B3DAcceleratorPlugin fails to build because it can't find gl.h. Installing mesa-common-dev (which is the most common answer when

[Pharo-dev] [Pharo 7.0-dev] Build #454: 21128-FastTable-search-should-not-setup-first-selected-item-if-nothing-is-found

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #454 was: SUCCESS. The Pull Request #732 was integrated: "21128-FastTable-search-should-not-setup-first-selected-item-if-nothing-is-found" Pull request url: https://github.com/pharo-project/pharo/pull/732 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #453: 21116 Super tearDown need to be called as last message in tearDown of VSReleaseDevelopmentVersionCommandTest

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #453 was: SUCCESS. The Pull Request #717 was integrated: "21116 Super tearDown need to be called as last message in tearDown of VSReleaseDevelopmentVersionCommandTest" Pull request url:

[Pharo-dev] [Pharo 7.0-dev] Build #452: 20929 Remove unnecessary "self debug:#testSelector" comment from test methods - PASS 1

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #452 was: SUCCESS. The Pull Request #649 was integrated: "20929 Remove unnecessary "self debug:#testSelector" comment from test methods - PASS 1" Pull request url: https://github.com/pharo-project/pharo/pull/649 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #451: 21059-Make-icon-list-searchable

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #451 was: SUCCESS. The Pull Request #730 was integrated: "21059-Make-icon-list-searchable" Pull request url: https://github.com/pharo-project/pharo/pull/730 Issue Url: https://pharo.fogbugz.com/f/cases/21059 Build Url:

Re: [Pharo-dev] [Ann] Calypso in progress: Spotter menu and settings

2018-01-25 Thread Tudor Girba
Excellent work! Doru > On Jan 25, 2018, at 1:25 PM, Denis Kudriashov wrote: > > Hi, > > I just released new version of Calypso 0.8.11 which includes several fixes > and new features. > > The most exiting feature is Spotter menu from Esteban >

[Pharo-dev] [Pharo 7.0-dev] Build #450: 21034 ep monitor classreset should not create a new instance if current is already empty

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #450 was: SUCCESS. The Pull Request #698 was integrated: "21034 ep monitor classreset should not create a new instance if current is already empty" Pull request url: https://github.com/pharo-project/pharo/pull/698 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #449: 21065 Super setUp need to be called in HiNodesAndLinksIteratorWithOneLinkModelTest

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #449 was: SUCCESS. The Pull Request #712 was integrated: "21065 Super setUp need to be called in HiNodesAndLinksIteratorWithOneLinkModelTest" Pull request url: https://github.com/pharo-project/pharo/pull/712 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #448: 21106 Super tearDown need to be called as last message in tearDown of PharoTutorial tests

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #448 was: SUCCESS. The Pull Request #725 was integrated: "21106 Super tearDown need to be called as last message in tearDown of PharoTutorial tests" Pull request url: https://github.com/pharo-project/pharo/pull/725 Issue

[Pharo-dev] [ANN] Pharo Consortium New Gold Member: KnowRoaming

2018-01-25 Thread Marcus Denker
The Pharo Consortium is very happy to announce that KnowRoaming has joined the Consortium as a Gold Member. About - KnowRoaming: https://www.knowroaming.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the

[Pharo-dev] [Pharo 7.0-dev] Build #447: 21101 Super tearDown need to be called as last message in tearDown of OpalCompiler tests

2018-01-25 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #447 was: SUCCESS. The Pull Request #729 was integrated: "21101 Super tearDown need to be called as last message in tearDown of OpalCompiler tests" Pull request url: https://github.com/pharo-project/pharo/pull/729 Issue Url:

Re: [Pharo-dev] Moving from mc to tonel?

2018-01-25 Thread Peter Uhnák
Hi Martin, there are some pull requests regarding encoding, I finally have a bit more time so I'll look into that in the coming days. Peter On Thu, Jan 25, 2018 at 3:57 AM, Martin Dias wrote: > Hi, any news or experiences on the migration tools? I'd try again on next >