- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bloc status

by Juraj Kubelka

Please check the github-cache directory. You may do not use the Iceberg integration. Or you may share repositories among images: IceRepository shareRepositoriesBetweenImages ifTrue: [ IceRepository sharedRepositoriesLocationString ] Cheers, Juraj > On Oct 24, 2017, at 16:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > This is what I see: > <http://forum.world.st/file/t128965/Screenshot_2017-10-24_15.jpeg> > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 24, 2017

Re: [Pharo-dev] Pharo Process question

by Esteban Lorenzano

> On 24 Oct 2017, at 21:47, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi > > are the pending PR reevaluated when one PR is integrated? it was, but Guille disabled it because it was killing the server. when we jump to tonel we can re-evaluate the problem :) Esteban > > Stef >

Oct. 24, 2017

Re: [Pharo-dev] Bloc status

by Stephane Ducasse

Sean are you using the launcher? because your github clone repo and download code should be close to the PharoLauncher image repo. Stef On Tue, Oct 24, 2017 at 9:32 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > This is what I see: > <http://forum.world.st/file/t128965/Screenshot_2017-10-24_15.jpeg> > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Oct. 24, 2017

Pharo Process question

by Stephane Ducasse

Hi are the pending PR reevaluated when one PR is integrated? Stef

Oct. 24, 2017

Re: [Pharo-dev] Bloc status

by Sean P. DeNigris

This is what I see: <http://forum.world.st/file/t128965/Screenshot_2017-10-24_15.jpeg> ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 24, 2017

Re: [Pharo-dev] Bloc status

by Tudor Girba

Then you should have a "pharo-local/iceberg/feenkcomâ folder somewhere because this is where iceberg puts the files. Could you please check. Doru > On Oct 24, 2017, at 8:06 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Pharo #60513 via Launcher. Loaded GT as per GH readme: > Iceberg enableMetacelloIntegration: true. > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

Oct. 24, 2017

Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations

by henry

Please see version 3.6 proposed for a new dual protocol. https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… - HH > -------- Original Message -------- > Subject: Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations > Local Time: October 24, 2017 1:42 PM > UTC Time: October 24, 2017 5:42 PM > From: henry(a)callistohouse.club > To: Stephane Ducasse <stepharo.self(a)gmail.com>, Pharo Development List <pharo-dev(a)lists.pharo.org> > > Please excuse all the low-level detail, if inappropriate to the discussion. The protocol changes are here specified. > > - HH > > On Tue, Oct 24, 2017 at 13:40, henry <[henry(a)callistohouse.club]("mailto:henry@callistohouse.club")> wrote: > >> In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol of >> >> - ProtocolOffered { offered, preferred } >> - ProtocolAccepted { accepted } >> - IWant|GiveInfo|ReplyInfo { vatId, domain, publicKey, cryptoProtocols, dataEncoders } >> - IAm|ReplyInfo { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParam } >> - Go { cryptoProtocol, dataEncoder, dhParam, signature } >> - GoToo { signature } >> >> Using eLinda : >> >> [http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz]("http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz") >> >> Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame, with set selected version, to route to the correct SessionOperation to support each version of the protocol. >> >> With a non-specific vatId required, anonymous connections would be supported. >> >> - HH >> >> On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <[stepharo.self(a)gmail.com](""mailto:stepharo.self@gmail.com"")> wrote: >> >>> Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH

Oct. 24, 2017

Re: [Pharo-dev] Bloc status

by Sean P. DeNigris

Pharo #60513 via Launcher. Loaded GT as per GH readme: Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 24, 2017

Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations

by henry

Please excuse all the low-level detail, if inappropriate to the discussion. The protocol changes are here specified. - HH On Tue, Oct 24, 2017 at 13:40, henry <[henry(a)callistohouse.club]("mailto:henry@callistohouse.club")> wrote: > In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol of > > - ProtocolOffered { offered, preferred } > - ProtocolAccepted { accepted } > - IWant|GiveInfo|ReplyInfo { vatId, domain, publicKey, cryptoProtocols, dataEncoders } > - IAm|ReplyInfo { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParam } > - Go { cryptoProtocol, dataEncoder, dhParam, signature } > - GoToo { signature } > > Using eLinda : > > [http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz]("http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz") > > Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame, with set selected version, to route to the correct SessionOperation to support each version of the protocol. > > With a non-specific vatId required, anonymous connections would be supported. > > - HH > > On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <[stepharo.self(a)gmail.com](""mailto:stepharo.self@gmail.com"")> wrote: > >> Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH @callistohouse.club>

Oct. 24, 2017

Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations

by henry

In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol of - ProtocolOffered { offered, preferred } - ProtocolAccepted { accepted } - IWant|GiveInfo|ReplyInfo { vatId, domain, publicKey, cryptoProtocols, dataEncoders } - IAm|ReplyInfo { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParam } - Go { cryptoProtocol, dataEncoder, dhParam, signature } - GoToo { signature } Using eLinda : http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame, with set selected version, to route to the correct SessionOperation to support each version of the protocol. With a non-specific vatId required, anonymous connections would be supported. - HH On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <[stepharo.self(a)gmail.com]("mailto:stepharo.self@gmail.com")> wrote: > Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH @callistohouse.club>

Oct. 24, 2017