August 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #630: 4302-Code-completion-fix-extended-completion-for-NECController

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

There is a new Pharo build available! The status of the build #630 was: SUCCESS. The Pull Request #4303 was integrated: "4302-Code-completion-fix-extended-completion-for-NECController" Pull request url: https://github.com/pharo-project/pharo/pull/4303 Issue Url: https://github.com/pharo-project/pharo/issues/4302 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Cyril Ferlicot

On Tue, Aug 13, 2019 at 2:59 PM Norbert Hartl <norbert(a)hartl.name> wrote: > > > Ah yes, I just wrote on discord. I did a tool in spec2 which I cannot use in the newest pharo. The #asSpecAdapter uses still MorphicGenericAdapter instead of SpMorphicGenericAdapter. Iceberg needs the former, my tool the latter. What is the strategy for that. For now I did a #asSpec2Adapter in my image that return the SpMorphic.. class. > Hi, The extensions in Spec2 are renamed to not conflict with Spec 1. You are looking for #asSpAdapter ;) > Norbert > > -- Cyril Ferlicot https://ferlicot.fr

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Torsten Bergmann

Cyril wrote > Until now, the T is before the prefix. (For example TIceXXX for > Iceberg). So I followed what was already done. But then IMHO Iceberg is wrong too and do not correctly and consistently use their own prefix in front of classes/traits. See other samples like traits in which are also there already: Epicea -> EpTEventVisitor Fuel -> FLTGlobalClassOrTraitSerializationTest Glamour -> GLMTBlockTags Moose Algos -> MalTEdgeNode ... and where "prefix" is first as it should be. There are several reasons why "prefix" should be first: 1. As the name says: it is a prefix - so it would be obvious to have it in front of the class or trait name. 2. Prefixes are a workaround because we do not have namespaces (yet). Following the "prefix" always first rule we could later have a separation into namespaces more easily later when migrating. 3. If someone uses a prefix starting with a "T" too, like "TPL" for Template library then people get easily confused with class/trait mix of "TTPL" and "TPLT" looking like a typo or thinking all are traits because "T" is the first. Therefore - Prefix should be two (as in Seaside), ideally three letters and ideally in uppercase IMHO we should define a rule to have three uppercase letters at least for the base image. - order should be "prefix" and then class or trait name (where trait names start with "T". Smalltalk provides lots of freedom. But without rules and discipline it easily ends up in inconsistencies, chaos, a mess... Looks like even Pharo engineers miss a code guide these days ... Bye T.

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Norbert Hartl

> Am 13.08.2019 um 12:28 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Thanks for pushing this Cyril! > This will let us move forward with Iceberg too :) Ah yes, I just wrote on discord. I did a tool in spec2 which I cannot use in the newest pharo. The #asSpecAdapter uses still MorphicGenericAdapter instead of SpMorphicGenericAdapter. Iceberg needs the former, my tool the latter. What is the strategy for that. For now I did a #asSpec2Adapter in my image that return the SpMorphic.. class. Norbert > >> El 13 ago 2019, a las 12:15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> escribiÃ³: >> >> On Thu, Jun 20, 2019 at 5:29 PM Cyril Ferlicot <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: >>> >>> Hello everyone! >>> >>> This is an important update about the development of Spec. >>> >>> As you might have heard, we are working on Spec to release a new >>> version in Pharo 8. One goal is to unify all Pharo interfaces behind >>> one GUI framework and a second goal is to allow multiple back-ends >>> (Morphic but also GTK, Bloc, ...). To reach those goals we have been >>> updating the current version of Spec. We see now, however, that >>> updating Spec directly creates troubles with migration. For example, >>> we currently have a lot of deprecation warnings in Iceberg, because we >>> can't update it without breaking Pharo 7 compatibility. >>> >>> After some discussions between the engineers working on Spec, here is >>> our plan to improve the situation: We will copy all classes of Spec >>> and rename them with the "Sp" prefix. (We will also ensure that every >>> class of Spec started with the same prefix for consistency). For >>> extensions methods, we will rename them to have a version different >>> from Spec 1 (The spec from Pharo 7). Once done we will integrate this >>> new version in Pharo 8. From there we will wait some weeks to let >>> users who started to use the updated Spec change their projects to use >>> this new Spec2. Finally, we will revert all changes that happened on >>> Spec 1 and deprecate the packages. We hope this will make things >>> easier for everyone. >>> >>> Have a nice day! >> >> Hi, >> >> The revert of changes of Spec 1 is now done in Pharo 8. >> >> Spec 1 is now in the same state than in Pharo 7 and Spec2 can live next to it. >> All classes of Spec2 start with the Sp or TSp prefix. >> >> Have a nice day. >> >>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr <https://ferlicot.fr/> >> >> >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr <https://ferlicot.fr/>

