December 2014 - Pharo-users

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

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

by Johan Fabry

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

Dec. 8, 2014

[ANN] RProjectConnector V1.0

by Blondeau Vincent

Hello everyone, I am glad to announce the first version of the RProjectConnector, a binding between Pharo and R using NativeBoost. You can now call directly your R methods from Pharo: data := (1 to: 1000) collect: #yourself. res := (#acf asRFunctionWith: {data}) eval To use it, you should copy the R libraries near the Pharo VM (see the documentation on SmalltalkHub to see how to proceed) and Gofer it smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector'; configuration; loadStable Don't forget to relaunch Pharo after the installation to be able to use the connector. The sources are available on Smalltalkhub: http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector if you want to participate, just ask me! Cheers, Vincent BLONDEAU ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Dec. 8, 2014

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

by Sven Van Caekenberghe

Hi Tommaso, > On 08 Dec 2014, at 14:27, Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com> wrote: > > Hello everybody, > > I am excited to announce that ShoreLine Reporter is now part of Pharo 4. > ShoreLine Reporter is a tool to detect and report errors in Pharo: whenever a user encounters an exception, she can select the "Report" option from the Pre Debug Window and send a stack trace to the ShoreLine server. > > We are using the collected data to identify bugs in the system faster. We are also building a set of tools that the community can use to visualize the information from Pharo exceptions. More on that soon ;-) > > If you want to help the Pharo development just press the "Report" button to submit your exceptions. You can also decide to submit every exception without being bothered by selecting the "always submit" checkbox. > > We do not want to intrude your privacy: this option is opt-in and does not send any data without your explicit consensus. Also, we are working to introduce the possibility to filter the stack trace data that involves proprietary code, and include only information regarding the core system. 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 ? Sven > Any question or suggestion to improve the tool is more than welcome. > > Stay tuned and have fun! > Tommaso >

Dec. 8, 2014

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

by Tudor Girba

This is really great news! Thanks a lot for doing that. I see this as the first step in a completely new direction for Pharo. Cheers, Doru On Mon, Dec 8, 2014 at 2:27 PM, Tommaso Dal Sasso < tommaso.dalsasso(a)gmail.com> wrote: > Hello everybody, > > I am excited to announce that ShoreLine Reporter is now part of Pharo 4. > ShoreLine Reporter is a tool to detect and report errors in Pharo: > whenever a user encounters an exception, she can select the "Report" option > from the Pre Debug Window and send a stack trace to the ShoreLine server. > > We are using the collected data to identify bugs in the system faster. We > are also building a set of tools that the community can use to visualize > the information from Pharo exceptions. More on that soon ;-) > > If you want to help the Pharo development just press the "Report" button > to submit your exceptions. You can also decide to submit every exception > without being bothered by selecting the "always submit" checkbox. > > We do not want to intrude your privacy: this option is opt-in and does not > send any data without your explicit consensus. Also, we are working to > introduce the possibility to filter the stack trace data that involves > proprietary code, and include only information regarding the core system. > > Any question or suggestion to improve the tool is more than welcome. > > Stay tuned and have fun! > Tommaso > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 8, 2014

ShoreLine Reporter is in Pharo 4

by Tommaso Dal Sasso

Hello everybody, I am excited to announce that ShoreLine Reporter is now part of Pharo 4. ShoreLine Reporter is a tool to detect and report errors in Pharo: whenever a user encounters an exception, she can select the "Report" option from the Pre Debug Window and send a stack trace to the ShoreLine server. We are using the collected data to identify bugs in the system faster. We are also building a set of tools that the community can use to visualize the information from Pharo exceptions. More on that soon ;-) If you want to help the Pharo development just press the "Report" button to submit your exceptions. You can also decide to submit every exception without being bothered by selecting the "always submit" checkbox. We do not want to intrude your privacy: this option is opt-in and does not send any data without your explicit consensus. Also, we are working to introduce the possibility to filter the stack trace data that involves proprietary code, and include only information regarding the core system. Any question or suggestion to improve the tool is more than welcome. Stay tuned and have fun! Tommaso

Dec. 8, 2014