[Pharo-dev] [Pharo 7.0-dev] Build #726: 21646 AbstractFileReference should use "utilities" protocol name

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #726 was: SUCCESS.

The Pull Request #1149 was integrated: "21646  AbstractFileReference should use 
"utilities" protocol name"
Pull request url: https://github.com/pharo-project/pharo/pull/1149

Issue Url: https://pharo.fogbugz.com/f/cases/21646
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/726/

[Pharo-dev] [Pharo 7.0-dev] Build #727: 21642-Add-Deprecated-to-the-old-Ring-package-names

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #727 was: SUCCESS.

The Pull Request #1148 was integrated: 
"21642-Add-Deprecated-to-the-old-Ring-package-names"
Pull request url: https://github.com/pharo-project/pharo/pull/1148

Issue Url: https://pharo.fogbugz.com/f/cases/21642
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/727/

[Pharo-dev] [ANN] Slides for a Lecture: MetaLinks

[Marcus Denker]

Hi,

I did last week a short lecture at VUB Brussels. Topic: MetaLinks.

Slideshare: https://www.slideshare.net/MarcusDenker/lecture-metalinks
PDF: http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf 



Marcus

[Pharo-dev] [Pharo 7.0-dev] Build #728: 21577 Cannot read from /dev/urandom

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #728 was: SUCCESS.

The Pull Request #1093 was integrated: "21577 Cannot read from /dev/urandom"
Pull request url: https://github.com/pharo-project/pharo/pull/1093

Issue Url: https://pharo.fogbugz.com/f/cases/Issue21577
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/728/

[Pharo-dev] [Pharo 7.0-dev] Build #729: 21650-rename-the-class-Key-to-something-less-generic

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #729 was: SUCCESS.

The Pull Request #1153 was integrated: 
"21650-rename-the-class-Key-to-something-less-generic"
Pull request url: https://github.com/pharo-project/pharo/pull/1153

Issue Url: https://pharo.fogbugz.com/f/cases/21650
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/729/

Re: [Pharo-dev] [Pharo-users] [ANN] Slides for a Lecture: MetaLinks

[Alistair Grant]

Great introduction.  I'd seen MetaLinks mentioned in emails, but
basically ignored them as I didn't know what they were.

Thanks, Marcus!

Cheers,
Alistair


On 27 March 2018 at 10:17, Marcus Denker  wrote:
> Hi,
>
> I did last week a short lecture at VUB Brussels. Topic: MetaLinks.
>
> Slideshare: https://www.slideshare.net/MarcusDenker/lecture-metalinks
> PDF: http://marcusdenker.de/talks/18LectureMetaLinks/MetaLinks.pdf
>
>
> Marcus

[Pharo-dev] [Pharo 7.0-dev] Build #730: 20898-MultiByteFileStream-upToAll-does-not-work-correctly-with-UTF-8

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #730 was: SUCCESS.

The Pull Request #632 was integrated: 
"20898-MultiByteFileStream-upToAll-does-not-work-correctly-with-UTF-8"
Pull request url: https://github.com/pharo-project/pharo/pull/632

Issue Url: https://pharo.fogbugz.com/f/cases/20898
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/730/

[Pharo-dev] [Pharo 7.0-dev] Build #731: 21639-Package-RPackage-Traits-seems-to-be-empty

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #731 was: SUCCESS.

The Pull Request #1145 was integrated: 
"21639-Package-RPackage-Traits-seems-to-be-empty"
Pull request url: https://github.com/pharo-project/pharo/pull/1145

Issue Url: https://pharo.fogbugz.com/f/cases/21639
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/731/

[Pharo-dev] [Pharo 7.0-dev] Build #732: 21462-Open-a-FileStream-based-on-fd-or-FILE

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #732 was: SUCCESS.

The Pull Request #1014 was integrated: 
"21462-Open-a-FileStream-based-on-fd-or-FILE"
Pull request url: https://github.com/pharo-project/pharo/pull/1014

Issue Url: https://pharo.fogbugz.com/f/cases/21462
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/732/

Re: [Pharo-dev] [Pharo 7.0-dev] Build #732: 21462-Open-a-FileStream-based-on-fd-or-FILE

[Alistair Grant]

On 27 March 2018 at 14:41,   wrote:
> There is a new Pharo build available!
>
> The status of the build #732 was: SUCCESS.
>
> The Pull Request #1014 was integrated: 
> "21462-Open-a-FileStream-based-on-fd-or-FILE"
> Pull request url: https://github.com/pharo-project/pharo/pull/1014
>
> Issue Url: https://pharo.fogbugz.com/f/cases/21462
> Build Url: 
> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/732/

Note that this needs a VM dated 8 Mar 2018 or later, i.e. the next stable VM.

If you're on linux and want to try this:

http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201803160215-43a2f5c.zip
http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-201803160215-43a2f5c.zip

should work.

Thanks for integrating, Marcus!

Cheers,
Alistair

[Pharo-dev] [Pharo 7.0-dev] Build #733: 21649-Integer--printOn-has-a-superfluous-return-

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #733 was: SUCCESS.

The Pull Request #1155 was integrated: 
"21649-Integer--printOn-has-a-superfluous-return-"
Pull request url: https://github.com/pharo-project/pharo/pull/1155

Issue Url: https://pharo.fogbugz.com/f/cases/21649
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/733/

Re: [Pharo-dev] [ANN] Slides for a Lecture: MetaLinks

[Sean P. DeNigris]

Marcus Denker-4 wrote
> Slideshare: https://www.slideshare.net/MarcusDenker/lecture-metalinks

Sooo cool! This is one of those things that I know is a game changer but
I've yet to work into my tactics e.g. debugging. Embarrassingly, I'm still
doing stupid logging most of the time :/



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] [Pharo 7.0-dev] Build #734: 21633-use-ensure-for-meta-level

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #734 was: FAILURE.

The Pull Request #1157 was integrated: "21633-use-ensure-for-meta-level"
Pull request url: https://github.com/pharo-project/pharo/pull/1157

Issue Url: https://pharo.fogbugz.com/f/cases/21633
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/734/

[Pharo-dev] [Pharo 7.0-dev] Build #735: 21654-MetaLink-should-have-announceChange-for-all-SystemAnnouncer-related-change-announcing

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #735 was: SUCCESS.

The Pull Request #1158 was integrated: 
"21654-MetaLink-should-have-announceChange-for-all-SystemAnnouncer-related-change-announcing"
Pull request url: https://github.com/pharo-project/pharo/pull/1158

Issue Url: https://pharo.fogbugz.com/f/cases/21654
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/735/

Re: [Pharo-dev] Bloc: Simulating "Worlds"

[Sean P. DeNigris]

Sean P. DeNigris wrote
> Sean P. DeNigris wrote
>> Looks like it's time for my annual Bloc Dream check in ha ha! 
> [crickets chirping]…
> One year too many?

I committed a Bloc fix. Does that earn me a reply? ;-)



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Bloc: Simulating "Worlds"

[Aliaksei Syrel]

"a reply"

^^ here you go, Sean :)

P.S. I will reply here with an example when it is done. We need to simulate
bloc spaces exactly as you described to record gifs and videos without
frame drop at 60fps.

Cheers,
Alex

On 27 March 2018 at 19:36, Sean P. DeNigris  wrote:

> Sean P. DeNigris wrote
> > Sean P. DeNigris wrote
> >> Looks like it's time for my annual Bloc Dream check in ha ha!
> > [crickets chirping]…
> > One year too many?
>
> I committed a Bloc fix. Does that earn me a reply? ;-)
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
>
>

[Pharo-dev] Roadmap to Pharo 7 Release

[Sean P. DeNigris]

Does a high level overview exist of what still has to be done? Do we expect
any more potentially-disruptive changes or are we in/near the stabilization
phase?



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] [Pharo 7.0-dev] Build #736: 21656-Simplify-ClassDescriptioncomment-more

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #736 was: SUCCESS.

The Pull Request #1159 was integrated: 
"21656-Simplify-ClassDescriptioncomment-more"
Pull request url: https://github.com/pharo-project/pharo/pull/1159

Issue Url: https://pharo.fogbugz.com/f/cases/21656
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/736/

Re: [Pharo-dev] Roadmap to Pharo 7 Release

[Esteban Lorenzano]

still we have to release iceberg 0.7 then we’ll see how we are there.
and still we have to make a 64bit windows VM+image that works for us.
and we still need to fix that annoying debug blocking all bug
and of course, we have some leaks we still need to solve.

I think all the other issues are covered (I need to check and I can’t right 
now… but I have that feeling).

cheers,
Esteban 



> On 27 Mar 2018, at 19:47, Sean P. DeNigris  wrote:
> 
> Does a high level overview exist of what still has to be done? Do we expect
> any more potentially-disruptive changes or are we in/near the stabilization
> phase?
> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
> 

Re: [Pharo-dev] Roadmap to Pharo 7 Release

[Peter Uhnák]

