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

If I google... parrottalk protocol nothing seems related. So what is ParrotTalk? P.S... since this is not "part of" pharo, [pharo-users] would be a better place for discussion than [pharo-dev]. Could you re-announce there, with some description of use cases and who/where the protocol is used?

Re: [Pharo-dev] Bloc status

Juraj Kubelka wrote > Or you may share repositories among images… kIceRepository > sharedRepositoriesLocationString That was it! It was {IcebergSharedRepoFolder}/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar Now that I can see the presentations… Super cool!! Putting more $! in front of

Re: [Pharo-dev] DateModel Deprecation

Sean P. DeNigris wrote > Does anyone know why poor DateModel is being picked on? ;) Oops, never mind. I see it's just been renamed. Pheew, that was a close one ha ha - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] DateModel Deprecation

Does anyone know why poor DateModel is being picked on? ;) It is used e.g. by Magritte. I also made a slice to fix the problem with nil handling two years ago. - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] [Pharo 7.0-dev] Build #225: SUCCESS

There is a new Pharo build available! The status of the build #225 was: SUCCESS. Could not extract further issue information from commit message: Better Zinc! Super! Build Url:

Re: [Pharo-dev] Bloc status

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.

Re: [Pharo-dev] Pharo Process question

> On 24 Oct 2017, at 21:47, Stephane Ducasse 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 >

Re: [Pharo-dev] Bloc status

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 wrote: > This is what I see: >

[Pharo-dev] Pharo Process question

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

Re: [Pharo-dev] Bloc status

This is what I see: - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Bloc status

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 wrote: > > Pharo #60513 via Launcher. Loaded GT as per GH readme: >

