- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ Article ] LampSort, a non-recursive QuickSort implementation

by Sven Van Caekenberghe

> On 08 Dec 2014, at 19:59, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Well written and very dictactic. Thanks, that was the idea. > Do you have this text as a class comment in your class? Well, not completely, but there are links to the article in the class comment: https://github.com/svenvc/lampsort/tree/master/LampSort.package/LampSort.cl… > Cheers, > Alexandre > > >> Le 08-12-2014 Ã 15:36, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : >> >> Hi, >> >> Here is another article I just published >> >> LampSort, a non-recursive QuickSort implementation >> >> The divide and conquer partitioning is at the heart of QuickSort >> >> https://medium.com/@svenvc/lampsort-a-non-recursive-quicksort-implementatio… >> >> Pharo makes it easy to implement this non-recursive version of QuickSort - and beautiful as well. >> >> Sven >> >> >

Dec. 8, 2014

Re: [Pharo-users] [ Article ] LampSort, a non-recursive QuickSort implementation

by Alexandre Bergel

Well written and very dictactic. Do you have this text as a class comment in your class? Cheers, Alexandre > Le 08-12-2014 Ã 15:36, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > > Hi, > > Here is another article I just published > > LampSort, a non-recursive QuickSort implementation > > The divide and conquer partitioning is at the heart of QuickSort > > https://medium.com/@svenvc/lampsort-a-non-recursive-quicksort-implementatio… > > Pharo makes it easy to implement this non-recursive version of QuickSort - and beautiful as well. > > Sven > >

Dec. 8, 2014

[ Article ] LampSort, a non-recursive QuickSort implementation

by Sven Van Caekenberghe

Hi, Here is another article I just published LampSort, a non-recursive QuickSort implementation The divide and conquer partitioning is at the heart of QuickSort https://medium.com/@svenvc/lampsort-a-non-recursive-quicksort-implementatio… Pharo makes it easy to implement this non-recursive version of QuickSort - and beautiful as well. Sven

Dec. 8, 2014

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

by Tommaso Dal Sasso

On 08/12/14 17:32, Sven Van Caekenberghe wrote: >> On 08 Dec 2014, at 17:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> We should add this explanation to the tool itselfâ¦ >> >> Marcus > Yes, and maybe also show the actual stack trace and other info that will be sent in dialog so that the user can see precisely what gets shared. > OK, I'll add a help button with detailed description of the submitted data. The stack trace is already displayed, I will also add the additional information to the displayed data. Tommaso

Dec. 8, 2014

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

by Sven Van Caekenberghe

> On 08 Dec 2014, at 17:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 08 Dec 2014, at 16:34, Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com> wrote: >> >> >> On 08/12/14 14:47, Sven Van Caekenberghe wrote: >>> Hi Tommaso, >>> >>> I think this is a cool initiative, many environments have something similar, so this is a welcome addition. >>> >>> However, you must be clearer about the security implications (and/or tell us how these concerns are dealt with in other places). Say I execute: >>> >>> ZnEasy >>> get: 'http://zn.stfx.eu/nuclear-launch-codes.txt' >>> username: 'barak.obama(a)whitehouse.gov' >>> password: 'michele'. >>> >>> This will leave sensitive hosts, ports, URIs, usernames and above all passwords on the stack. Will these be reported/uploaded as well ? >>> >> Hi Sven, >> >> you are right, I stressed the idea when I first presented ShoreLine Reporter to the mailing list but it is important to be clear: We do not collect any kind of sensitive data. The stack trace we collect is in text in the format ClassName>>methodSignature:, to be sure that we exclude any parameter, password or repository. >> >> In addition to the stack trace, we collect the author name, the date and the pharo version, to cluster the data and have an idea of the evolution of the system during time. >> > > We should add this explanation to the tool itselfâ¦ > > Marcus Yes, and maybe also show the actual stack trace and other info that will be sent in dialog so that the user can see precisely what gets shared.

Dec. 8, 2014

Re: [Pharo-users] [Esug-list] [ann] gtspotter: a moldable interface for spotting objects

by Johan Fabry

OK now I get it â¦ thanks for clarifying! I think my confusion stems from the use of âcategory' and then talking about 'the collection objectâ, which made me think about collections and source code and protocols and packages and I got lost. I think that the sentence of the blog would be clearer like this (uppercase to show changes): To do this, GTSpotter offers an extra action: diving in a RESULTS category. Pressing Cmd+Shift+ArrowRight dives in the collection OF RESULTS OF that category. Thus, we can continue refining the search inside the category. So then, my suggestion for a legend at the bottom of the results list would be: Cmd+Shift+ArrowUp/ArrowDown = Next/Prev category, Cmd+RightArrow = Dive into Result, Cmd+Shift+RightArrow = Dive into Category > On Dec 8, 2014, at 12:48, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Ok. Let's take it step by step and see if we cannot find a better way of explaining. > > Take a look at the first picture in the blog post. Entering GTSpo shows results both for Classes and for Packages. These "Classes" and "Packages" are what we call search categories, and they have associated a query processor that can populate them with results (see the "Spotting your objects" section from the bottom of the post). > > In our case, we get 39 classes (of which only 5 are shown) and 1 package that match the query. If you want to look at all those 39 classes, you can dive in the whole collection behind the category in a separate step. This is achieved through Cmd+Shift+ArrowRight. Does it make more sense now? > > I did not consider the category to be confusing. Would you propose another name? > > Cheers, > Doru > > > On Mon, Dec 8, 2014 at 4:02 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Sorry, but no :-( > > I am always confused when people say âcategoryâ because the word has so many overloaded meanings. The same happens in the blog post, it is not clear to me what category means here, and what does it have to do with the collection object? > > > On Dec 7, 2014, at 11:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > Yes, we will still evolve the UI. At the very least you will get the shortkeys directly on the actions. > > > > The answer to your question is in the blog post: > > GTSpotter offers an extra action: diving in a category. Pressing Cmd+Shift+ArrowRight dives in the collection object containing only the items from that category. Thus, we can continue refining the search inside the category. > > > > So, you will open the collection of that sub-category and you will see more items at once (not just 5). Is it clearer now? > > > > Cheers, > > Doru > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Dec. 8, 2014

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

