ifTrue ifFalse shortcuts
Locked
12
12
 
|
Hi,
was removal of ifTrue/ifFalse shortcuts on purpose, or by accident? (maybe was caused by switch to Rubric?) Peter |
Re: ifTrue ifFalse shortcuts
|
|
Hi,
Yes it was not on purpose. It is not implemented in Rubric, but I can do it if there is a need of it (which seems to be the case). Franck Date: Sat, 8 Aug 2015 12:09:22 +0200 From: [hidden email] To: [hidden email] Subject: [Pharo-dev] ifTrue ifFalse shortcuts Hi, was removal of ifTrue/ifFalse shortcuts on purpose, or by accident? (maybe was caused by switch to Rubric?) Peter |
|
|
I think it could be nice to keep this shortcut :)
On 08/08/2015 12:12, Franck Warlouzet
wrote:
|
|
|
I would also appreciate if it was readded, as I've been using it regularly. Peter On Sat, Aug 8, 2015 at 12:21 PM, ThomasHeniart <[hidden email]> wrote:
|
Re: ifTrue ifFalse shortcuts
|
Administrator
|
+1. Of course hopefully one day soon our dream of fully customizable shortcuts will be realized and we can each have the exact shortcuts we want :)
Cheers,
Sean |
Re: ifTrue ifFalse shortcuts
|
|
Ok then I will add it to Rubric
Franck > Date: Sat, 8 Aug 2015 03:54:02 -0700 > From: sean@clipperadams.com > To: pharo-dev@lists.pharo.org > Subject: Re: [Pharo-dev] ifTrue ifFalse shortcuts > > Peter Uhnák wrote > > I would also appreciate if it was readded, as I've been using it > > regularly. > > +1. Of course hopefully one day soon our dream of fully customizable > shortcuts will be realized and we can each have the exact shortcuts we want > :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ifTrue-ifFalse-shortcuts-tp4841604p4841618.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > |
|
|
In reply to this post by Sean P. DeNigris
We need people to help to continue to integrate keymapping :)
Le 8/8/15 12:54, Sean P. DeNigris a écrit : > Peter Uhnák wrote >> I would also appreciate if it was readded, as I've been using it >> regularly. > +1. Of course hopefully one day soon our dream of fully customizable > shortcuts will be realized and we can each have the exact shortcuts we want > :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ifTrue-ifFalse-shortcuts-tp4841604p4841618.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > |
|
|
In reply to this post by Peter Uhnak
if reintroduce them means reintroduce them hardcoded as before, then I’m complete against it and I WILL NOT integrate such solution.
I’m sorry for being so strong here, but previous implementation was lame and we need to get rid of them. Now, I understand people are used to use those bindings and also some others (no idea which ones because I never used them… for me ocompletion is good enough… but those are tastes). So I would be very happy to integrate a generic way to define keybindings and outputs (which is already there, with keymapping, but I mean an editor or something), and I would be very happy to integrate a default configuration (which of course, will include #ifTrue:/##ifFalse:) Esteban
|
Re: ifTrue ifFalse shortcuts
|
Administrator
|
+1. I wrote the same thing in the issue comment just before I read this!
Cheers,
Sean |
|
|
In reply to this post by EstebanLM
I am nearly finished with converting old shortcut mapping (Editor/TextEditor cmdActions/shiftCmdAction map) to our keymapping framework.cleanup TextEditors shortcut definition 2015-08-08 14:57 GMT+02:00 Esteban Lorenzano <[hidden email]>:
|
|
|
Thank a lot! Yesterday with guillermo and christophe we spent one full afternoon reading all the recursive dependencies introduced when we just want to have monticello in the bootstrap (to be able to load code). We filled up two black boards and I should say that I was a nice down to see the complexity but we will fix it :). Yesterday Esteban sat with igor and started to integrate the OSWindow integration work of igor (yes igor you should do pull requests :). So there are some problems with the mac vm and this will have to be fixed (probably next week). After I hope that we will get clean events from SDL
Tell us we will :) Thanks thanks thanks. I often frustrated when I see myself doing things more than twice but this is a pattern. I decided long time ago that if this is necessary to do intermediate actions to lower the stress on the future actions, I'm ready to throw awy what I did to get the ultimate goal reached.
|
|
|
In reply to this post by Nicolai Hess
Le 11/8/15 10:25, Nicolai Hess a
écrit :
Thank a lot! Yesterday with guillermo and christophe we spent one full afternoon reading all the recursive dependencies introduced when we just want to have monticello in the bootstrap (to be able to load code). We filled up two black boards and I should say that I was a nice down to see the complexity but we will fix it :). Yesterday Esteban sat with igor and started to integrate the OSWindow integration work of igor (yes igor you should do pull requests :). So there are some problems with the mac vm and this will have to be fixed (probably next week). After I hope that we will get clean events from SDL
Tell us we will :) Thanks thanks thanks. I often frustrated when I see myself doing things more than twice but this is a pattern. I decided long time ago that if this is necessary to do intermediate actions to lower the stress on the future actions, I'm ready to throw awy what I did to get the ultimate goal reached.
|
Re: ifTrue ifFalse shortcuts
|
|
Any objections on using cmd+t / cmd+f for insert ifTrue/ifFalse (linux/windows this would be alt+t/alt+f, mac this would be cmd+t/cmd+f). 2015-08-12 18:52 GMT+02:00 stepharo <[hidden email]>:
|
|
|
Hi,
Yes. Both of those commands are in use: - Cmd+t = suggestions - Cmd+f = search I think these types of inserts should not have simple bindings because we are asking for trouble. cheers, Doru > On Aug 3, 2016, at 10:15 AM, Nicolai Hess <[hidden email]> wrote: > > Any objections on using > cmd+t / cmd+f for insert ifTrue/ifFalse > (linux/windows this would be alt+t/alt+f, mac this would be cmd+t/cmd+f). > > 2015-08-12 18:52 GMT+02:00 stepharo <[hidden email]>: > > > Le 11/8/15 10:25, Nicolai Hess a écrit : >> I am nearly finished with converting old shortcut mapping (Editor/TextEditor cmdActions/shiftCmdAction map) >> to our keymapping framework. >> >> 15619 >> cleanup TextEditors shortcut definition > > Thank a lot! > > Yesterday with guillermo and christophe we spent one full afternoon reading all the recursive dependencies introduced > when we just want to have monticello in the bootstrap (to be able to load code). > We filled up two black boards and I should say that I was a nice down to see the complexity but we will fix it :). > > Yesterday Esteban sat with igor and started to integrate the OSWindow integration work of igor (yes igor you should do pull requests :). > So there are some problems with the mac vm and this will have to be fixed (probably next week). > After I hope that we will get clean events from SDL >> >> I need some more time, one or two vm changes and some people testing this on a mac. > > Tell us we will :) > >> >> I know, this is a bit late because we replace our text components with rubric, but if this >> is finished and working for "old" PluggableTextMorphs, I will do the same for rubric. > Thanks thanks thanks. > I often frustrated when I see myself doing things more than twice but this is a pattern. I decided long time ago that > if this is necessary to do intermediate actions to lower the stress on the future actions, I'm ready to throw awy what > I did to get the ultimate goal reached. > > >> >> >> >> 2015-08-08 14:57 GMT+02:00 Esteban Lorenzano <[hidden email]>: >> if reintroduce them means reintroduce them hardcoded as before, then I’m complete against it and I WILL NOT integrate such solution. >> I’m sorry for being so strong here, but previous implementation was lame and we need to get rid of them. >> >> Now, I understand people are used to use those bindings and also some others (no idea which ones because I never used them… for me ocompletion is good enough… but those are tastes). So I would be very happy to integrate a generic way to define keybindings and outputs (which is already there, with keymapping, but I mean an editor or something), and I would be very happy to integrate a default configuration (which of course, will include #ifTrue:/##ifFalse:) >> >> Esteban >> >> >> >>> On 08 Aug 2015, at 12:45, Peter Uhnák <[hidden email]> wrote: >>> >>> I would also appreciate if it was readded, as I've been using it regularly. >>> >>> Peter >>> >>> On Sat, Aug 8, 2015 at 12:21 PM, ThomasHeniart <[hidden email]> wrote: >>> I think it could be nice to keep this shortcut :) >>> >>> >>> On 08/08/2015 12:12, Franck Warlouzet wrote: >>>> Hi, >>>> >>>> Yes it was not on purpose. It is not implemented in Rubric, but I can do it if there is a need of it (which seems to be the case). >>>> >>>> Franck >>>> >>>> Date: Sat, 8 Aug 2015 12:09:22 +0200 >>>> From: [hidden email] >>>> To: [hidden email] >>>> Subject: [Pharo-dev] ifTrue ifFalse shortcuts >>>> >>>> Hi, >>>> >>>> was removal of ifTrue/ifFalse shortcuts on purpose, or by accident? >>>> https://pharo.fogbugz.com/f/cases/16125/Nautilus-doesn-t-recognize-the-cmd-T-cmd-F-ifTrue-ifFalse-shortcuts-anymore >>>> (maybe was caused by switch to Rubric?) >>>> >>>> Peter >>> >>> >> >> > > -- www.tudorgirba.com www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened." |
|
|
In reply to this post by Nicolai Hess-3-2
From a software design perspective it shouldn't be easy to insert #ifTrue:ifFalse :)
Norbert
|
Re: ifTrue ifFalse shortcuts
|
|
In reply to this post by Tudor Girba-2
2016-08-03 10:19 GMT+02:00 Tudor Girba <[hidden email]>: Hi, Ah ok, (on mac only, as on windows/linux suggesstions uses meta+t which is mapped to ctrl+t). cmd+shift+t cmd+shift+f ?
|
Re: ifTrue ifFalse shortcuts
|
|
In reply to this post by NorbertHartl
I'm also against.
- They take a place in the shortcuts that prevents others to use it - If lazy people really needs this, the code completion should be enhanced. This is a code completion concern... In general, my rule of thumb is to answer the following questions: How many people use it? - if a lot, maybe it makes sense to integrate it - if not a lot, make it a loadable extension How often do people use it? - if at least 10 times per hour (e.g., reformat code, senders, implementors, search) the shortcut should be simple - otherwise we can put it in a more complex combination to leave place to the common ones. Guille -------- Original Message --------
From a software design perspective it shouldn't be easy to insert #ifTrue:ifFalse :) |
Re: ifTrue ifFalse shortcuts
|
|
In reply to this post by NorbertHartl
2016-08-03 10:21 GMT+02:00 Norbert Hartl <[hidden email]>:
:-)
|
Re: ifTrue ifFalse shortcuts
|
|
In reply to this post by Guillermo Polito
2016-08-03 10:27 GMT+02:00 Guille Polito <[hidden email]>:
+1 |
|
|
I will just re-post my first answer:
if reintroduce them means reintroduce them hardcoded as before, then I’m complete against it and I WILL NOT integrate such solution.
I’m sorry for being so strong here, but previous implementation was lame and we need to get rid of them. Now, I understand people are used to use those bindings and also some others (no idea which ones because I never used them… for me ocompletion is good enough… but those are tastes). So I would be very happy to integrate a generic way to define keybindings and outputs (which is already there, with keymapping, but I mean an editor or something), and I would be very happy to integrate a default configuration (which of course, will include #ifTrue:/##ifFalse:) Esteban
|
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |