Hi

I'm FEDUP to have to go up to click on buttons in the debugger.

I know that some of you have a preferences to fix this problem (yes doru
nicely explain that we do not understand anything

and this is part of design but I do not care of design I care about my
efficiency - as if Apple wuld not break their design rules in any
version of iTunes).

And I would like to use such preferences.


Stef

Hi

I'm FEDUP to have to go up to click on buttons in the debugger.

I know that some of you have a preferences to fix this problem (yes doru nicely explain that we do not understand anything

and this is part of design but I do not care of design I care about my efficiency - as if Apple wuld not break their design rules in any version of iTunes).

And I would like to use such preferences.


Stef

Hi Stef,

I never explained anyone how they do not understand something :). When I try to explain something, I mostly try to explain how I reason and the kinds of constraints I considered so that others can find what is wrong.

Related to your issue, there is no preference currently. Interestingly, others have asked for changes for a different layout of the default debugger. So, we should have a way to allow people to enable/disable debuggers (similar to how it is for Spotter extensions) and we could then allow people to choose between different formats for the default debugger.

I stress “default" because there are others, and this is what my previous mail actually described (and not breaking the design rules). I did not get a reply to that mail, so I thought that the description was meaningful enough. It looks like it was not.

I opened an issue for this:
https://pharo.fogbugz.com/f/cases/18882/GTDebugger-should-offer-enable-disable-mechanisms-for-extension-debuggers

Cheers,
Doru



--
www.tudorgirba.com
www.feenk.com

"Value is always contextual."

On Sun, Aug 07, 2016 at 09:42:07AM +0200, stepharo wrote:
I am not sure if this is what you are looking for, but I have a startup script that changes the shortcuts to be (on Linux) always ctrl+shift+<first letter of the command>

(And it underlines the letter too.)

https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformDebugger.st

(original thread: http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html )

Peter

Some positiveness,

One think I like very much with the new GTDebugger: the meaning of each
button action from its label is very clear and I am pretty sure beginner
with Pharo will understand easily the use of each one.

Regarding productivity, why not using the shortcut described in each
button tooltips (the tooltips will deserve a better text than just the
repeating of the label, but it is nice there is the shortcut mentioned)

Hilaire

Le 07/08/2016 à 22:30, Tudor Girba a écrit :
--
Dr. Geo
http://drgeo.eu

On 8/7/16 6:06 PM, Hilaire wrote:
> Regarding productivity, why not using the shortcut described in each
> button tooltips (the tooltips will deserve a better text than just the
> repeating of the label, but it is nice there is the shortcut mentioned)
>
I didn't realize that there were tooltips for those buttons ... there
appears to be a bit of a delay for them to come up (on my machine) and
not all of the buttons have tool tips (into, over and through) and a) I
don't know how long I am supposed to wait for a tool tip to NOT show up
and b) no matter how long I wait, over doesn't appear to have a tool tip
(the into and through tooltips are very hard to bring up ... if I am
very stubborn, I can get them to come up but I'm not sure where the
magic spot is) ...

... I have to move the mouse up out of the button and then back down
into the next button to see tool tips ... if you slide the mouse from
button to button laterally, the tool tip never shows up ...

and finally oh yeah ... 2 of shortcuts are without a SHIFT and 3 of them
require a SHIFT and into/over/through are unshifted/shifted/shifted
which means that I have to contort my hand to use them --- something
that I believe has been discussed before ---

The way I work, if I have my hand on the mouse I will try to use the
mouse if my hand is on the keyboard I will prefer to use the keyboard
... because of screen real estate issues with the browser windows
(discussed before) I end up having to have my hands on the mouse just to
see what I want to see ... so telling me that the keyboard shortcuts are
more productive is not necessarily a true statement ...

BTW, if I didn't love Smalltalk and Pharo, I wouldn't be chiming in here
... all of my criticisms are intended to be constructive ...

Since lack of feedback is construed to mean "love it", I've decided to
let you know about the things that annoy me and hopefully I am providing
enough information to give you a feel for what I think it is that
actually annoys me :)

Dale

Le 08/08/2016 à 09:44, Dale Henrichs a écrit :
Yes, the tooltips in the debugger are boggus! I try to look in other
part of Pharo for same unconsistant behavior, and it seems not present.


> and finally oh yeah ... 2 of shortcuts are without a SHIFT and 3 of them
> require a SHIFT and into/over/through are unshifted/shifted/shifted
> which means that I have to contort my hand to use them --- something
> that I believe has been discussed before ---


Yeah, I though a bit the same. This mix of Ctrl and Ctrl+shift is very
unfortunate in the debugger.


Hilaire

--
Dr. Geo
http://drgeo.eu

Hi,

There is an open issue for this:
https://pharo.fogbugz.com/f/cases/18020/Shortcut-keys-in-GTDebugger-should-be-user-assignable

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"When people care, great things can happen."