Re: [Pharo-dev] OSProcess for Pharo 7

On Mon, 18 Mar 2019 at 10:20, David T. Lewis wrote: > Hi Mariano, > > On Sun, Mar 17, 2019 at 08:29:59PM -0300, Mariano Martinez Peck wrote: > > > > > > ducasse wrote > > > > this is not because we do not care of Pharo that we will fix it > > > > immediately. > > > > > > Yes of course, just want

Re: [Pharo-dev] OSProcess for Pharo 7

Hi Mariano, On Sun, Mar 17, 2019 at 08:29:59PM -0300, Mariano Martinez Peck wrote: > > > > ducasse wrote > > > this is not because we do not care of Pharo that we will fix it > > > immediately. > > > > Yes of course, just want to keep it on the radar (and maybe Mariano will > > read he he) > > >

Re: [Pharo-dev] OSProcess for Pharo 7

> > > > > ducasse wrote > > this is not because we do not care of Pharo that we will fix it > > immediately. > > Yes of course, just want to keep it on the radar (and maybe Mariano will > read he he) > > I always do :) But honestly, I don't have enough time to carry on that myself. As you could

Re: [Pharo-dev] OSProcess for Pharo 7

> ducasse wrote >> Our main problem is that >> - if more people would review PR >> - send PRs > > Thank you for the reminder of that bottleneck. I will try to do that more > now that we have moved to GH. The old process seemed too cumbersome to be > able to effectively utilize a few

Re: [Pharo-dev] [Moose-dev] Re: Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

On Sun, Mar 17, 2019 at 9:24 PM Stéphane Ducasse wrote: > I know what is it to write book. > I sent you some support and I want to be a reviewer. > Would be my pleasure Stef ! Today was a wonderful start ! Thank you, Nick > > Stef > > On 17 Mar 2019, at 20:35, Nick Papoylias wrote: > >

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

I know what is it to write book. I sent you some support and I want to be a reviewer. Stef > On 17 Mar 2019, at 20:35, Nick Papoylias wrote: > > That was good to know. I updated the site with one-click direct > (non-recurring) alternative: PayPal.Me for Lands >

Re: [Pharo-dev] Roassal Animations

+10, I’ve loved them them too. > On 17 Mar 2019, at 19:40, Sven Van Caekenberghe wrote: > > > >> On 17 Mar 2019, at 20:10, Serge Stinckwich >> wrote: >> >> Most of the animations are available in the Roassal3 code: >> >> https://github.com/ObjectProfile/Roassal3 > > Yes, OK, but maybe

Re: [Pharo-dev] Roassal Animations

> On 17 Mar 2019, at 20:10, Serge Stinckwich wrote: > > Most of the animations are available in the Roassal3 code: > > https://github.com/ObjectProfile/Roassal3 Yes, OK, but maybe there is some webpage somewhere that collects the Twitter posts, they were really good advertisements. > On

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

That was good to know. I updated the site with* one-click direct* *(non-recurring) alternative*: *PayPal.Me for Lands* https://npapoylias.gitlab.io/lands-project/Support/ *"Alternatively you can make a direct (non-recurrent) contribution * *through paypal.me

Re: [Pharo-dev] Roassal Animations

Most of the animations are available in the Roassal3 code: https://github.com/ObjectProfile/Roassal3 On Sun, Mar 17, 2019 at 7:23 PM Sven Van Caekenberghe wrote: > Hi, > > Who has seen these Roassal Animations on Twitter recently ? > > These are crazy cool and super slick. > > Is there a place

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

> On 17 Mar 2019, at 18:28, Benoit St-Jean wrote: > > If that was the case, then it makes no sense to implement #upTo: but not > #upToAll: , right Indeed :) > > On 2019-03-17 10:37, ducasse wrote: >> Was there a conscious decision not to include the #upToAll: method >>

Re: [Pharo-dev] Roassal Animations

> On 17 Mar 2019, at 19:23, Sven Van Caekenberghe wrote: > > Hi, > > Who has seen these Roassal Animations on Twitter recently ? Me :) > These are crazy cool and super slick. > > Is there a place where they are all collected, maybe with their code ? We should ask milton and alex > Sven

[Pharo-dev] Roassal Animations

