[Pharo-dev] Stable configuration of PetitParser broken for stable PetitGui in Pharo 5

Loading PetitGui with this expression: --- Metacello new configuration: 'PetitParser'; version: #'stable'; repository: 'http://smalltalkhub.com/mc/Moose/PetitParser/main/'; load: 'PetitGui'. --- loads, but any attempt to use the PetitParser GUI tool results in deprecation exceptions like

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Thanks for the follow up post of this change log Marcus. cheers -ben On Wed, Aug 3, 2016 at 5:23 PM, Marcus Denker wrote: > >> On 03 Aug 2016, at 11:07, GitHub wrote: >> >> >> Log Message: >> --- >> 60163 >> 18831 Integrate new Epicea

Re: [Pharo-dev] ifTrue ifFalse shortcuts

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

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

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

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

Le 3/8/16 à 10:27, Guille Polito a écrit : 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... For your information a student from Prague will

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Thanks Martin. We missed yesterday: show only the latest version of every entities. :) Setf Le 3/8/16 à 11:23, Marcus Denker a écrit : On 03 Aug 2016, at 11:07, GitHub wrote: Log Message: --- 60163 18831 Integrate new Epicea version

Re: [Pharo-dev] ifTrue ifFalse shortcuts

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 >>>

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60167 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 3dbc9a: 60167

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 3dbc9a34a1ed59a0c76483034e67bda09c12a842 https://github.com/pharo-project/pharo-core/commit/3dbc9a34a1ed59a0c76483034e67bda09c12a842 Author: Jenkins Build Server Date:

Re: [Pharo-dev] [pharo-project/pharo-core] 94fcf4: 60165

Thanks for the follow up log message Marcus. cheers -ben On Wed, Aug 3, 2016 at 7:00 PM, Marcus Denker wrote: > >> On 03 Aug 2016, at 12:24, GitHub wrote: >> >> Branch: refs/heads/6.0 >> Home: https://github.com/pharo-project/pharo-core >>

Re: [Pharo-dev] ifTrue ifFalse shortcuts

> 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

> 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

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60166 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] ifTrue ifFalse shortcuts

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] [pharo-project/pharo-core] 94fcf4: 60165

> On 03 Aug 2016, at 12:24, GitHub wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 94fcf44742b41d7898726b57a76edc70fb1d9aea > >

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60165 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 94fcf4: 60165

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 94fcf44742b41d7898726b57a76edc70fb1d9aea https://github.com/pharo-project/pharo-core/commit/94fcf44742b41d7898726b57a76edc70fb1d9aea Author: Jenkins Build Server Date:

Re: [Pharo-dev] ifTrue ifFalse shortcuts

> 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

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60164 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] da55ae: 60164

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: da55ae710e057333d74071fe26ce269850f496ec https://github.com/pharo-project/pharo-core/commit/da55ae710e057333d74071fe26ce269850f496ec Author: Jenkins Build Server Date:

Re: [Pharo-dev] ifTrue ifFalse shortcuts

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] [pharo-project/pharo-core] f57843: 60163

> On 03 Aug 2016, at 11:07, GitHub wrote: > > > Log Message: > --- > 60163 > 18831 Integrate new Epicea version > https://pharo.fogbugz.com/f/cases/18831 > ChangeLog for this: - Case 18813: Implement redo and undo of protocol addition and removal. -

[Pharo-dev] [pharo-project/pharo-core] f57843: 60163

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f578434a0d828004d918c36066a3cff9163f056b https://github.com/pharo-project/pharo-core/commit/f578434a0d828004d918c36066a3cff9163f056b Author: Jenkins Build Server Date:

Re: [Pharo-dev] GT-Spotter dive in shortcut

2016-08-03 10:02 GMT+02:00 Tudor Girba : > Hi, > > > On Aug 3, 2016, at 9:16 AM, Nicolai Hess wrote: > > > > > > > > 2016-06-18 23:34 GMT+02:00 Nicolai Hess : > > > > > > 2016-06-18 20:55 GMT+02:00 Tudor Girba

Re: [Pharo-dev] ifTrue ifFalse shortcuts

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

> 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

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60163 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] ifTrue ifFalse shortcuts

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 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

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 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

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?

Re: [Pharo-dev] ifTrue ifFalse shortcuts

2016-08-03 10:19 GMT+02:00 Tudor Girba : > Hi, > > Yes. Both of those commands are in use: > - Cmd+t = suggestions > - Cmd+f = search > 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 ? > > I think

Re: [Pharo-dev] ifTrue ifFalse shortcuts

From a software design perspective it shouldn't be easy to insert #ifTrue:ifFalse :) Norbert > Am 03.08.2016 um 10:15 schrieb Nicolai Hess : > > Any objections on using > cmd+t / cmd+f for insert ifTrue/ifFalse > (linux/windows this would be alt+t/alt+f, mac this would

Re: [Pharo-dev] ifTrue ifFalse shortcuts

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 wrote: > > Any objections on

Re: [Pharo-dev] 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 : > > > Le 11/8/15 10:25, Nicolai Hess a écrit : > > I am nearly finished with converting old shortcut

Re: [Pharo-dev] GT-Spotter dive in shortcut

Hi, > On Aug 3, 2016, at 9:16 AM, Nicolai Hess wrote: > > > > 2016-06-18 23:34 GMT+02:00 Nicolai Hess : > > > 2016-06-18 20:55 GMT+02:00 Tudor Girba : > Hi, > > Command is an actual key on Mac next to Option(which is Alt)

Re: [Pharo-dev] GT-Spotter dive in shortcut

2016-06-18 23:34 GMT+02:00 Nicolai Hess : > > > 2016-06-18 20:55 GMT+02:00 Tudor Girba : > >> Hi, >> >> Command is an actual key on Mac next to Option(which is Alt) and Control. >> So, Command is a concrete key and mapping it logically to another key