So I take it Cargo will not be in P7? (Assuming Cargo is still being
developed, which it currently isn't.)

Thanks,
Peter

On Tue, Mar 27, 2018 at 8:11 PM, Esteban Lorenzano 
wrote:

> still we have to release iceberg 0.7 then we’ll see how we are there.
> and still we have to make a 64bit windows VM+image that works for us.
> and we still need to fix that annoying debug blocking all bug
> and of course, we have some leaks we still need to solve.
>
> I think all the other issues are covered (I need to check and I can’t
> right now… but I have that feeling).
>
> cheers,
> Esteban
>
>
>
> > On 27 Mar 2018, at 19:47, Sean P. DeNigris 
> wrote:
> >
> > Does a high level overview exist of what still has to be done? Do we
> expect
> > any more potentially-disruptive changes or are we in/near the
> stabilization
> > phase?
> >
> >
> >
> > -
> > Cheers,
> > Sean
> > --
> > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.
> html
> >
>
>
>

Re: [Pharo-dev] Roadmap to Pharo 7 Release

[Aliaksei Syrel]

Hi,

btw, there is an interesting opened issue on Cargo's github page:
https://github.com/demarey/cargo/issues/32

I wanted to let you know that the Rust programming language ships with a
> package manager that is also called Cargo, which is a trademarked part of
> the project. There definitely seems to be scope for confusion around the
> name. Can we work together to figure something out?


It is opened by Aaron Turon, Mozilla developer.

Any thoughts?

Cheers,
Alex

On 27 March 2018 at 20:29, Peter Uhnák  wrote:

> So I take it Cargo will not be in P7? (Assuming Cargo is still being
> developed, which it currently isn't.)
>
> Thanks,
> Peter
>
> On Tue, Mar 27, 2018 at 8:11 PM, Esteban Lorenzano 
> wrote:
>
>> still we have to release iceberg 0.7 then we’ll see how we are there.
>> and still we have to make a 64bit windows VM+image that works for us.
>> and we still need to fix that annoying debug blocking all bug
>> and of course, we have some leaks we still need to solve.
>>
>> I think all the other issues are covered (I need to check and I can’t
>> right now… but I have that feeling).
>>
>> cheers,
>> Esteban
>>
>>
>>
>> > On 27 Mar 2018, at 19:47, Sean P. DeNigris 
>> wrote:
>> >
>> > Does a high level overview exist of what still has to be done? Do we
>> expect
>> > any more potentially-disruptive changes or are we in/near the
>> stabilization
>> > phase?
>> >
>> >
>> >
>> > -
>> > Cheers,
>> > Sean
>> > --
>> > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.ht
>> ml
>> >
>>
>>
>>
>

[Pharo-dev] Calypso: how to see two different methods (without diff) side by side?

[Stephane Ducasse]

Hi denis

I do not really use a method diff but I would love to be able to see
two methods
side by side.

Stef

Re: [Pharo-dev] Roadmap to Pharo 7 Release

[Stephane Ducasse]

Yes we will rename it: Panier ou Cabas you see the stuff old ladies
are using to go shopping :)
Now we are not in hurry. It should work first.


On Tue, Mar 27, 2018 at 8:37 PM, Aliaksei Syrel  wrote:
> Hi,
>
> btw, there is an interesting opened issue on Cargo's github page:
> https://github.com/demarey/cargo/issues/32
>
>> I wanted to let you know that the Rust programming language ships with a
>> package manager that is also called Cargo, which is a trademarked part of
>> the project. There definitely seems to be scope for confusion around the
>> name. Can we work together to figure something out?
>
>
> It is opened by Aaron Turon, Mozilla developer.
>
> Any thoughts?
>
> Cheers,
> Alex
>
> On 27 March 2018 at 20:29, Peter Uhnák  wrote:
>>
>> So I take it Cargo will not be in P7? (Assuming Cargo is still being
>> developed, which it currently isn't.)
>>
>> Thanks,
>> Peter
>>
>> On Tue, Mar 27, 2018 at 8:11 PM, Esteban Lorenzano 
>> wrote:
>>>
>>> still we have to release iceberg 0.7 then we’ll see how we are there.
>>> and still we have to make a 64bit windows VM+image that works for us.
>>> and we still need to fix that annoying debug blocking all bug
>>> and of course, we have some leaks we still need to solve.
>>>
>>> I think all the other issues are covered (I need to check and I can’t
>>> right now… but I have that feeling).
>>>
>>> cheers,
>>> Esteban
>>>
>>>
>>>
>>> > On 27 Mar 2018, at 19:47, Sean P. DeNigris 
>>> > wrote:
>>> >
>>> > Does a high level overview exist of what still has to be done? Do we
>>> > expect
>>> > any more potentially-disruptive changes or are we in/near the
>>> > stabilization
>>> > phase?
>>> >
>>> >
>>> >
>>> > -
>>> > Cheers,
>>> > Sean
>>> > --
>>> > Sent from:
>>> > http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
>>> >
>>>
>>>
>>
>

Re: [Pharo-dev] Roadmap to Pharo 7 Release

[Stephane Ducasse]

- [easy] I want to have a package with all the deprecatedTransform
from Pharo current and paste versions.
- should check the removal of FTPlugin (tx tx tx pablo)
- newline abstraction because we should stop to have cr all the way?
- Clap command-line (yes damien please push)
- Remove Versionner, Komitter, Nautilus
- Improve calypso

We are working on Spec2. Denis is working on an architecture:
- no more adapter
- no more interpreter
- working with Morphic and Bloc.

So we will see. As soon as it feels ok I would like to rewrite many
tools with it.
And we will need help.

Since Glamour is not really maintained anymore and source of some
leaks and problems, we want to remove any users
except GTTools.

Stef














On Tue, Mar 27, 2018 at 7:47 PM, Sean P. DeNigris  wrote:
> Does a high level overview exist of what still has to be done? Do we expect
> any more potentially-disruptive changes or are we in/near the stabilization
> phase?
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
>

Re: [Pharo-dev] Roadmap to Pharo 7 Release

[Peter Uhnák]

>
> Since Glamour is not really maintained anymore and source of some
> leaks and problems, we want to remove any users
> except GTTools.
>

Can you please provide more info on this? What exactly is going to be
removed?

Thanks,
Peter

Re: [Pharo-dev] Bloc: Simulating "Worlds"

[Sean P. DeNigris]

Aliaksei Syrel wrote
> "a reply"

Ha ha. Thanks, that clears it up nicely. I'm all set ;)


Aliaksei Syrel wrote
> P.S. I will reply here with an example when it is done.

Looking forward to it :)



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] Why calypso inverse the hierarchy?

