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

2016-05-03 Thread stepharo
May be it works for millions people. So we can add EXTRA bindings to be compatible for them but I have something else to do that to learn and use keys that can be removed from my keyboard. For me there are to control volume output and nothing else. Stef Le 19/4/16 à 22:49,

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

2016-04-19 Thread Tudor Girba
We already agreed to have the shortcuts externalized and we will try to do for Pharo 5. Please let’s close this topic and move on. Doru > On Apr 19, 2016, at 10:57 PM, Sven Van Caekenberghe wrote: > > We can have both, or we can make it super easy to enable or customise them. >

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

2016-04-19 Thread Esteban A. Maringolo
2016-04-19 17:49 GMT-03:00 p...@highoctane.be : > On Tue, Apr 19, 2016 at 8:38 PM, Eliot Miranda > wrote: > But Pharo? Nah! > We have a great debugger? Sure let's hide it under absconse shortcuts that > only we know. > > New debugger is nicer looking

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

2016-04-19 Thread Sven Van Caekenberghe
We can have both, or we can make it super easy to enable or customise them. Phil has a point: it seems there is some standard out there. > On 19 Apr 2016, at 22:49, p...@highoctane.be wrote: > > > > On Tue, Apr 19, 2016 at 8:38 PM, Eliot Miranda > wrote: > > > > > >

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

2016-04-19 Thread p...@highoctane.be
On Tue, Apr 19, 2016 at 8:38 PM, Eliot Miranda wrote: > > > On Tue, Apr 19, 2016 at 6:52 AM, stepharo wrote: > >> This F keys suck! >> > > +1. How do you remember which F key does what in the Debugger? F10 - fix > my code to be a perfect 10?? > With

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

2016-04-19 Thread p...@highoctane.be
On Tue, Apr 19, 2016 at 8:38 PM, Eliot Miranda wrote: > > > > On Tue, Apr 19, 2016 at 6:52 AM, stepharo wrote: >> >> This F keys suck! > > > +1. How do you remember which F key does what in the Debugger? F10 - fix my code to be a perfect 10?? > Yeah,

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

2016-04-19 Thread Eliot Miranda
On Tue, Apr 19, 2016 at 6:52 AM, stepharo wrote: > This F keys suck! > +1. How do you remember which F key does what in the Debugger? F10 - fix my code to be a perfect 10?? > Stef > > Le 17/4/16 18:00, Ben Coman a écrit : > > Interesting. A search turned up... Quick Tip

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

2016-04-19 Thread stepharo
This F keys suck! Stef Le 17/4/16 18:00, Ben Coman a écrit : 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.b...@highoctane.be wrote:

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

2016-04-18 Thread Mark Bestley
Added as #10820 but for Pharo6 as per other requests Mark On 18/04/2016 10:30, Tudor Girba wrote: 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

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

2016-04-17 Thread p...@highoctane.be
On Sun, Apr 17, 2016 at 8:50 PM, Peter Uhnák wrote: > > > On Sun, Apr 17, 2016 at 8:17 PM, p...@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

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

2016-04-17 Thread Peter Uhnák
On Sun, Apr 17, 2016 at 8:17 PM, p...@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

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

2016-04-17 Thread p...@highoctane.be
Hitting a single key instead of Ctl-Alt-whatever madness. 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. And you can put a little paper on top of them for easy reference. If we

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

2016-04-17 Thread Peter Uhnák
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 wrote: > Interesting. A search turned up... Quick Tip Debugger Shortcut Key >

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

2016-04-17 Thread Ben Coman
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.b...@highoctane.be wrote: > Most of the world IDE use function keys for debugging. > >

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

2016-04-17 Thread philippe.b...@highoctane.be
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" wrote: > >

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

2016-04-17 Thread Peter Uhnák
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

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

2016-04-16 Thread Peter Uhnák
> > 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