by Marcus Denker

> On 08 Dec 2014, at 16:34, Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com> wrote: > > > On 08/12/14 14:47, Sven Van Caekenberghe wrote: >> Hi Tommaso, >> >> I think this is a cool initiative, many environments have something similar, so this is a welcome addition. >> >> However, you must be clearer about the security implications (and/or tell us how these concerns are dealt with in other places). Say I execute: >> >> ZnEasy >> get: 'http://zn.stfx.eu/nuclear-launch-codes.txt' >> username: 'barak.obama(a)whitehouse.gov' >> password: 'michele'. >> >> This will leave sensitive hosts, ports, URIs, usernames and above all passwords on the stack. Will these be reported/uploaded as well ? >> > Hi Sven, > > you are right, I stressed the idea when I first presented ShoreLine Reporter to the mailing list but it is important to be clear: We do not collect any kind of sensitive data. The stack trace we collect is in text in the format ClassName>>methodSignature:, to be sure that we exclude any parameter, password or repository. > > In addition to the stack trace, we collect the author name, the date and the pharo version, to cluster the data and have an idea of the evolution of the system during time. > We should add this explanation to the tool itselfâ¦ Marcus

Dec. 8, 2014

STON - new release?

by Usman Bhatti

Hi Sven, I have used STON to serialize some of my objects and it is really simple and cool to work with STON. For my project, I loaded the stable version. When I tried to customize the names of my classes for serialization using stonName, I got errors of MetaClass DNU. I saw that you already fixed this problem a few months back. I loaded recent changes and the problem was resolved. I would like to load a newer version of STON with this bug fix. Do you plan to update ConfigOf with a latest release because I would like to avoid loading a baseline? thanks. usman

Dec. 8, 2014

Re: [Pharo-users] [Esug-list] [ann] gtspotter: a moldable interface for spotting objects

by Tudor Girba

Hi, Ok. Let's take it step by step and see if we cannot find a better way of explaining. Take a look at the first picture in the blog post. Entering GTSpo shows results both for Classes and for Packages. These "Classes" and "Packages" are what we call search categories, and they have associated a query processor that can populate them with results (see the "Spotting your objects" section from the bottom of the post). In our case, we get 39 classes (of which only 5 are shown) and 1 package that match the query. If you want to look at all those 39 classes, you can dive in the whole collection behind the category in a separate step. This is achieved through Cmd+Shift+ArrowRight. Does it make more sense now? I did not consider the category to be confusing. Would you propose another name? Cheers, Doru On Mon, Dec 8, 2014 at 4:02 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Sorry, but no :-( > > I am always confused when people say âcategoryâ because the word has so > many overloaded meanings. The same happens in the blog post, it is not > clear to me what category means here, and what does it have to do with the > collection object? > > > On Dec 7, 2014, at 11:16, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > Yes, we will still evolve the UI. At the very least you will get the > shortkeys directly on the actions. > > > > The answer to your question is in the blog post: > > GTSpotter offers an extra action: diving in a category. Pressing > Cmd+Shift+ArrowRight dives in the collection object containing only the > items from that category. Thus, we can continue refining the search inside > the category. > > > > So, you will open the collection of that sub-category and you will see > more items at once (not just 5). Is it clearer now? > > > > Cheers, > > Doru > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 8, 2014

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

by Tommaso Dal Sasso

On 08/12/14 14:47, Sven Van Caekenberghe wrote: > Hi Tommaso, > > I think this is a cool initiative, many environments have something similar, so this is a welcome addition. > > However, you must be clearer about the security implications (and/or tell us how these concerns are dealt with in other places). Say I execute: > > ZnEasy > get: 'http://zn.stfx.eu/nuclear-launch-codes.txt' > username: 'barak.obama(a)whitehouse.gov' > password: 'michele'. > > This will leave sensitive hosts, ports, URIs, usernames and above all passwords on the stack. Will these be reported/uploaded as well ? > Hi Sven, you are right, I stressed the idea when I first presented ShoreLine Reporter to the mailing list but it is important to be clear: We do not collect any kind of sensitive data. The stack trace we collect is in text in the format ClassName>>methodSignature:, to be sure that we exclude any parameter, password or repository. In addition to the stack trace, we collect the author name, the date and the pharo version, to cluster the data and have an idea of the evolution of the system during time. I hope it is clear enough, thanks for your question! Tommaso

Dec. 8, 2014