Hi, Indeed. This somehow slipped from the todo list. Could you please open an issue for making the shortcuts settable and mark it for Pharo 5? Cheers, Doru
On Apr 17, 2016, at 10:32 PM, Mark Bestley <st@bestley.co.uk> wrote:
The most important thing is allow the user to reassign them.
e.g. when mainly a C programmer on Windows I used Visual Studio and remapped Eclipse keys to those when I worked in other languages.
Now I am on a Mac and so remapping to Xcode or as there is no standard set of keys I find the keys above the numeric pad the easieest to use and reconfigure Xcode, Eclipse and Intellij (and emacs) to use these.
Mark
On 17/04/2016 20:22, phil@highoctane.be wrote:
On Sun, Apr 17, 2016 at 8:50 PM, Peter Uhnák <i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>> wrote:
On Sun, Apr 17, 2016 at 8:17 PM, phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>> wrote:
Hitting a single key instead of Ctl-Alt-whatever madness.
Hmm. That's a good point. And since the shortcut name takes barely any space it could be presented alongside the label.
Proceed[F5] or Into[6]
On the other hand, for me personally at least... pressing ctrl+shift takes very little hand movement, while F keys are quite far. But then again, I'm using Microsoft Natural Ergonomic Keybord 4000 which is _really_ big, on laptop it may not be such an issue.
Microsoft Digital Media Pro Keyboard in this office. Not exactly small. Still not the Logitech G19 for gaming that I have on another machine. But there is space for a small card on top of the Fx keys.
F5 for step through, F6 for step over, F7 for step into, F8 for run to here would be a nice 4 key setup. Add F9 for create.
Note that most people have some Java background so, F5->F8 makes a lot of sense.
Also, Windows has Ctrl instead of Alt for most actions in Pharo5, that's annoying.
That's annoying also for other shortcuts⦠such as alt+c/alt+v for copy pasting, which is really weird (unless it has been fixed).
Yes but once used to it, both should work.
And you can put a little paper on top of them for easy reference.
If we could have something like http://community.sparxsystems.com/community-resources/509-81enterprise-archi... for Pharo, using a bunch of function keys, that would be cool.
I have more keyboard keys above F keys :( ⦠for example to instantly launch Pharo :)
:)
Peter
Phil
On Sun, Apr 17, 2016 at 7:05 PM, Peter Uhnák <i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>> wrote:
So they use F keys, however they are clearly not uniform either, so I don't see the appeal. Not to mention that they will be just as hard to remember.
On Sun, Apr 17, 2016 at 6:00 PM, Ben Coman <btc@openinworld.com <mailto:btc@openinworld.com>> wrote:
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@highoctane.be <mailto:philippe.back@highoctane.be> <philippe.back@gmail.com <mailto:philippe.back@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@gmail.com <mailto:i.uhnak@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@gmail.com <mailto:i.uhnak@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@gmail.com <mailto:i.uhnak@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 <http://www.tudorgirba.com> >>>> www.feenk.com <http://www.feenk.com> >>>> >>>> "Value is always contextual." >>>> >>>> >>>> >>>> >>>> >>> >>
-- Mark
-- www.tudorgirba.com www.feenk.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."