Re: [Pharo-dev] Bloc status

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

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

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 <[he...@callistohouse.club]("mailto:he...@callistohouse.club;)> wrote: > In order to bring ParrotTalk-3.6 support, alongside

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

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

Re: [Pharo-dev] UnifiedFFI Docs

Hey Esteban, Now that you have outed yourself as a maintainer of FFI, I have a question. :-) I want to call the libclang function: /** * \brief Parse the given source file and the translation unit corresponding * to that file. * * This routine is the main entry point for the Clang C API,

Re: [Pharo-dev] latest Cryptography package integration

I am grateful for your interest. The issue is conflicting requirements: 1 - same package for Squeak and Pharo. 2 - X509 support is spurious but RSA depends on ASN.1 support 3 - Pharo [and Squeak!] both have hash functions and DigitalSecureAlgorithm that may get overwritten, leading to... 4 -

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

In my tests, at the moment. Only there. I derived the ParrotTalk-3.5 spec from eright’s.org’s ELib implementation. Do you think I should change the spec to allow for free, anonymous connections? - HH On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse

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

Oh! I was U.N.familiar with Parrot drones. That’s awesome! Well how about using encrypted communications with a Parrot drone? This is the purpose and accomplishment of ParrotTalk, encrypted communications. In 33 classes, minus 4 test classes with 16 tests (same #, 16, as eLinda!), ParrotTalk

Re: [Pharo-dev] latest Cryptography package integration

I would like the package to be working for Pharo. Now from your description I have problem to really understand the situation. I think that Pharo core should have minimum and packages should be able to be loaded nicely on top. > Currently, SHA1, SHA256 and MD5 all get redefined by

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

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

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

Hi! What ParrotTalk is about? It does not seem related to the drone stuff (https://www.parrot.com) ? (Which I first thought). I had a look at the .pdf you’ve sent, it seems to do something with networking Cheers, Alexandre > On Oct 24, 2017, at 9:33 AM, henry

[Pharo-dev] latest Cryptography package integration

I am curious as to integration of the newest Cryptography package there into Pharo. There are two Undeclared: SoundRecorder and FillInTheBlank, though I do not know if such would be a part of a Pharo-Squeak compatibility layer. More pertinent would be what to do with the HashFunctions that

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

> On 24 Oct 2017, at 17:56, henry wrote: > > Hi Marcus, > > Are you using SHA256 inside Pharo to generate the checksum files? If so were > you planning to use the OpenPGP by hmmosner, in the Cryptography repository > for PGP signatures? > No, this just uses

Re: [Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

Hi Marcus, Are you using SHA256 inside Pharo to generate the checksum files? If so were you planning to use the OpenPGP by hmmosner, in the Cryptography repository for PGP signatures? I am curious as to integration of the newest Cryptography package there into Pharo. There are two Undeclared:

[Pharo-dev] [Pharo 7.0-dev] Build #224: 20574-FFITypeArray--annonymousClassCreator-doesnt-handle-pointer-types-correctly

There is a new Pharo build available! The status of the build #224 was: SUCCESS. The Pull Request #392 was integrated: "20574-FFITypeArray--annonymousClassCreator-doesnt-handle-pointer-types-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/392 Issue Url:

[Pharo-dev] [ANN] Pharo Consortium New Platinum Member: Ingenieurbüro für Bauwesen Schmidt GmbH

The Pharo Consortium is very happy to announce that Ingenieurbüro für Bauwesen Schmidt GmbH has joined the Consortium as a Platinum Member. About - Ingenieurbüro für Bauwesen Schmidt GmbH: http://bauing-schmidt.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium

[Pharo-dev] [ANN] sha256 checksum for Pharo6 downloads

Hi, A tiny first step: I added sha256 chechsums for all downloads created by the Pharo6 build process https://ci.inria.fr/pharo/ This step: https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-5-Publish/

[Pharo-dev] [Pharo 7.0-dev] Build #223: 20580-ValueChanged-should-be-moved-to-System-Model

There is a new Pharo build available! The status of the build #223 was: SUCCESS. The Pull Request #390 was integrated: "20580-ValueChanged-should-be-moved-to-System-Model" Pull request url: https://github.com/pharo-project/pharo/pull/390 Issue Url:

Re: [Pharo-dev] Bloc status

What Pharo are you using and how did you load the code? Doru > On Oct 24, 2017, at 3:49 PM, Sean P. DeNigris wrote: > > Tudor Girba-2 wrote >> In the meantime, the file is in: >> ./pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar > > I don't

Re: [Pharo-dev] Probably stupid... question about string printString.

Hi Torsten, On Sun, Oct 22, 2017 at 10:40:41AM +0200, Torsten Bergmann wrote: > Alistair Grant wrote: > > I can't comment on the original thinking behind this > > The original thinking is simple and as the name says: you want to print the > object (even when it is a string) to be print in a

Re: [Pharo-dev] Bloc status

Tudor Girba-2 wrote > In the meantime, the file is in: > ./pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar I don't seem to even have ./pharo-local/iceberg! - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Iceberg - viewing uncommitted changes

Hi Ben, On Tue, Oct 03, 2017 at 09:36:59PM +0800, Ben Coman wrote: > When the Iceberg [Packages] tab shows "Uncommitted changes", > how do you view what those changes are? > > For example... > $ curl get.pharo.org/70+vm | bash > $ ./pharo-ui > * Open System > Settings > Include system

[Pharo-dev] [Pharo 7.0-dev] Build #222: 20575-TextMorph-cannot-work-without-code-completion-temporary-solution

There is a new Pharo build available! The status of the build #222 was: SUCCESS. The Pull Request #387 was integrated: "20575-TextMorph-cannot-work-without-code-completion-temporary-solution" Pull request url: https://github.com/pharo-project/pharo/pull/387 Issue Url:

Re: [Pharo-dev] System Update Failure from #60510 -> #60513

Hi, I have copied it over! Thanks, Marcus > On 22 Oct 2017, at 03:55, Sean P. DeNigris wrote: > > Marcus Denker-4 wrote >> yes, can you send it to me? I will add it. > > It's in the Pharo60Inbox. Of course I can still send it to you if

[Pharo-dev] [Pharo 7.0-dev] Build #221: 20573-BaselineOfMorphic-should-include-System-Identification

There is a new Pharo build available! The status of the build #221 was: SUCCESS. The Pull Request #384 was integrated: "20573-BaselineOfMorphic-should-include-System-Identification" Pull request url: https://github.com/pharo-project/pharo/pull/384 Issue Url:

Re: [Pharo-dev] Some segfault crashes and freezes when trying to re-run saved pharo 7 images

Hi again, I checked with Stef this morning. Starting the image on a VM without Freetype solves the problem. Just open the VM, remove or rename the Freetype dynamic libraries (FT2, Freetype, 3 libs in total), then start your image. That's unfortunate the hexadecimal editor solution is so much

[Pharo-dev] Iceberg. Uncommited changes just after loading code from a repo?

Hello, After cloning a repo with Iceberg, loading the code and before doing any change, iceberg sees a lot of additions to the code in the "Synchronize Repository" window. Here are the steps I followed: - Load fresh Pharo7 image - Delete the previous clone of my repo in

Re: [Pharo-dev] Bloc Feedback

Hi, Indeed, instance variables is what we are mainly concerned with as well. We keep on trimming, but it still feels like too many variables. Cheers, Doru > On Oct 24, 2017, at 8:59 AM, Nicolai Hess wrote: > > > > 2017-10-24 2:04 GMT+02:00 Sean P. DeNigris

Re: [Pharo-dev] Bloc Feedback

2017-10-24 2:04 GMT+02:00 Sean P. DeNigris : > Tudor Girba-2 wrote > > Thanks for the feedback! > > But of course! Thanks for pushing Bloc :) IMHO a clean low-level graphics > framework is the linchpin to unleash a tremendous amount of creativity in > the Pharo community. I

Re: [Pharo-dev] Bloc status

> On Oct 24, 2017, at 2:09 AM, Sean P. DeNigris wrote: > > Tudor Girba-2 wrote >> right now we have three such "real life scenarios” that you can play with: > > Are these safe to load in a working image? IOW could one switch back and > forth between the standard and