October 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ShoreLine Reporter - A tool to collect stack traces

by Tommaso Dal Sasso

Hello, thanks for the feedback! I uploaded the slides here: http://shoreline.inf.usi.ch/files/ESUG2014.pdf (I tried slideshare, but it didm't work...). The video of the presentation is among the ESUG2014 videos, this are the direct links: https://www.youtube.com/watch?v=_PDQGlq4yxw&index=61&list=PLJ5nSnWzQXi_6yyR… https://www.youtube.com/watch?v=GgXdA-bcmyA&index=60&list=PLJ5nSnWzQXi_6yyR… Tommaso On 08/10/14 18:36, Martin Dias wrote: > Tommaso: I also started to load it > > On Wed, Oct 8, 2014 at 6:09 PM, Esteban A. Maringolo > <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> wrote: > > Do you have a link to ESUG's slides/presentation? > > Regards! > Esteban A. Maringolo > > > 2014-10-07 13:23 GMT-03:00 Tommaso Dal Sasso > <tommaso.dalsasso(a)gmail.com <mailto:tommaso.dalsasso@gmail.com>>: > > Hello everybody, > > > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > > > ShoreLine Reporter is a Pharo plugin to collect stack traces > from exceptions > > and send them to a central repository. > > You can give feedback to the community by breaking things: how > cool is that? > > > > > > * Why? > > > > We are collecting stack traces for research purposes and to > identify the > > Pharo components that can be improved or optimized. > > We are also working on a web platform where users can access the > submitted > > data and use them during the debugging process. More on that soon! > > > > > > * How? > > > > You can install ShoreLine Reporter by visiting the project page on > > SmalltalkHub: > > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > <http://www.smalltalkhub.com/#%21/%7Edalsat/ShoreLine-Reporter/> > > > > Installing ShoreLine Reporter requires only a couple of seconds, > and you can > > configure it with the level of feedback that you prefer. On the > SmalltalkHub > > page you can find a script to automatically install ShoreLine > Reporter with > > every new Pharo image. Just drop it in your Pharo preferences > directory and > > forget about it. > > > > Once ShoreLine Report is installed, you can decide to configure > if you want > > to be prompted to submit a stack trace, or to automatically > submit each > > exception without any bother. > > > > > > * What? > > > > We try to collect as few data as possible: the execution > stacktrace, the > > name of the author and the Pharo build. We do *not* any collect > personal > > data, such as passwords or repositories. The data is currently > stored on our > > server, at the University of Lugano. > > > > > > * Compatibility > > > > ShoreLine Reporter is developed for the Pharo debugger. We are > improving > > ShoreLine Reporter to work with GTInspector, we will push an > update in the > > following days. > > > > > > For any problem, contact me! > > > > Thanks, hope to see a lot of your exceptions ;-) > > Tommaso Dal Sasso @ REVEAL > > > >

Oct. 9, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40292 Home: https://github.com/pharo-project/pharo-core

Oct. 9, 2014

[pharo-project/pharo-core] 64869d: 40292

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 64869d4fa7bbbd94f0764df922abd455be02ddfc https://github.com/pharo-project/pharo-core/commit/64869d4fa7bbbd94f0764df9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-09 (Thu, 09 Oct 2014) Changed paths: M AST-Core.package/RBFindBlockArgumentAssignment.class/instance/visiting/visitArgumentNode_.st M AST-Core.package/RBFindBlockArgumentAssignment.class/instance/visiting/visitAssignmentNode_.st M Polymorph-Widgets.package/MorphicUIManager.class/instance/ui requests/edit_label_accept_.st M Polymorph-Widgets.package/MorphicUIManager.class/instance/ui requests/openComparisonFrom_to_belongingTo_from_labeled_inWindowLabeled_.st M Refactoring-Critics.package/RBSmalllintChecker.class/instance/actions/run.st M SUnit-UI.package/TestRunner.class/instance/history saving/showDiffWith_.st M SUnit-UI.package/TestRunner.class/instance/history saving/showProgress.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script292.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40292.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Core.package/MenuModel.class/instance/protocol/addTitle_.st M System-Settings.package/SettingBrowser.class/instance/user interface/helpDeclaringAndManagingSettings.st Log Message: ----------- 40292 14196 Do not use workspace as an editor https://pharo.fogbugz.com/f/cases/14196 14086 RBSmalllintChecker is not applying rules in class-side https://pharo.fogbugz.com/f/cases/14086 14133 UIManager should not overuse the workspace for editing https://pharo.fogbugz.com/f/cases/14133 14195 In the ChangeSorter: DNU when trying to get a menu https://pharo.fogbugz.com/f/cases/14195 14199 RBFindBlockArgumentAssignment is sometimes wrong https://pharo.fogbugz.com/f/cases/14199 http://files.pharo.org/image/40/40292.zip

Oct. 9, 2014

Re: [Pharo-dev] List Method selection could be improved

by phil＠highoctane.be