Hi, Who has seen these Roassal Animations on Twitter recently ? These are crazy cool and super slick. Is there a place where they are all collected, maybe with their code ? Sven

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

--- Begin Message --- If that was the case, then it makes no sense to implement #upTo: but not #upToAll: , right On 2019-03-17 10:37, ducasse wrote: Was there a conscious decision not to include the #upToAll: method onZnBufferedReadStream?. This method is really useful for parsing files

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

Eric, Someone wrote a clean implementation of #upToAll: that does not use #position: - I forgot who - but it can be found in ZnCharacterReadStream>>#upToAll: I guess this could be copied over to ZnBufferedReadStream. The main reason that I was against #upToAll: was the implementation using

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

On Sun, Mar 17, 2019 at 2:18 PM Stéphane Ducasse wrote: > Hi nick > > I wanted to support your chapters via paypal but it asked me about my visa > and I would like > to pay via my paypal account. Do you know if this is possible? > Thanx Stef ! *Through patreon, this seems to be required for

[Pharo-dev] [Pharo 8.0] Build #146: 2843-Clean-Navigation-code

There is a new Pharo build available! The status of the build #146 was: SUCCESS. The Pull Request #2844 was integrated: "2843-Clean-Navigation-code" Pull request url: https://github.com/pharo-project/pharo/pull/2844 Issue Url: https://pharo.fogbugz.com/f/cases/2843 Build Url:

[Pharo-dev] [Pharo 8.0] Build #145: 2817-distinguish-between-instance-side-and-class-side-in-method-template

There is a new Pharo build available! The status of the build #145 was: SUCCESS. The Pull Request #2819 was integrated: "2817-distinguish-between-instance-side-and-class-side-in-method-template" Pull request url: https://github.com/pharo-project/pharo/pull/2819 Issue Url:

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

Thanks Stef, I imagine that sven did not add it because on infinite stream it does not > make sense. > Just to clarify my earlier email, I got here was by calling `'/path/to/some/file' asFileReference binaryReadStream` which responds with the ZnBufferedReadStream. I expected to be able to use

Re: [Pharo-dev] ZnBufferedReadStream and #upToAll:

Hi eric > Hi all, > > Was there a conscious decision not to include the #upToAll: method > onZnBufferedReadStream?. This method is really useful for parsing files -- > finding sub-patterns of bytes, etc. Perhaps #upToAll: is not the idiomatic > way to do this, but I found it very useful to

[Pharo-dev] ZnBufferedReadStream and #upToAll:

Hi all, Was there a conscious decision not to include the #upToAll: method onZnBufferedReadStream?. This method is really useful for parsing files -- finding sub-patterns of bytes, etc. Perhaps #upToAll: is not the idiomatic way to do this, but I found it very useful to use in the plain old

[Pharo-dev] is haltOnce working in P8?

Because I have experiences showing me that haltOnce is executed multiple times. Stef Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59

Re: [Pharo-dev] [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

Hi nick I wanted to support your chapters via paypal but it asked me about my visa and I would like to pay via my paypal account. Do you know if this is possible? Else can you send me your pp account? Stef > On 17 Mar 2019, at 10:21, Nick Papoylias wrote: > > Dear friends ! > > I am quite

[Pharo-dev] [Pharo 8.0] Build #144: 2753-betterFileVersionExtraction

There is a new Pharo build available! The status of the build #144 was: FAILURE. The Pull Request #2848 was integrated: "2753-betterFileVersionExtraction" Pull request url: https://github.com/pharo-project/pharo/pull/2848 Issue Url: https://pharo.fogbugz.com/f/cases/2753 Build Url:

Re: [Pharo-dev] ZdcAbstractSocketStream>>peekFor:?

Hi Sven, On Sat, 16 Mar 2019 at 20:28, Sven Van Caekenberghe wrote: > > Here please, https://github.com/svenvc/zodiac Done. The changes were made in Pharo 8 and it's added lots of methodProperties.json files. I assume this is because you haven't had to make changes since Iceberg was

[Pharo-dev] ZnMimePart

Hi Sven, I'm trying to parse maildir emails using ZnMimePart and have a few questions: 1. The standard indicates that text lines should be terminated with CRLF, however in practice many maildir format emails (as saved by offlineimap and successfully handled by mutt) use LF. Are you open to