- Pharo-users - lists.pharo.org

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

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

by Tudor Girba

Hi Christophe, On Mon, Dec 8, 2014 at 10:43 AM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > Hi Doru and all, > > Great work. All these tools are really moving the development experience a > step forward :) > I will try it ASAP. > At this time, I just wonder if it is possible to search text in method > sources. It is often useful. > It's not done now, but you can just add it. It should probably take you a couple of minutes :). Just try to follow the instructions from the end of the post and let us know how it goes. > Another related thing I don't know how to do, is to refactor a set of > methods (could be some methods to 20 or more). In these methods, I send a > specific message. Now, I just want to remove the message implementation (it > is not a rename) and I have to update the code accordingly. Sometimes, I > could do that by just a search/replace (text) functionality (would be cool > to use patterns there) in methods source code but I cannot find a way do > that for now. So I do it by hand. > I wonder if it already exists a way to do that or if GTSpotter could > address this issue. > I think this is out of the direct realm of GTSpotter. But, it would be an interesting area nevertheless. We would likely be able to benefit from combining somehow RB rules with spotter. Cheers, Doru > Christophe. > > Le 7 dÃ©c. 2014 Ã 14:14, Tudor Girba a Ã©crit : > > Hi, > > Alex Syrel, Andrei Chis and I are happy to announce a new addition to the > Glamorous Toolkit: > GTSpotter, a novel interface for spotting objects. > > GTSpotter has two goals: > - Provide a uniform yet moldable interface that can work on any object, and > - Handle searching through arbitrary levels of object nesting. > > We think this will have a significant impact on the development workflow > in Pharo. > > Here is a couple of screenshots: > <gtspotter-packages-classes.png> <gtspotter-dive-class-method-sender.png> > <gtspotter-playground.png> > > > A trailer is available here: > https://www.youtube.com/watch?v=PhSmjR3NOlU > > A detailed description is available here: > http://www.humane-assessment.com/blog/introducing-gtspotter > > It works already in Pharo 3.0 and can be played with by following the > instructions from: > http://gt.moosetechnology.org > > Please let us know what you think. > > Enjoy, > The Glamorous Team > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 8, 2014

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

by Christophe Demarey

Hi Doru and all, Great work. All these tools are really moving the development experience a step forward :) I will try it ASAP. At this time, I just wonder if it is possible to search text in method sources. It is often useful. Another related thing I don't know how to do, is to refactor a set of methods (could be some methods to 20 or more). In these methods, I send a specific message. Now, I just want to remove the message implementation (it is not a rename) and I have to update the code accordingly. Sometimes, I could do that by just a search/replace (text) functionality (would be cool to use patterns there) in methods source code but I cannot find a way do that for now. So I do it by hand. I wonder if it already exists a way to do that or if GTSpotter could address this issue. Christophe. Le 7 dÃ©c. 2014 Ã 14:14, Tudor Girba a Ã©crit : > Hi, > > Alex Syrel, Andrei Chis and I are happy to announce a new addition to the Glamorous Toolkit: > GTSpotter, a novel interface for spotting objects. > > GTSpotter has two goals: > - Provide a uniform yet moldable interface that can work on any object, and > - Handle searching through arbitrary levels of object nesting. > > We think this will have a significant impact on the development workflow in Pharo. > > Here is a couple of screenshots: > <gtspotter-packages-classes.png> <gtspotter-dive-class-method-sender.png> <gtspotter-playground.png> > > > A trailer is available here: > https://www.youtube.com/watch?v=PhSmjR3NOlU > > A detailed description is available here: > http://www.humane-assessment.com/blog/introducing-gtspotter > > It works already in Pharo 3.0 and can be played with by following the instructions from: > http://gt.moosetechnology.org > > Please let us know what you think. > > Enjoy, > The Glamorous Team

Dec. 8, 2014

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

by Tudor Girba

