[Pharo-dev] [Pharo-users] GTDebugger shortcuts usability

Ben Coman btc at openinworld.com
Sun Apr 17 12:00:45 EDT 2016


Interesting. A search turned up... Quick Tip Debugger Shortcut Key Reference
http://www.mularien.com/blog/category/eclipse/

cheers -ben

On Sun, Apr 17, 2016 at 11:15 PM, philippe.back at highoctane.be
<philippe.back at gmail.com> wrote:
> Most of the world IDE use function keys for debugging.
>
> Additional benefit: easier for newcomers to use it.
>
> Having the buttons on the top is a pain as the code pane is at the bottom
> and requires travels all the time.
>
> Phil
>
> On Apr 17, 2016 4:57 PM, "Peter Uhnák" <i.uhnak at gmail.com> wrote:
>>
>> Well, I've added a startup script for myself... but it would be nice to
>> have it everywhere by default in some variant...
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> StartupPreferencesLoader default executeAtomicItems: {
>> StartupAction
>> name: 'Change debugger labels & shortcuts'
>> code: [
>> GLMMorphicActionRenderer compile: (
>> (GLMMorphicActionRenderer>>#render:) sourceCode
>> copyReplaceAll: 'setBalloonText: (anAction title'
>> with: 'setBalloonText: (anAction title asString'
>> ).
>> RestartDebugAction compile: 'defaultKeyText
>> ^ ''R'''.
>> RestartDebugAction compile: 'defaultLabel
>> ^ ''Restart'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'.
>> ResumeDebugAction compile: 'defaultKeyText
>> ^ ''P'''.
>> ResumeDebugAction compile: 'defaultLabel
>> ^ ''Proceed'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'.
>> StepIntoDebugAction compile: 'defaultKeyText
>> ^ ''I'''.
>> StepIntoDebugAction compile: 'defaultLabel
>> ^ ''Into'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'.
>> StepOverDebugAction compile: 'defaultLabel
>> ^ ''Over'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'.
>> StepThroughDebugAction compile: 'defaultLabel
>> ^ ''Through'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'.
>> ]
>> runOnce: true.
>> }
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>> On Sat, Apr 16, 2016 at 11:39 PM, Peter Uhnák <i.uhnak at gmail.com> wrote:
>>>>
>>>> Let’s turn this energy into something positive. Please propose a
>>>> concrete set of default keybindings that you think would work better. In
>>>> this process, please take into account all keybindings that are already
>>>> defined in the code editor (it might not be so easy as it appears).
>>>
>>>
>>> As I've said:
>>>
>>> 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw)
>>> 2. can we use the default shortcuts pattern where one of the letters is
>>> underlined?
>>>
>>> as for the shortcuts themselves, problem is proceed, restart & into
>>>
>>> proceed: ctrl+shift+p is not taken, so I don't see why it has shortcut
>>> confusing with restart
>>> restart: ctrl+shift+r indents, but I'd argue that uniformity is more
>>> important here... indent is just convenience
>>> into: ctrl+shift+i is taken (I've never used it, but it maybe it's
>>> important), but we can still use ctrl+shift+n and underline n (point 2)
>>>
>>> If points 1 & 2 are implemented, then the letter is not as important,
>>> although first letter is always preferable.
>>>
>>> Peter
>>>
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>> > On Apr 16, 2016, at 8:37 PM, Peter Uhnák <i.uhnak at gmail.com> wrote:
>>>> >
>>>> > Hi,
>>>> >
>>>> > I'm getting fed-up with GTDebugger shortcuts since they are completely
>>>> > random.
>>>> >
>>>> > Can we have them more meaningful and/or somehow visible?
>>>> >
>>>> > For now I ended up overriding the labels so I can at least see them...
>>>> > but doing this is also stupid, because I still have to look at them since I
>>>> > cannot remember random shortcuts.
>>>> >
>>>> > <debugger.png>
>>>> >
>>>> > 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux
>>>> > btw)
>>>> > 2. can we use the default shortcuts pattern where one of the letters
>>>> > is underlined?
>>>> >
>>>> > Peter
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>> www.feenk.com
>>>>
>>>> "Value is always contextual."
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>



More information about the Pharo-dev mailing list