Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-10 Thread stepharo
tx Bernhard. Indeed this is a nice suggestion. Le 10/8/16 à 20:41, Bernhard Pieber a écrit : And this is how it works in VA Smalltalk. The default shortcut to expand the abbreviations used there is Shift-Space. See this excellent video by the late James Robertson:

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-10 Thread Bernhard Pieber
And this is how it works in VA Smalltalk. The default shortcut to expand the abbreviations used there is Shift-Space. See this excellent video by the late James Robertson: https://www.youtube.com/watch?v=TY_rJ3G0Tn4 If the same default abbreviations were used as in VA Smalltalk, this would be

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread stepharo
exactly… we even have the algorithm implemented for this. I insist I would enhance ocompletion instead of adding an expansion shortcut. But the rules may not be the same and we will see what lukas will do. and if someone want to hack just that now then we can use it now. Stef Esteban --

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread stepharo
Le 3/8/16 à 14:21, Peter Uhnak a écrit : that’s a lot better than hardcoding specific expansions, yes. I still believe this is work of completion engine, though… I don't know the current status (it's summer holidays), but we had a student that was interested in working on the completion

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread stepharo
itf ==> ifTrue: [ ] ifFalse: [ ] The could be an interface to define these code expansions - initially at least on a purely personal basis. > And this is not really for adding a new feature. This shortcut already (always :) ) existed With a single shortcut for

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread stepharo
Hi ben I think that this it the way to go: Only one key binding to rule all the expansions :) Stef On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano wrote: I will just re-post my first answer: if reintroduce them means reintroduce them hardcoded as before, then I’m

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread stepharo
s to be the case). Franck Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uh...@gmail.com To: pharo-dev@lists.pharo.org Subject: [Pharo-dev] ifTrue ifFalse shortcuts

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Ben Coman
On Wed, Aug 3, 2016 at 8:05 PM, Esteban Lorenzano wrote: > >> On 03 Aug 2016, at 13:47, Cyril Ferlicot Delbecque >> wrote: >> >> >> >> On 03/08/2016 10:56, Ben Coman wrote: >>> I would guess code expansions could be many and varied between >>>

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Peter Uhnak
> that’s a lot better than hardcoding specific expansions, yes. > I still believe this is work of completion engine, though… > I don't know the current status (it's summer holidays), but we had a student that was interested in working on the completion engine as his bachelor thesis next

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Esteban Lorenzano
> On 03 Aug 2016, at 13:47, Cyril Ferlicot Delbecque > wrote: > > > > On 03/08/2016 10:56, Ben Coman wrote: >> I would guess code expansions could be many and varied between >> different individuals, and quickly consume available keyboard >> shortcuts. Perhaps a

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Cyril Ferlicot Delbecque
On 03/08/2016 10:56, Ben Coman wrote: > I would guess code expansions could be many and varied between > different individuals, and quickly consume available keyboard > shortcuts. Perhaps a generic mechanism would be single shortcut for > "code expansion" which processes the letters preceding

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Esteban Lorenzano
> On 03 Aug 2016, at 11:08, Nicolai Hess wrote: > > > > 2016-08-03 10:56 GMT+02:00 Ben Coman >: > On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano > wrote: > > I

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Nicolai Hess
2016-08-03 11:10 GMT+02:00 Esteban Lorenzano : > > On 03 Aug 2016, at 10:52, Nicolai Hess wrote: > > > > 2016-08-03 10:36 GMT+02:00 Esteban Lorenzano : > >> I will just re-post my first answer: >> >> if reintroduce them means

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Nicolai Hess
2016-08-03 10:56 GMT+02:00 Ben Coman : > On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano > wrote: > > 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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Esteban Lorenzano
> On 03 Aug 2016, at 10:52, Nicolai Hess wrote: > > > > 2016-08-03 10:36 GMT+02:00 Esteban Lorenzano >: > I will just re-post my first answer: > > if reintroduce them means reintroduce them hardcoded as before, then

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Ben Coman
On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano wrote: > 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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Nicolai Hess
2016-08-03 10:36 GMT+02:00 Esteban Lorenzano : > 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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Esteban Lorenzano
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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Denis Kudriashov
2016-08-03 10:27 GMT+02:00 Guille Polito : > 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... > +1

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Guille Polito
-- Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uh...@gmail.com <mailto:i.uh...@gmail.com> To: pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org>

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Nicolai Hess
;> > >> Esteban > >> > >> > >> > >>> On 08 Aug 2015, at 12:45, Peter Uhnák <i.uh...@gmail.com> wrote: > >>> > >>> I would also appreciate if it was readded, as I've been using it > regularly. > >>> > >>> Peter

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Norbert Hartl
eniart <heniart.tho...@gmail.com >>> <mailto:heniart.tho...@gmail.com>> wrote: >>> I think it could be nice to keep this shortcut :) >>> >>> >>> On 08/08/2015 12:12, Franck Warlouzet wrote: >>>> Hi, >>>> >>>

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Tudor Girba
;i.uh...@gmail.com> 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 <heniart.tho...@gmail.com> >>> wrote: >>> I think

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 Thread Nicolai Hess
gt; >>> 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: i.uh...@gmail.com >>> To: pharo-dev@lists.pharo.org >>> 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 >>> >>> >>> >> >> > >

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-12 Thread stepharo
Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uh...@gmail.com mailto:i.uh...@gmail.com To: pharo-dev@lists.pharo.org mailto:pharo-dev@lists.pharo.org Subject: [Pharo-dev] ifTrue ifFalse shortcuts Hi

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-12 Thread stepharo
Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uh...@gmail.com mailto:i.uh...@gmail.com To: pharo-dev@lists.pharo.org mailto:pharo-dev@lists.pharo.org Subject: [Pharo-dev] ifTrue ifFalse shortcuts Hi, was removal of ifTrue/ifFalse shortcuts

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-11 Thread Nicolai Hess
-- Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uh...@gmail.com To: pharo-dev@lists.pharo.org 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

[Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread Peter Uhnák
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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread Franck Warlouzet
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: i.uh...@gmail.com To: pharo-dev@lists.pharo.org Subject: [Pharo-dev] ifTrue ifFalse shortcuts Hi

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread ThomasHeniart
Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uh...@gmail.com To: pharo-dev@lists.pharo.org 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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread Peter Uhnák
. 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: i.uh...@gmail.com To: pharo-dev@lists.pharo.org Subject: [Pharo-dev] ifTrue ifFalse shortcuts Hi

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread Sean P. DeNigris
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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread Franck Warlouzet
Ok then I will add it to Rubric Franck Date: Sat, 8 Aug 2015 03:54:02 -0700 From: s...@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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread stepharo
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

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread Esteban Lorenzano
of it (which seems to be the case). Franck Date: Sat, 8 Aug 2015 12:09:22 +0200 From: i.uh...@gmail.com mailto:i.uh...@gmail.com To: pharo-dev@lists.pharo.org mailto:pharo-dev@lists.pharo.org Subject: [Pharo-dev] ifTrue ifFalse shortcuts Hi, was removal of ifTrue/ifFalse shortcuts

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2015-08-08 Thread Sean P. DeNigris
EstebanLM wrote if reintroduce them means reintroduce them hardcoded as before, then I’m complete against it +1. I wrote the same thing in the issue comment just before I read this! - Cheers, Sean -- View this message in context: