November 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About Collator

by Nicolas Cellier

2017-11-05 10:16 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > > On 5 Nov 2017, at 06:00, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > Hi guys > > > > Why do we rename class Sort to introduce terms that have unknown, > > unclear, undocumented meaning? > > +1 > > > > > To me PluggableSortFunction is MUCH better than CollatorBlockFunction. > > but pluggable is also bad, IMO. > also I see there is some incoherence in the names: > agree with Esteban, Pluggable pouah! > ChainedSortFunction -> this is kind of ok, but I think a > âComposedSortFunctionâ is better. > But there can be several kind of composition... For example wrapped as illustrated with UnderfinedSorter refactoring that I proposed. Personnally I like Chained because it explicitely tells the kind of composition SortByPropertyFunction -> shouldnât be âPropertySortFunctionâ ? (coherent > with the previous one) > +1 for PropertySortFunction, or maybe just PropertySorter CollatorSortFunction -> this is like a âBlockSortFunctionâ or > âValuableSortFunctionâ ? > CollatorBlockFunction is only a proxy to the block so as it answers to #threeWayCompare:with: protocol rather than value:value: It's a Block view as a CollatorFunction. The name first surprised me negatively, but after reflexion it tells what it is. 1) Collator indicates that the block (valuable) will return -1, 0 or +1 2) It's not necessarily a block, it could be anything understanding value:value: But, the valuable should return -1,0,+1, so apart <=> (threeWayCompareTo:) it ain't gonna be anything but a block in practice. For <=> we would want a DefaultSortFunction and would not use a CollatorBlockFunction. 3) Function refers to SortFunction. For this, I'm neutral, whether you call it Sorter or SortFunction I don't care. SortFunction kind of implies these are stateless, so it's a rather good and accurate name. Maybe a Sorter could be more confusing, because a Sorter could be thought as having the sorted collection as instance variable (statefull). Nicolas > Esteban > > > > > Stef > > > > >

Nov. 5, 2017

Re: [Pharo-dev] about SortFunctions

by Denis Kudriashov

Hi Nicolas. We had discussion on operator <=> in original case where SortFunction was integrated https://pharo.fogbugz.com/f/cases/17728/Integrate-Travis-Griggs-TAG-SortFun… . 2017-11-05 0:37 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > Hi all, > I started a discussion with Denis in a pull request > https://github.com/pharo-project/pharo/pull/430 > But since it's going beyond simple code review, it probably has a better > place here. > > First, I want to say thanks for enriching this original work of Travis > Griggs. > http://objology.blogspot.fr/2010/11/tag-sortfunctions-redux.html > http://objology.blogspot.fr/2010/11/tag-sortfunctions.html > <http://objology.blogspot.fr/2010/11/tag-sortfunctions-redux.html> > > Of course, I'm never satisfied. > So I don't really appreciate the rewrite of space ship operator <=> into a > more heavy threeWayCompareTo: > > In my eyes, it's so obvious that <=> means < or = or > in the context of > SortFunction > And also that the order matches the signs > < = > > -1 0 1 > IOW result will be -1 if receiver is <, 0 if equal, +1 if superior > > #threeWayCompareTo: does not tell as well. > But maybe It's a question of taste and I don't have the same eyes as Pharo > people? > To me it's also a question of respect to the original author, don't change > a good selector for the sake of changing. > > Apart this detail, I wanted to speak about SortByPropertyFunction. > SortByProperty is super usefull for composing / chaining like this: > > population sortBy: #name ascending , #age descending. > > But currently, SortByPropertyFunction is allways using the default > hardcoded collation <=> ... He he, it's also notice it's shorter to write ;) > > Imagine that my properties are neither String nor Magnitude, or they are, > but I want a different collation policy, because in French $Ã© must not be > sorted too far from $e. > > It could be written quite simply with: > > c sortBy: #name collatedInFrench ascending , #age descending > > With current implementation, collatedInFrench would have to use a block > (thru a CollatorBlockFunction which is a proxy to the block in a > SortFunction disguise): > > Symbol>>collatedInFrench > "interpret self as a property" > ^[:a :b | FrenchCollator collate: (self value: a) with: (self > value: b)] > > But IMO SortByPropertyFunction should better feed a reified > CollatorFunction, or said differently a SortFunction, as Denis said. > > Symbol>>collatedInFrench > ^FrenchCollator new onProperty: self > > SortFunction>>onProperty: aValuable > ^SortByPropertyFunction sortProperty: aValuable with: self > > What do you think? > > Nicolas > >

Nov. 5, 2017

Re: [Pharo-dev] [squeak-dev] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption

by henry

Thank you, Ben, weâll see Iâll let you know. Sent from ProtonMail Mobile On Sun, Nov 5, 2017 at 06:14, Ben Coman <btc(a)openinworld.com> wrote: > Good luck with it. > cheers -ben > > On Sun, Nov 5, 2017 at 5:17 AM, henry <henry(a)callistohouse.club> wrote: > >> I am preparing an Internet Draft for submission through IETF. Listed below. >> >> Sent from ProtonMail Mobile >> >>> ---------- Forwarded message ---------- >>> From: Bob<robert.withers(a)protonmail.com> >>> Date: On Sat, Nov 4, 2017 at 13:56 >>> Subject: Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>> To: Bob <robert.withers(a)protonmail.com > >>> Cc: SAAG <saag(a)ietf.org> >>> >>> I updated the I-D located here: http://jmp.sh/VRejS2g >>> >>> Thank you for your consideration, >>> - HH >>> >>>> -------- Original Message -------- >>>> Subject: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>>> Local Time: November 3, 2017 9:07 AM >>>> UTC Time: November 3, 2017 1:07 PM >>>> From: robert.withers(a)protonmail.com >>>> To: SAAG <saag(a)ietf.org> >>>> >>>> Good morning, >>>> >>>> I am forwarding this announcement of the ParrotTalk v3.6 specification and 2 reference implementations, in Squeak/Pharo and Java, to the SAAG list. I was advised that this mailing list regarding the Security Area is the correct home for this announcement. Below, I corrected the version of the Squeak/Pharo ParrotTalk code to version 11, interoperable with the Java version. I am proceeding to work on the Internet-Draft and I hope some discussion builds around this work. >>>> >>>> Thank you. >>>> - HH >>>> >>>>> -------- Original Message -------- >>>>> Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>>>> Local Time: November 2, 2017 9:19 PM >>>>> UTC Time: November 3, 2017 1:19 AM >>>>> From: henry(a)callistohouse.club >>>>> To: IETF <ietf(a)ietf.org> >>>>> >>>>> I have developed the ParrotTalk Protocol, and am starting an internet draft document[1] for submission to the process at IETF. >>>>> >>>>> ParrotTalk Protocol is documented in part here[2], while I have two implementations: 1 in Squeak/Pharo[3 a/b] and the other in Java[4 a/b]. The particulars of MAC key and ivSequence derivation, as well as constrained traffic signing, are the implementations, yet missing from the specification. They will be added to the internet-draft. >>>>> >>>>> How do I go about submitting a specification for ParrotTalk for IETF review and consideration? >>>>> >>>>> Thank you. >>>>> >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH

Nov. 5, 2017

Re: [Pharo-dev] [Pharo7.0a] Next batch of enhancements

by Sean P. DeNigris

Guillermo Polito wrote > Question: would you like that we set-up a jenkins job that sends this > report every saturday or monday morning? I found this format valuable. Would it be in addition to or in lieu of the current one-per-issue CI notifications? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 5, 2017

Re: [Pharo-dev] How to update currently used VM for PharoLauncher?

by stephan

