June 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Debugger Button Positioning

by Eliot Miranda

Hi Henrik, On Thu, Jun 14, 2018 at 12:47 PM, Henrik-Nergaard <draagren(a)outlook.com> wrote: > Hi, > > Moving the icons down to the middle row is as simple as changing: > > *** > codeActionsPragmas > ^ #( stackDebuggingActions codeDebuggingActions ) > *** > *** > stackDebuggingActionsPragmas > ^ #() > *** > > in GTGenericStackDebugger. > > Best regards, > Henrik > Thanks. I have to say that the renaming from #stackDebuggingActions to gtStackDebuggingAction, as in StepIntoDebugAction class>>gtStackDebuggingActionFor: aDebugger <gtStackDebuggingAction> is a cruel joke. The whole point about pragmas is that they're supposed to be messages, and hence senders (and if possible, implementors) work. But with the mangling that occurs here, a simple senders of stackDebuggingActions brings nothing, and one is left manually searching the system before one finds references to gtStackDebuggingAction. Obscure and hence horrible. _,,,^..^,,,_ best, Eliot "I designed pragmas to be useful and natural, not painful and obscure" Miranda

June 14, 2018

Re: [Pharo-dev] Debugger Button Positioning

by Ben Coman

On 15 June 2018 at 06:51, Ben Coman <btc(a)openinworld.com> wrote: > > > On 15 June 2018 at 03:47, Henrik-Nergaard <draagren(a)outlook.com> wrote: > >> Hi, >> >> Moving the icons down to the middle row is as simple as changing: >> >> *** >> codeActionsPragmas >> ^ #( stackDebuggingActions codeDebuggingActions ) >> > > Thanks for the tip. Note this needs to be stackDebuggingAction > > > cheers -ben > > Anyone know how to do an experiment duplicating the debugging buttons vertically to the left of the code pane, but only the small icon, no text ? cheers -ben

June 14, 2018

strange debugging

by Ben Coman

Not sure if this is intended behaviour... in a brand new build 71053, open a browser GTGenericStackDebuggerTest >> testBasic right-click and choose "Debug" the debugger opens about on the third statement. Clicking <Restart> doesn't improve things, and then clicking <Into> shows the stack on MetaLink>>uninstall. cheers -ben

June 14, 2018

Re: [Pharo-dev] Debugger Button Positioning

by Ben Coman

On 15 June 2018 at 03:47, Henrik-Nergaard <draagren(a)outlook.com> wrote: > Hi, > > Moving the icons down to the middle row is as simple as changing: > > *** > codeActionsPragmas > ^ #( stackDebuggingActions codeDebuggingActions ) > Thanks for the tip. Note this needs to be stackDebuggingAction cheers -ben

June 14, 2018

[Pharo 7.0-dev] Build #1059: 22154 Categorize Ombu Manifest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1059 was: SUCCESS. The Pull Request #1554 was integrated: "22154 Categorize Ombu Manifest" Pull request url: https://github.com/pharo-project/pharo/pull/1554 Issue Url: https://pharo.fogbugz.com/f/cases/22154 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 14, 2018

Re: [Pharo-dev] Debugger Button Positioning

by Henrik-Nergaard

Hi, Moving the icons down to the middle row is as simple as changing: *** codeActionsPragmas ^ #( stackDebuggingActions codeDebuggingActions ) *** *** stackDebuggingActionsPragmas ^ #() *** in GTGenericStackDebugger. Best regards, Henrik -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 14, 2018

Re: [Pharo-dev] Debugger Button Positioning

by Cyril Ferlicot D.

Le 14/06/2018 Ã 20:13, Eliot Miranda a Ã©critÂ : > Hi All, > Hi, > Â Â Â I've been using Pharo intensively for the first time, Pharo 7. > Forgive me for starting with a complaint, but I don't have time to state > all the things that are great about it; you already now ;-) > No problem. It's always easier to talk about the bad things than to good ones. :) I hope you will like your usage of Pharo. > One thing I find painful is the positioning of the debugger > into/over/through buttons.Â Because these are above the context list, > and you read the code like I do, one has to mouse further to reach > them.Â I find my focus is on the highlighted method, and my cursor is > typically within it (I'm dong implementors, or senders, or just looking > at the code).Â Further, there's lots of space between the Source tab and > the "Where Is?" and "Browse" buttons.Â Doesn't it make more sense to put > the into/over/through buttons between the Source tab and the "Where Is?" > button?Â If not, doesn't it make sense to put a copy of the buttons > there where they're in much easier reach? > It was raised many times before but apparently it was not easy to change. Peter did some scripts to change it and I currently use them. The code can be found here: https://github.com/jecisc/pharo-scripts/tree/master/settings/PharoSettings5… There are some extensions to the debugger and to replace the current behaviour of the debugger I use Metalinks (https://github.com/jecisc/pharo-scripts/blob/master/settings/PharoSettings5…) If we can have a way to get it directly into the debugger it would be great. :) > _,,,^..^,,,_ > best,Â Eliot -- Cyril Ferlicot https://ferlicot.fr

June 14, 2018

Re: [Pharo-dev] Debugger Button Positioning

by Esteban A. Maringolo

On 14/06/2018 15:13, Eliot Miranda wrote: > Hi All, > > Â Â Â I've been using Pharo intensively for the first time, Pharo 7. > Forgive me for starting with a complaint, but I don't have time to state > all the things that are great about it; you already now ;-) > > One thing I find painful is the positioning of the debugger > into/over/through buttons.Â Because these are above the context list, > and you read the code like I do, one has to mouse further to reach > them.Â I find my focus is on the highlighted method, and my cursor is > typically within it (I'm dong implementors, or senders, or just looking > at the code).Â Further, there's lots of space between the Source tab and > the "Where Is?" and "Browse" buttons.Â Doesn't it make more sense to put > the into/over/through buttons between the Source tab and the "Where Is?" > button?Â If not, doesn't it make sense to put a copy of the buttons > there where they're in much easier reach? I agree with you in all your remarks, and IMO not only the buttons position is suboptimal, also their shortcuts. But AFAIR this was discussed some time ago when the GTDebugger was set as the default debugger. But the discussion was settled to "you can create your own". Which I don't like, but it's fair enough. :) Regards! -- Esteban A. Maringolo

June 14, 2018

Debugger Button Positioning

by Eliot Miranda

Hi All, I've been using Pharo intensively for the first time, Pharo 7. Forgive me for starting with a complaint, but I don't have time to state all the things that are great about it; you already now ;-) One thing I find painful is the positioning of the debugger into/over/through buttons. Because these are above the context list, and you read the code like I do, one has to mouse further to reach them. I find my focus is on the highlighted method, and my cursor is typically within it (I'm dong implementors, or senders, or just looking at the code). Further, there's lots of space between the Source tab and the "Where Is?" and "Browse" buttons. Doesn't it make more sense to put the into/over/through buttons between the Source tab and the "Where Is?" button? If not, doesn't it make sense to put a copy of the buttons there where they're in much easier reach? _,,,^..^,,,_ best, Eliot

June 14, 2018

[Pharo 7.0-dev] Build #1058: 21987-Stdio-file-creation-should-be-able-to-be-deactivated

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1058 was: SUCCESS. The Pull Request #1432 was integrated: "21987-Stdio-file-creation-should-be-able-to-be-deactivated" Pull request url: https://github.com/pharo-project/pharo/pull/1432 Issue Url: https://pharo.fogbugz.com/f/cases/21987 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 14, 2018