I am happy you found the problem. Please continue asking questions. Cheers, Doru On Mon, Dec 8, 2014 at 10:33 AM, Edward Povazan <empovazan(a)gmail.com> wrote: > I found the problem. I forgot a simple fact - with Smalltalk I have access > to all the code! Anyways, I discovered that I had somehow zapped > Moose/HashTable (no idea how) and so in the layout code "HashTable newâ was > raising the exception, sending ânewâ to UndefinedObject. Makes sense to me > now. > > Thanks for all the help, it resulted in me poking around more when I > suddenly realized I could. > -Ed > > > On Dec 7, 2014, at 4:58 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Could you make the image available? > > Cheers, > Doru > > > > On Sun, Dec 7, 2014 at 1:03 PM, Edward Povazan <empovazan(a)gmail.com> > wrote: > >> Thank you, >> >> For some reason there were a few. Reverted most. However all my Petit* >> ones trigger the same error when reloading them. I deleted them. But the >> error persists, as soon as I try open a Workspace I get the Emergency >> Evaluator screen. >> >> -Ed >> >> On Dec 7, 2014, at 12:21 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> If I understand correctly, you are on Pharo 3. What I suggest is to open >> the Monticello Browser and look at the changed packages. Then you can load >> the previous versions of those, and you should get back to normal. >> >> Cheers, >> Doru >> >> >> >> On Sun, Dec 7, 2014 at 6:08 AM, Edward Povazan <empovazan(a)gmail.com> >> wrote: >> >>> Hello, >>> >>> Iâve been using Pharo for a while as my playground for trying things >>> out, itâs a very soothing place to code and figure out algorithms (except >>> that when I return to my âreal worldâ, the friction with modern tools is >>> amplified). Iâm still a newb when it comes to knowing how things work >>> deeper down. >>> >>> Iâm a little stuck. I did something (canât remember) and not realizing >>> that I had a problem, saved my image too. >>> Now when I try open a Workspace, I get a *** System error handling >>> failed *** with a huge amount of text. >>> >>> Iâve uploaded a screen grab here: http://imgur.com/4ZwsF6e >>> >>> Is this worth debugging? >>> >>> My plan is to install the origin tools, and remove GToolkit. And then >>> reinstall GToolkit. >>> Would this help? >>> >>> And, how? I realize I donât know what tools are in the default Pharo3 >>> image! >>> Can someone tell me what they are called? >>> >>> Thanks! Canât wait to get back to the happy place! >>> -Ed >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 8, 2014

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

by Edward Povazan

I found the problem. I forgot a simple fact - with Smalltalk I have access to all the code! Anyways, I discovered that I had somehow zapped Moose/HashTable (no idea how) and so in the layout code "HashTable newâ was raising the exception, sending ânewâ to UndefinedObject. Makes sense to me now. Thanks for all the help, it resulted in me poking around more when I suddenly realized I could. -Ed On Dec 7, 2014, at 4:58 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Could you make the image available? > > Cheers, > Doru > > > > On Sun, Dec 7, 2014 at 1:03 PM, Edward Povazan <empovazan(a)gmail.com> wrote: > Thank you, > > For some reason there were a few. Reverted most. However all my Petit* ones trigger the same error when reloading them. I deleted them. But the error persists, as soon as I try open a Workspace I get the Emergency Evaluator screen. > > -Ed > > On Dec 7, 2014, at 12:21 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> If I understand correctly, you are on Pharo 3. What I suggest is to open the Monticello Browser and look at the changed packages. Then you can load the previous versions of those, and you should get back to normal. >> >> Cheers, >> Doru >> >> >> >> On Sun, Dec 7, 2014 at 6:08 AM, Edward Povazan <empovazan(a)gmail.com> wrote: >> Hello, >> >> Iâve been using Pharo for a while as my playground for trying things out, itâs a very soothing place to code and figure out algorithms (except that when I return to my âreal worldâ, the friction with modern tools is amplified). Iâm still a newb when it comes to knowing how things work deeper down. >> >> Iâm a little stuck. I did something (canât remember) and not realizing that I had a problem, saved my image too. >> Now when I try open a Workspace, I get a *** System error handling failed *** with a huge amount of text. >> >> Iâve uploaded a screen grab here: http://imgur.com/4ZwsF6e >> >> Is this worth debugging? >> >> My plan is to install the origin tools, and remove GToolkit. And then reinstall GToolkit. >> Would this help? >> >> And, how? I realize I donât know what tools are in the default Pharo3 image! >> Can someone tell me what they are called? >> >> Thanks! Canât wait to get back to the happy place! >> -Ed >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 8, 2014

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

by Thierry Goubier

2014-12-07 20:21 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > > Hi Thierry, > > What I meant is that no IDE I know allows you to refine search through arbitrary levels of nesting. For example, looking for senders, filter, implementors, filter, senders, filter ... > > > Is the AltBrowser able to do that? If so, I missed this one. It is able to do that. It's very simple: every search you do is answered as a browser instance scoped to the RBEnvironment containing the search results. So, depending on what you search next, it happens in the current scope or in the parent scope, and recursively constrain the scope The finder is integrated into that (i.e. finder searches, any type, are scoped to the RBEnvironment). Refactoring commands are (should be) restricted to that scope. Limitation: RB environments are not dynamic. Thierry

Dec. 8, 2014