On 04-11-17 20:29, Christophe Demarey wrote: > It makes sense only for the development image but it could be a nice > option to add to the launcher. Do you think it will be used? I have a personal need for it, but that should of course not be the determining factor. I see several scenario's for this: - A 'normal' user notices a problem, that gets fixed in a development vm. She needs to test and use it, is probably not interested in following all other new development vms, and ideally should switch as soon as possible to using a newer stable vm again. Supporting the automatic switch to a newer stable vm makes sense for us to avoid having too many new users using the unstable versions. It might be useful to make that decision for an individual image, when other projects are not affected by the issue. So here there would be two choices: I want to download a latest (or version) vm and automatically upgrade to a newer stable when that arrives, and I want to use that for only this image or for all fitting images. - At the moment I'm running into a lot of the current vm issues. I have some production images that should be using stable, but in my development I want to just use the latest vm that managed to get green tests :) Nearly all new versions are improvements, but once in a while there are changes that need to be reverted. So there I just want to check before starting an image if there is a new vm I can use, and will just ignore that once in a while there is a broken one. Stephan

Nov. 5, 2017

Re: [Pharo-dev] [Pharo-users] [Pharo7.0a] Next batch of enhancements

by Pavel Krivanek

Ups, my fault. -- Pavel 2017-11-05 12:58 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Just a side note, all text preceded by >> in the mail is the original pull > request comment. So it was the PR comment that was wrong. We decided with > Stef to let the comment untouched and not parse it, because we cannot > depend on what people put as a comment... > > On Sun, Nov 5, 2017 at 12:32 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> >> >> On Sun, Nov 5, 2017 at 7:00 PM, PBKResearch <peter(a)pbkresearch.co.uk> >> wrote: >> >>> >>> I managed to find the fogbugz entry - not easy, because it has been >>> closed, >> >> so clicking on the link gives 404 >> >> >> btw, I don't think the 404 has anything to do with the case being >> closed. >> The url is simply incorrect. Compare the last slash in this correct >> url... >> https://pharo.fogbugz.com/f/cases/20587/remove-UIThemeWatery >> >> >>> * 20587-remove-UIThemeWatery >>> >> https://pharo.fogbugz.com/f/cases/20587-remove-UIThemeWatery >>> >>> >> >> this issue url works fine... >> >>> Issue URL: https://pharo.fogbugz.com/f/cases/20587 >>> >> >> >> >>> PR URL: https://github.com/pharo-project/pharo/pull/395 >>> Diff URL: https://github.com/pharo-project/pharo/pull/395/files >>> >> >> >> cheers -ben >> >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Nov. 5, 2017

Re: [Pharo-dev] [Pharo-users] [Pharo7.0a] Next batch of enhancements

by Guillermo Polito

Just a side note, all text preceded by >> in the mail is the original pull request comment. So it was the PR comment that was wrong. We decided with Stef to let the comment untouched and not parse it, because we cannot depend on what people put as a comment... On Sun, Nov 5, 2017 at 12:32 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Sun, Nov 5, 2017 at 7:00 PM, PBKResearch <peter(a)pbkresearch.co.uk> > wrote: > >> >> I managed to find the fogbugz entry - not easy, because it has been >> closed, > > so clicking on the link gives 404 > > > btw, I don't think the 404 has anything to do with the case being closed. > The url is simply incorrect. Compare the last slash in this correct > url... > https://pharo.fogbugz.com/f/cases/20587/remove-UIThemeWatery > > >> * 20587-remove-UIThemeWatery >> >> https://pharo.fogbugz.com/f/cases/20587-remove-UIThemeWatery >> >> > > this issue url works fine... > >> Issue URL: https://pharo.fogbugz.com/f/cases/20587 >> > > > >> PR URL: https://github.com/pharo-project/pharo/pull/395 >> Diff URL: https://github.com/pharo-project/pharo/pull/395/files >> > > > cheers -ben > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Nov. 5, 2017

Re: [Pharo-dev] [Pharo-users] [Pharo7.0a] Next batch of enhancements

by Ben Coman