[Stephane Ducasse]

Hi denis

Calypso asked me where I want to install a method.
And I do not really appreciate that I get the inheritance tree reserved.
To me it will destroy students.
On my own code which is super stupid I had to think twice. I cannot
image students.

Then when working on code that is not ours it is be super difficult to
understand anything.

How can I set that superclass should be higher than subclasses?

Stef

Re: [Pharo-dev] Why calypso inverse the hierarchy?

[Stephane Ducasse]

And by the way I do not understand why calypso asks me where I want to
define a method, when I selected already the class in which I'm
coding.

On Tue, Mar 27, 2018 at 11:11 PM, Stephane Ducasse
 wrote:
> Hi denis
>
> Calypso asked me where I want to install a method.
> And I do not really appreciate that I get the inheritance tree reserved.
> To me it will destroy students.
> On my own code which is super stupid I had to think twice. I cannot
> image students.
>
> Then when working on code that is not ours it is be super difficult to
> understand anything.
>
> How can I set that superclass should be higher than subclasses?
>
> Stef

Re: [Pharo-dev] Calypso: how to see two different methods (without diff) side by side?

[Denis Kudriashov]

Hi Stef.

I found very simple way how to support it. So maybe next release if there
will be time.

Best regards,
Denis

2018-03-27 21:15 GMT+02:00 Stephane Ducasse :

> Hi denis
>
> I do not really use a method diff but I would love to be able to see
> two methods
> side by side.
>
> Stef
>
>

Re: [Pharo-dev] Why calypso inverse the hierarchy?

[Denis Kudriashov]

Hi Stef

2018-03-27 23:11 GMT+02:00 Stephane Ducasse :

> Hi denis
>
> Calypso asked me where I want to install a method.
>

Normally this dialog appears when you edit a method which class is not
selected in the browser.
For example if you enable superclass method visibility and edit one of
inherited methods.
But give me your scenario.


> And I do not really appreciate that I get the inheritance tree reserved.
>

There is setting for this. And I am not against to change default value or
hardcode this part.

Originally it was simple list with selected class at the bottom. Then there
was issue The currently edited class should be the first option when
overriding methods .
Idea that first item should be the most common case which is selected class.
At the end I realized that I can easily show hierarchy which I though is
better than simple list. And I reused existing hierarchy from method
visibility list.

So there are two points for this dialog:
- do we want selected class to be first?
- do we want hierarchical view?

Best regards,
Denis

To me it will destroy students.
> On my own code which is super stupid I had to think twice. I cannot
> image students.
>
> Then when working on code that is not ours it is be super difficult to
> understand anything.
>
> How can I set that superclass should be higher than subclasses?
>
> Stef
>

Re: [Pharo-dev] Slot Questions

[Marcus Denker]

> On 24 Mar 2018, at 21:21, Sean P. DeNigris  wrote:
> 
> Stateful traits inspired me to reread the flexible object layout paper and I
> came up with a few questions about slots:
> - What is the plan for tool support? For example, it seems that to make
> slots discoverable like any other class or message, "References to it"
> should include class definitions, which should be the primary slot client.

Yes, these things need to be done.. I have a very large TODO list for this but 
it is hard to find time

> - Why does IndexedSlot have a #name slot? I thought the index and name were
> "either or" for instVars.

This is the name of the variable. Even though an init-var is accessed by index, 
it still has a name
(e.g. #x in Point).

Marcus