Pharo3: keep your finger on shift at all times to move multiple things. Christophe Demarey showed it to me as I was complaining. Still, completely unintuitive. Phil On Wed, Oct 8, 2014 at 8:52 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2014-10-08 15:35 GMT-03:00 stepharo <stepharo(a)free.fr>: > > > > Hi > > > > It seems that we got some regressions in the method pane. > > - Sometimes I have the impression that I cannot look for a method just > typing the starting letter > > - When deleting a method it would be good that the next item is > selected. > > > What do you think? > > That it should be modified to behave as you expect, which is a common > pattern of list selection. > > > Plus (in Pharo 3): > - You can't individually select separate elements (methods) by holding > down Ctrl and clicking on them. > - You can select continuous elements using Shift, but once you start > dragging them the one that has the cursor when the drag operation > starts is unselected. (so if you we're going to recategorize 5 > methods, you end up doing it for only 4). > > > I don't know if those are regressions, but they certainly doesn't > follow the most used patterns of element selection. > > > Regards, > > > Esteban A. Maringolo > >

Oct. 8, 2014

Re: [Pharo-dev] List Method selection could be improved

by Esteban A. Maringolo

2014-10-08 15:35 GMT-03:00 stepharo <stepharo(a)free.fr>: > > Hi > > It seems that we got some regressions in the method pane. > - Sometimes I have the impression that I cannot look for a method just typing the starting letter > - When deleting a method it would be good that the next item is selected. > What do you think? That it should be modified to behave as you expect, which is a common pattern of list selection. Plus (in Pharo 3): - You can't individually select separate elements (methods) by holding down Ctrl and clicking on them. - You can select continuous elements using Shift, but once you start dragging them the one that has the cursor when the drag operation starts is unselected. (so if you we're going to recategorize 5 methods, you end up doing it for only 4). I don't know if those are regressions, but they certainly doesn't follow the most used patterns of element selection. Regards, Esteban A. Maringolo

Oct. 8, 2014

List Method selection could be improved

by stepharo

Hi It seems that we got some regressions in the method pane. - Sometimes I have the impression that I cannot look for a method just typing the starting letter - When deleting a method it would be good that the next item is selected. What do you think? Stef

Oct. 8, 2014

Re: [Pharo-dev] BlockClosure source code

by Marcus Denker

> On 08 Oct 2014, at 18:28, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > > On 8 oct. 2014, at 17:49, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > >>> >>> On 08 Oct 2014, at 16:46, Jan KurÅ¡ <kurs(a)iam.unibe.ch <mailto:kurs@iam.unibe.ch>> wrote: >>> >>> Hi, >>> >>> I need to extract a source code from a block closure and I found something strange: >>> >>> [ :ctx | [ ctx atEnd ] ifTrue: [ ] ] . >>> [ :ctx | [ ctx atEnd ] whileTrue:[ ] ]. >>> >>> Print of the first line returns: >>> '[ :ctx | [ ctx atEnd ] ifTrue: [ ] ]' >>> >>> Print of the second line returns: >>> '[ ctx atEnd ]' >>> >>> And honestly, I have no idea why. This behaviour was observed in Pharo3 and Pharo4. >>> >>> Is there a way how to get a consistent result, i.e. '[ :ctx | [ ctx atEnd ] whileTrue:[ ] ]' for a second line? >> >> >> I think this is an example that exposes a bug that we still have in the source mappingâ¦ on Context, see >> >> sourceNode >> "Return the source node of the method or the block corresponding to the receiver" >> ^ (method sourceNodeForPC: self neighborPCWithCorrectMapping) enclosingMethodOrBlockNode >> "Uncomment the following once the pc->AST mapping is fixed" >> "^ (method sourceNodeForPC: (pc ifNil: [ self startpc ])) enclosingMethodOrBlockNode" >> >> #neighborPCWithCorrectMapping returns the inner send, which is wrongâ¦ this method needs to be rethought. > > Yes it should. But that's not easy with optimized loop messages like whileTrue: & co. > Ideally, the source mapping needs to be fixed because that's the reason this method exists in the first place. The first step is to record a range for the byte code that an IRNode createsâ¦ > Or else we accepts that "1 to: 1 do: [ :i | ^ thisContext sourceNode ]" returns a method node instead of a block node and use a different implementation. > >> >> Marcus

Oct. 8, 2014

Re: [Pharo-dev] ShoreLine Reporter - A tool to collect stack traces

by Martin Dias

Tommaso: I also started to load it On Wed, Oct 8, 2014 at 6:09 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Do you have a link to ESUG's slides/presentation? > > Regards! > Esteban A. Maringolo > > > 2014-10-07 13:23 GMT-03:00 Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com>: > > Hello everybody, > > > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > > > ShoreLine Reporter is a Pharo plugin to collect stack traces from > exceptions > > and send them to a central repository. > > You can give feedback to the community by breaking things: how cool is > that? > > > > > > * Why? > > > > We are collecting stack traces for research purposes and to identify the > > Pharo components that can be improved or optimized. > > We are also working on a web platform where users can access the > submitted > > data and use them during the debugging process. More on that soon! > > > > > > * How? > > > > You can install ShoreLine Reporter by visiting the project page on > > SmalltalkHub: > > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > > > > Installing ShoreLine Reporter requires only a couple of seconds, and you > can > > configure it with the level of feedback that you prefer. On the > SmalltalkHub > > page you can find a script to automatically install ShoreLine Reporter > with > > every new Pharo image. Just drop it in your Pharo preferences directory > and > > forget about it. > > > > Once ShoreLine Report is installed, you can decide to configure if you > want > > to be prompted to submit a stack trace, or to automatically submit each > > exception without any bother. > > > > > > * What? > > > > We try to collect as few data as possible: the execution stacktrace, the > > name of the author and the Pharo build. We do *not* any collect personal > > data, such as passwords or repositories. The data is currently stored on > our > > server, at the University of Lugano. > > > > > > * Compatibility > > > > ShoreLine Reporter is developed for the Pharo debugger. We are improving > > ShoreLine Reporter to work with GTInspector, we will push an update in > the > > following days. > > > > > > For any problem, contact me! > > > > Thanks, hope to see a lot of your exceptions ;-) > > Tommaso Dal Sasso @ REVEAL > > > >

Oct. 8, 2014

Re: [Pharo-dev] BlockClosure source code

by Camille Teruel

On 8 oct. 2014, at 17:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On 08 Oct 2014, at 16:46, Jan KurÅ¡ <kurs(a)iam.unibe.ch> wrote: >> >> Hi, >> >> I need to extract a source code from a block closure and I found something strange: >> >> [ :ctx | [ ctx atEnd ] ifTrue: [ ] ] . >> [ :ctx | [ ctx atEnd ] whileTrue:[ ] ]. >> >> Print of the first line returns: >> '[ :ctx | [ ctx atEnd ] ifTrue: [ ] ]' >> >> Print of the second line returns: >> '[ ctx atEnd ]' >> >> And honestly, I have no idea why. This behaviour was observed in Pharo3 and Pharo4. >> >> Is there a way how to get a consistent result, i.e. '[ :ctx | [ ctx atEnd ] whileTrue:[ ] ]' for a second line? > > > I think this is an example that exposes a bug that we still have in the source mappingâ¦ on Context, see > > sourceNode > "Return the source node of the method or the block corresponding to the receiver" > ^ (method sourceNodeForPC: self neighborPCWithCorrectMapping) enclosingMethodOrBlockNode > "Uncomment the following once the pc->AST mapping is fixed" > "^ (method sourceNodeForPC: (pc ifNil: [ self startpc ])) enclosingMethodOrBlockNode" > > #neighborPCWithCorrectMapping returns the inner send, which is wrongâ¦ this method needs to be rethought. Yes it should. But that's not easy with optimized loop messages like whileTrue: & co. Ideally, the source mapping needs to be fixed because that's the reason this method exists in the first place. Or else we accepts that "1 to: 1 do: [ :i | ^ thisContext sourceNode ]" returns a method node instead of a block node and use a different implementation. > > Marcus

Oct. 8, 2014

Re: [Pharo-dev] ShoreLine Reporter - A tool to collect stack traces

by Esteban A. Maringolo

Do you have a link to ESUG's slides/presentation? Regards! Esteban A. Maringolo 2014-10-07 13:23 GMT-03:00 Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com>: > Hello everybody, > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > ShoreLine Reporter is a Pharo plugin to collect stack traces from exceptions > and send them to a central repository. > You can give feedback to the community by breaking things: how cool is that? > > > * Why? > > We are collecting stack traces for research purposes and to identify the > Pharo components that can be improved or optimized. > We are also working on a web platform where users can access the submitted > data and use them during the debugging process. More on that soon! > > > * How? > > You can install ShoreLine Reporter by visiting the project page on > SmalltalkHub: > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > > Installing ShoreLine Reporter requires only a couple of seconds, and you can > configure it with the level of feedback that you prefer. On the SmalltalkHub > page you can find a script to automatically install ShoreLine Reporter with > every new Pharo image. Just drop it in your Pharo preferences directory and > forget about it. > > Once ShoreLine Report is installed, you can decide to configure if you want > to be prompted to submit a stack trace, or to automatically submit each > exception without any bother. > > > * What? > > We try to collect as few data as possible: the execution stacktrace, the > name of the author and the Pharo build. We do *not* any collect personal > data, such as passwords or repositories. The data is currently stored on our > server, at the University of Lugano. > > > * Compatibility > > ShoreLine Reporter is developed for the Pharo debugger. We are improving > ShoreLine Reporter to work with GTInspector, we will push an update in the > following days. > > > For any problem, contact me! > > Thanks, hope to see a lot of your exceptions ;-) > Tommaso Dal Sasso @ REVEAL >

Oct. 8, 2014