Aug. 13, 2019

[Pharo 8.0] Build #629: 4280-Code-completion-DNU-inside-literal-array

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

There is a new Pharo build available! The status of the build #629 was: FAILURE. The Pull Request #4301 was integrated: "4280-Code-completion-DNU-inside-literal-array" Pull request url: https://github.com/pharo-project/pharo/pull/4301 Issue Url: https://github.com/pharo-project/pharo/issues/4280 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Cyril Ferlicot

On Tue, Aug 13, 2019 at 1:35 PM Torsten Bergmann <astares(a)gmx.de> wrote: > > Cyril Ferlicot wrote: > >The revert of changes of Spec 1 is now done in Pharo 8. > > Nice - lots of work. Thanks!!! > > > All classes of Spec2 start with the Sp or TSp prefix. > > Maybe I'm wrong but: > > If "Sp" is the prefix for Spec2 and trait names start with "T" we should > used SpT... for traits, no? > Until now, the T is before the prefix. (For example TIceXXX for Iceberg). So I followed what was already done. > Otherwise it would not be a prefix ... > > Thanks > T. > -- Cyril Ferlicot https://ferlicot.fr

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Torsten Bergmann

Cyril Ferlicot wrote: >The revert of changes of Spec 1 is now done in Pharo 8. Nice - lots of work. Thanks!!! > All classes of Spec2 start with the Sp or TSp prefix. Maybe I'm wrong but: If "Sp" is the prefix for Spec2 and trait names start with "T" we should used SpT... for traits, no? Otherwise it would not be a prefix ... Thanks T.

Aug. 13, 2019

problem with pushing to github

by Myroslava Romaniuk

Hi saw there's a lot going on with iceberg and spec today so likely this is related. Just created (20 mins ago) a new image to push a PR to pharo, and usually in a new image you have to fill in your credentials and you had 'accept' and 'ok' buttons (ok - to accept credentials, accept - to push). Now there's no 'accept' button and it doesn't push my changes anymore. Am i doing something wrong or is this a bug? P.S. i'm on windows, latest pharo 8. Best regards, Myroslava

Aug. 13, 2019

[Pharo 8.0] Build #628: Revert-Spec1-changes

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

There is a new Pharo build available! The status of the build #628 was: FAILURE. The Pull Request #4278 was integrated: "Revert-Spec1-changes" Pull request url: https://github.com/pharo-project/pharo/pull/4278 Issue Url: https://github.com/pharo-project/pharo/issues/Revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 13, 2019

Re: [Pharo-dev] [Pharo-users] Information on Spec development

by Guillermo Polito

Thanks for pushing this Cyril! This will let us move forward with Iceberg too :) > El 13 ago 2019, a las 12:15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> escribiÃ³: > > On Thu, Jun 20, 2019 at 5:29 PM Cyril Ferlicot <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: >> >> Hello everyone! >> >> This is an important update about the development of Spec. >> >> As you might have heard, we are working on Spec to release a new >> version in Pharo 8. One goal is to unify all Pharo interfaces behind >> one GUI framework and a second goal is to allow multiple back-ends >> (Morphic but also GTK, Bloc, ...). To reach those goals we have been >> updating the current version of Spec. We see now, however, that >> updating Spec directly creates troubles with migration. For example, >> we currently have a lot of deprecation warnings in Iceberg, because we >> can't update it without breaking Pharo 7 compatibility. >> >> After some discussions between the engineers working on Spec, here is >> our plan to improve the situation: We will copy all classes of Spec >> and rename them with the "Sp" prefix. (We will also ensure that every >> class of Spec started with the same prefix for consistency). For >> extensions methods, we will rename them to have a version different >> from Spec 1 (The spec from Pharo 7). Once done we will integrate this >> new version in Pharo 8. From there we will wait some weeks to let >> users who started to use the updated Spec change their projects to use >> this new Spec2. Finally, we will revert all changes that happened on >> Spec 1 and deprecate the packages. We hope this will make things >> easier for everyone. >> >> Have a nice day! > > Hi, > > The revert of changes of Spec 1 is now done in Pharo 8. > > Spec 1 is now in the same state than in Pharo 7 and Spec2 can live next to it. > All classes of Spec2 start with the Sp or TSp prefix. > > Have a nice day. > >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr <https://ferlicot.fr/> > > > > -- > Cyril Ferlicot > https://ferlicot.fr <https://ferlicot.fr/>

Aug. 13, 2019