Re: [Pharo-users] One comment to new Pharo5 debugger

That looks really great ! It solves the practical problem and, for me, also addresses the conceptual issues that Doru has. Doru, what do you think of this solution? The buttons are still connected to the stack, they are just below the stack instead of on top. I also don’t see why a ‘Stack’ lab

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi Doru, I think most people understand the great value of moldable tools. Maybe not all will use moldability but is a big plus to have. So, keep pushing! I just think we miss time to make the GT Debugger dealt view as productive as the spec debugger. There are users that do not use shortcuts

Re: [Pharo-users] One comment to new Pharo5 debugger

On Jun 4, 2016 14:11, "Ben Coman" wrote: > >> >> >> On Sat, Jun 4, 2016 at 11:28 PM, Gabriel Cotelli >> wrote: >> >>> Hi, >>> I undestand and really liked the idea of a moldable debugger and it's >>> true that the button actions act over the stack, however the decision on >>> what action to use i

Re: [Pharo-users] One comment to new Pharo5 debugger

On Sun, Jun 5, 2016 at 1:17 AM, Tudor Girba wrote: > Hi, > >> On Jun 4, 2016, at 7:09 PM, Ben Coman wrote: >> >> >> >> On Sat, Jun 4, 2016 at 11:28 PM, Gabriel Cotelli wrote: >> Hi, >> I undestand and really liked the idea of a moldable debugger and it's true >> that the button actions act over

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi, > On Jun 4, 2016, at 7:09 PM, Ben Coman wrote: > > > > On Sat, Jun 4, 2016 at 11:28 PM, Gabriel Cotelli wrote: > Hi, > I undestand and really liked the idea of a moldable debugger and it's true > that the button actions act over the stack, however the decision on what > action to use is

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi, > On Jun 4, 2016, at 12:18 PM, Sabine Manaa wrote: > > Hi Tudor, > > thank you for the explanation, which explains the situation. > > Speaking only for me: I never used custom debuggers, I always used the > default debugger in different smalltalk IDEs and so, I am used to a kind of > "s

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi, > On 04 Jun 2016, at 12:18, Sabine Manaa wrote: > > Hi Tudor, > > thank you for the explanation, which explains the situation. > > Speaking only for me: I never used custom debuggers, I always used the > default debugger in different smalltalk IDEs and so, one could say you never used

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi Tudor, thank you for the explanation, which explains the situation. Speaking only for me: I never used custom debuggers, I always used the default debugger in different smalltalk IDEs and so, I am used to a kind of "standard". But as your signature points out "Every thing should have the right

Re: [Pharo-users] One comment to new Pharo5 debugger

On Thu, May 26, 2016 at 9:59 PM, Esteban Lorenzano wrote: > > On 26 May 2016, at 14:49, Johan Fabry wrote: > > Yes, and there was also some discussion on the Pharo-users mailing list. > Apparently the same comments more or less ... > > I give a big +1 on moving the buttons down, so that they are

Re: [Pharo-users] One comment to new Pharo5 debugger

I think the reason not to change, is not a difficulty in implementation but a design view that is different from yours and mine. And from Sabine’s. And from Stef’s. And maybe from other persons too … Just to say that I think this should have been discussed more. -- Does this mail seem too bri

Re: [Pharo-users] One comment to new Pharo5 debugger

Johan, thank you, this works fine! regards Sabine 2016-05-27 2:33 GMT+02:00 jfabry [via Smalltalk] < ml-node+s1294792n4897659...@n4.nabble.com>: > > I will just leave this here, so that people that prefer the buttons in > their original place can get them back ... > > I did some quick investigati

Re: [Pharo-users] One comment to new Pharo5 debugger

2016-05-27 2:08 GMT+02:00 Johan Fabry : > codeActionsPragmas > > ^ #( codeDebuggingAction stackDebuggingAction ) > I am wondering. Why people from GT team not do this? I was think it not easy. Anyway change following method to remove buttons from top pane: "protocol: building actions" stackDebu

Re: [Pharo-users] One comment to new Pharo5 debugger

I will just leave this here, so that people that prefer the buttons in their original place can get them back ... I did some quick investigating, and it’s straightforward. Just change the implementation of GTGenericStackDebugger>>codeActionsPragmas to the following: codeActionsPragmas

Re: [Pharo-users] One comment to new Pharo5 debugger

Yes, and there was also some discussion on the Pharo-users mailing list. Apparently the same comments more or less ... I give a big +1 on moving the buttons down, so that they are between the stack and the code pane. I still don’t understand why they need to be so far away from the code pane

Re: [Pharo-users] One comment to new Pharo5 debugger

> On 26 May 2016, at 14:49, Johan Fabry wrote: > > Yes, and there was also some discussion on the Pharo-users mailing list. > Apparently the same comments more or less ... > > I give a big +1 on moving the buttons down, so that they are between the > stack and the code pane. I still don’t und

Re: [Pharo-users] One comment to new Pharo5 debugger

Yes, and there was also some discussion on the Pharo-users mailing list. Apparently the same comments more or less ... I give a big +1 on moving the buttons down, so that they are between the stack and the code pane. I still don’t understand why they need to be so far away from the code pane, i

Re: [Pharo-users] One comment to new Pharo5 debugger

Thanks Sabine! This is important that you report such problems. Several people including me already reported this problem that we will have to address for real. Stef Le 25/5/16 à 21:43, Sabine Manaa a écrit : Hi, today I moved to Pharo5. It is great to get feedback and solutions for probl

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi. Maybe me should give chance to standard Moose debugger view? (where stack pane on the left) 2016-05-26 9:37 GMT+02:00 Christophe Demarey : > Hi Sabine, > > this point was also « discussed » (no answer) here: > http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html > Yes, the n

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi Peter, Thanks. I geht all the nabble mails and try to read at least the subject but I missed this one. I create my own shortcuts as first solution. Regards Sabine Am Mittwoch, 25. Mai 2016 schrieb Peter Uhnák [via Smalltalk] : > Hi, > > yes, this question was raised before, but there are so

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi Sabine, this point was also « discussed » (no answer) here: http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html Yes, the new buttons are counter-productive and there is even no setting to have them usab

Re: [Pharo-users] One comment to new Pharo5 debugger

Hi, yes, this question was raised before, but there are some disagreements over how it should be, so it may take some time http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html You can also use a startup script to reassign them, such as this one. https://github.com/peteruhnak/pharo-

[Pharo-users] One comment to new Pharo5 debugger

Hi, today I moved to Pharo5. It is great to get feedback and solutions for problems so quickly. It is a pleasure to work with Pharo and to have the community. I am grateful for having this. I have one comment. I don't want to complain, I can use it but I was wondering about the new position and