- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 14:23, Aliaksei Syrel wrote: > Something changed in Pharo 7 between 06.10.2017 - 17.10.2017 because > GToolkit it loads flawlessly in Pharo from 6th of October. Looks most likely to be build 197: There is a new Pharo build available! The status of the build #197 was: SUCCESS. The Pull Request #362 was integrated: "20540-move-metacelloPlatformAttributes-to-Pharo7" Pull request url: https://github.com/pharo-project/pharo/pull/362 Issue Url: https://pharo.fogbugz.com/f/cases/20540 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by Aliaksei Syrel

Hi In last two commits I tried to fix Baseline of Documenter but failed because of Pillar. See screenshot. [image: Inline images 1] For a very long time we depended on #development of Pillar, but suddenly it gone away. See screenshot. [image: Inline images 2] I will change #pier back to #development. Something changed in Pharo 7 between 06.10.2017 - 17.10.2017 because GToolkit it loads flawlessly in Pharo from 6th of October.

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 13:32, Alistair Grant wrote: > That loads successfully for me, thanks, but Pillar & Magritte are > broken in new and interesting ways. It will be a while before I can > look in to it properly. The #pier and Magritte 3.5.0 references are not helpful there, and it looks like there are more pharo7 tags missing Stephan

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by Alistair Grant

Hi Stephan, On 19 October 2017 at 12:45, stephan <stephan(a)stack.nl> wrote: > On 19-10-17 12:21, stephan wrote: >> >> On 19-10-17 12:05, Alistair Grant wrote: >> >>> I've hit exactly the same issue. >>> >>> It looks like ConfigurationOfGrease is missing #pharo7.x version >>> identifiers throughout it. > > > Name: ConfigurationOfGrease-StephanEggermont.347 > Author: StephanEggermont > Time: 19 October 2017, 12:42:22.848053 pm > UUID: baaf8ebf-4518-0d00-ab4f-cad309d94048 > Ancestors: ConfigurationOfGrease-JohanBrichau.346 > > Added Pharo 7 versions of release1/1.3 That loads successfully for me, thanks, but Pillar & Magritte are broken in new and interesting ways. It will be a while before I can look in to it properly. Thanks, Alistair

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 12:21, stephan wrote: > On 19-10-17 12:05, Alistair Grant wrote: > >> I've hit exactly the same issue. >> >> It looks like ConfigurationOfGrease is missing #pharo7.x version >> identifiers throughout it. Name: ConfigurationOfGrease-StephanEggermont.347 Author: StephanEggermont Time: 19 October 2017, 12:42:22.848053 pm UUID: baaf8ebf-4518-0d00-ab4f-cad309d94048 Ancestors: ConfigurationOfGrease-JohanBrichau.346 Added Pharo 7 versions of release1/1.3

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by stephan

On 19-10-17 12:05, Alistair Grant wrote: > I've hit exactly the same issue. > > It looks like ConfigurationOfGrease is missing #pharo7.x version > identifiers throughout it. BaselineOfGToolkitDocumenter refers to ConfigurationOfPillar #pier version. That is very, very old. Pillar broke compatibility years ago ConfigurationOfPillar does not look good at all: - no pharo 7 in stable, and a strange common version. - in the stable version 6.0.6 all dependencies are to numbered versions instead of symbolic ones. ConfigurationOfCocoon has the same problem, pointing to Magritte3 3.5.0 I could load by defining #'pharo7' versions in #'release1' and #'release1.3' Stephan

Oct. 19, 2017

Re: [Pharo-dev] Loading GToolkit is broken in latest 7

by Alistair Grant

Hi Steph, On 19 October 2017 at 11:56, stephan <stephan(a)stack.nl> wrote: > Iceberg enableMetacelloIntegration: true. > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > > tries to resolve ConfigurationOfGrease to #release1 > > Stephan I've hit exactly the same issue. It looks like ConfigurationOfGrease is missing #pharo7.x version identifiers throughout it. I took a guess at the required changes (in the attached file), but have hit several other problems with Pillar that I'm still working through, e.g. at the start of October, loading Pillar with: spec project: 'Pillar' with: [ spec className: #ConfigurationOfPillar; versionString: #'development'; repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]. loaded Grease-Pharo30-Core. But now it doesn't. Cheers, Alistair

Oct. 19, 2017

Loading GToolkit is broken in latest 7

by stephan

Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. tries to resolve ConfigurationOfGrease to #release1 Stephan

Oct. 19, 2017

[Pharo 7.0-dev] Build #210: 19533-Configuration-command-line-handler-should-not-save-and-quit-by-himself

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #210 was: SUCCESS. The Pull Request #376 was integrated: "19533-Configuration-command-line-handler-should-not-save-and-quit-by-himself" Pull request url: https://github.com/pharo-project/pharo/pull/376 Issue Url: https://pharo.fogbugz.com/f/cases/19533 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 19, 2017

Management of ctrl + shift in windows

by Cyril Ferlicot D.

Hi, I have a weird problem on Windows and shortcuts. For the context I use a keyboard which is not of the AZERTY/QWERTY layout but BÃPO.[1] I have a problem with the fact that some `ctrl + shift + ?` shortucts does not works. But some works. For example in Nautilus I cannot do a format (`ctrl + shift + f`) or a debug it (`ctrl + shift + d`). In the other hand, in Spotter I can drill down a category with `ctrl + shift + ->`. If I use the AZERTY layout I do not have this problem. I tried to use the KeyPrinterMorph and to do the format shortcut. Here is the result: BÃPO: - Key SHIFT_L code: (65505) - Key CONTROL_L code: (65507) - Key F code: (70) AZERTY: - Key SHIFT_L code: (65505) - Key CONTROL_L code: (65507) - Key F code: (70) So this is the same key events. I don't have the knowledge and the time to investigate this. Maybe someone have some idea of where can be the problem? https://pharo.fogbugz.com/f/cases/20555/Bug-in-the-ctrl-shift-shortcuts-in-… [1] http://typematrix.com/bepo/view_closeup.php?l=&t=keyb&id=0 -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 19, 2017