On Sun, Nov 5, 2017 at 7:00 PM, PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > I managed to find the fogbugz entry - not easy, because it has been > closed, so clicking on the link gives 404 btw, I don't think the 404 has anything to do with the case being closed. The url is simply incorrect. Compare the last slash in this correct url... https://pharo.fogbugz.com/f/cases/20587/remove-UIThemeWatery > * 20587-remove-UIThemeWatery > >> https://pharo.fogbugz.com/f/cases/20587-remove-UIThemeWatery > > this issue url works fine... > Issue URL: https://pharo.fogbugz.com/f/cases/20587 > > PR URL: https://github.com/pharo-project/pharo/pull/395 > Diff URL: https://github.com/pharo-project/pharo/pull/395/files > cheers -ben

Nov. 5, 2017

Re: [Pharo-dev] [squeak-dev] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption

by Ben Coman

Good luck with it. cheers -ben On Sun, Nov 5, 2017 at 5:17 AM, henry <henry(a)callistohouse.club> wrote: > I am preparing an Internet Draft for submission through IETF. Listed below. > > > Sent from ProtonMail Mobile > > ---------- Forwarded message ---------- > From: Bob<robert.withers(a)protonmail.com> > Date: On Sat, Nov 4, 2017 at 13:56 > Subject: Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous > P2P encryption > To: Bob <robert.withers(a)protonmail.com> > Cc: SAAG <saag(a)ietf.org> > I updated the I-D located here: http://jmp.sh/VRejS2g > > Thank you for your consideration, > - HH > > -------- Original Message -------- > Subject: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P > encryption > Local Time: November 3, 2017 9:07 AM > UTC Time: November 3, 2017 1:07 PM > From: robert.withers(a)protonmail.com > To: SAAG <saag(a)ietf.org> > > Good morning, > > I am forwarding this announcement of the ParrotTalk v3.6 specification and > 2 reference implementations, in Squeak/Pharo and Java, to the SAAG list. I > was advised that this mailing list regarding the Security Area is the > correct home for this announcement. Below, I corrected the version of the > Squeak/Pharo ParrotTalk code to version 11, interoperable with the Java > version. I am proceeding to work on the Internet-Draft and I hope some > discussion builds around this work. > > Thank you. > - HH > > -------- Original Message -------- > Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption > Local Time: November 2, 2017 9:19 PM > UTC Time: November 3, 2017 1:19 AM > From: henry(a)callistohouse.club > To: IETF <ietf(a)ietf.org> > > I have developed the ParrotTalk Protocol, and am starting an internet > draft document[1] for submission to the process at IETF. > > ParrotTalk Protocol is documented in part here[2], while I have two > implementations: 1 in Squeak/Pharo[3 a/b] and the other in Java[4 a/b]. The > particulars of MAC key and ivSequence derivation, as well as > constrained traffic signing, are the implementations, yet missing from the > specification. They will be added to the internet-draft. > > How do I go about submitting a specification for ParrotTalk for IETF > review and consideration? > > Thank you. > > - HH > - HH > - HH > - HH > - HH > - HH > - HH > - HH > > > > > > >

Nov. 5, 2017

Re: [Pharo-dev] How to update currently used VM for PharoLauncher?

by Ben Coman

On Sun, Nov 5, 2017 at 3:29 AM, Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi Stefan, > > > Le 3 nov. 2017 Ã 17:23, stephan <stephan(a)stack.nl> a Ã©crit : > > > > I've noticed a few VM updates I want to use with PharoLauncher. > > What is the currently recommended way to update my PharoLauncher to use > > a non-stable version? > > For now, the way to get a fresh VM for the current development image (i.e. > 70) is to delete it from the VM store ($HOME/Documents/Pharo/vms/70 on OS > X) and try to run again the image will download the latest stable VM. > If you need another VM, you will have to install it by hand in the same > directory. There is currently no option to get an alpha VM. It makes sense > only for the development image but it could be a nice option to add to the > launcher. Do you think it will be used? > It would be useful to be able to be explicit about which VM is used to run an image, and the VMs to be selectable. When someone reports "I've a problem with Image Build X on VM Build Y" this would facilitate others replicating that configuration. cheers -ben

Nov. 5, 2017