[Pharo-dev] [Pharo 7.0] Build #168: BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs

There is a new Pharo build available! The status of the build #168 was: SUCCESS. The Pull Request #4084 was integrated: "BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs" Pull request url: https://github.com/pharo-project/pharo/pull/4084 Issue Url: https://phar

[Pharo-dev] [Pharo 7.0] Build #167: BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs

There is a new Pharo build available! The status of the build #167 was: FAILURE. The Pull Request #4084 was integrated: "BackPort Pharo7: Moved becomeForward from Object to ProtoObject where it belongs" Pull request url: https://github.com/pharo-project/pharo/pull/4084 Issue Url: https://phar

Re: [Pharo-dev] problem with pushing to github

+1 MacOS pharo8x64 El mar., 13 ago. 2019 a las 13:31, Myroslava Romaniuk via Pharo-dev (< pharo-dev@lists.pharo.org>) escribió: > 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

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

On Tue, Aug 13, 2019 at 3:25 PM Esteban Lorenzano wrote: > > > No, you are not :) > #asSpAdapter will be removed. > > You are looking for SpMorphPresenter (and/or the method SpPresenter>>newMorph) > In the Spec repository I deprecated #asSpAdapter with a mesage explaining SpMorphPresenter should

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

> On 13 Aug 2019, at 15:19, Cyril Ferlicot wrote: > > On Tue, Aug 13, 2019 at 2:59 PM Norbert Hartl 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 SpMorphic

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

On Tue, Aug 13, 2019 at 2:59 PM Norbert Hartl 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. > W

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

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-proje

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

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

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

> Am 13.08.2019 um 12:28 schrieb Guillermo Polito : > > 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

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

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/4

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

On Tue, Aug 13, 2019 at 1:35 PM Torsten Bergmann 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 a

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

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? Otherw

[Pharo-dev] problem with pushing to github

--- Begin Message --- 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

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

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://

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

Thanks for pushing this Cyril! This will let us move forward with Iceberg too :) > El 13 ago 2019, a las 12:15, Cyril Ferlicot > escribió: > > On Thu, Jun 20, 2019 at 5:29 PM Cyril Ferlicot > wrote: >> >> Hello everyone! >> >> This is an important update abou

[Pharo-dev] [Pharo 8.0] Build #627: 4194-Missing-refactoring-Abstract-instance-variable

There is a new Pharo build available! The status of the build #627 was: SUCCESS. The Pull Request #4199 was integrated: "4194-Missing-refactoring-Abstract-instance-variable" Pull request url: https://github.com/pharo-project/pharo/pull/4199 Issue Url: https://github.com/pharo-project/pharo/is

Re: [Pharo-dev] Information on Spec development

On Thu, Jun 20, 2019 at 5:29 PM Cyril Ferlicot 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 a

[Pharo-dev] [Pharo 8.0] Build #626: 4298-Calypso-does-not-show-empty-protocols

There is a new Pharo build available! The status of the build #626 was: SUCCESS. The Pull Request #4299 was integrated: "4298-Calypso-does-not-show-empty-protocols" Pull request url: https://github.com/pharo-project/pharo/pull/4299 Issue Url: https://github.com/pharo-project/pharo/issues/4298

[Pharo-dev] [Pharo 8.0] Build #625: Update-manually-resolved-dependencies

There is a new Pharo build available! The status of the build #625 was: FAILURE. The Pull Request #4285 was integrated: "Update-manually-resolved-dependencies" Pull request url: https://github.com/pharo-project/pharo/pull/4285 Issue Url: https://github.com/pharo-project/pharo/issues/Update Bui

Re: [Pharo-dev] Impossible to create new protocol?

On Tue, Aug 13, 2019 at 9:18 AM ducasse wrote: > > Tx pavel. > I ask cyril to fix it :) > https://github.com/pharo-project/pharo/pull/4299 > > -- Cyril Ferlicot https://ferlicot.fr

[Pharo-dev] [Pharo 8.0] Build #624: Update order of method list (RBPushDownPreview and RBPushUpPreview )

There is a new Pharo build available! The status of the build #624 was: FAILURE. The Pull Request #4296 was integrated: "Update order of method list (RBPushDownPreview and RBPushUpPreview )" Pull request url: https://github.com/pharo-project/pharo/pull/4296 Issue Url: https://github.com/phar

Re: [Pharo-dev] Impossible to create new protocol?

Tx pavel. I ask cyril to fix it :) > On 13 Aug 2019, at 09:09, Pavel Krivanek wrote: > > yes, the tagsForAllMethods method now hides protocols without methods: >allProtocols select: [ :each | each methods anySatisfy: ... > > út 13. 8. 2019 v 9:05 odesílatel Pavel Krivanek

Re: [Pharo-dev] Impossible to create new protocol?

yes, the tagsForAllMethods method now hides protocols without methods: allProtocols select: [ :each | each methods anySatisfy: ... út 13. 8. 2019 v 9:05 odesílatel Pavel Krivanek napsal: > introduced in build.613. This is probably the source of this issue: > https://github.com/pharo-project/p

[Pharo-dev] [Pharo 8.0] Build #623: Do-not-flush-all-caches-when-a-class-is-removed

There is a new Pharo build available! The status of the build #623 was: FAILURE. The Pull Request #4205 was integrated: "Do-not-flush-all-caches-when-a-class-is-removed" Pull request url: https://github.com/pharo-project/pharo/pull/4205 Issue Url: https://github.com/pharo-project/pharo/issues

Re: [Pharo-dev] Impossible to create new protocol?

introduced in build.613. This is probably the source of this issue: https://github.com/pharo-project/pharo/commit/a0706a080383be50fde8aa90d1709062919d3794 út 13. 8. 2019 v 8:53 odesílatel Pavel Krivanek napsal: > on three days old image (build.610) it worked > > út 13. 8. 2019 v 8:50 odesílatel