Re: [Pharo-users] Better Code Completion

But we should improve. It would be good to have someone taking that challenge because he would impact our all lives :) Le 10/10/15 12:22, Werner Kassens a écrit : On 10/10/2015 09:50 AM, stepharo wrote: the code should be in the image :) Hi Stephane, of course. but sometimes i only discove

Re: [Pharo-users] Multiple method deletion

Le 10/10/15 12:38, Peter Uhnák a écrit : I've been experiencing something similar, but I am using older Pharo ( 50287 ) and I wasn't quite able to precisely observe the reason for the error. There the problem was that I deleted a method, but the previously selected method was actually deleted

Re: [Pharo-users] Multiple method deletion

Thanks cyril I tried and I will try to reproduce it. If this happens again please try to tell us - was it when you removed one method? - was it when you removed multiple methods? Le 10/10/15 12:24, Ferlicot D. Cyril a écrit : Le 10/10/2015 07:57, stepharo a écrit : Are you sure? Becaus

Re: [Pharo-users] ifNotEmpty(Do):

Yes, ifNotEmptyDo: and ifNotNilDo: are for compatibility with other Smalltalks. The rule was added to communicate this in some way. Cheers. Uko > On 10 Oct 2015, at 18:55, Peter Uhnák wrote: > > Collection>>ifNotEmpty: comment says > > "If the block has an argument, eval with the receiver as

Re: [Pharo-users] ifNotEmpty(Do):

Look like #ifNotEmpty: is the correct choice. Collection methods select: [ :m | (m selector includesSubstring: 'if' caseSensitive: false) and: [ m selector includesSubstring: 'empty' caseSensitive: false ] ] thenCollect: [ :m |

[Pharo-users] ifNotEmpty(Do):

Collection>>ifNotEmpty: comment says "If the block has an argument, eval with the receiver as its argument, but it might be better to use ifNotEmptyDo: to make the code easier to understand" yet when I do that, Code Critic complains: ifNotEmptyDo: should not be used as ifNotEmpty: works for block

Re: [Pharo-users] Multiple method deletion

I've been experiencing something similar, but I am using older Pharo ( 50287 ) and I wasn't quite able to precisely observe the reason for the error. There the problem was that I deleted a method, but the previously selected method was actually deleted, so there were some selection inconsistencies.

Re: [Pharo-users] Better Code Completion

On 10/10/2015 09:50 AM, stepharo wrote: the code should be in the image :) Hi Stephane, of course. but sometimes i only discover some nice pharo code by reading a paper. i discovered ocompletion in the image only after having read that paper mentioned by Peter, and - thinking "yes, that shoul

Re: [Pharo-users] Multiple method deletion

Le 10/10/2015 09:57, stepharo a écrit : > Are you sure? > Because I code daily with it and I never got this behavior. > I will try. > Hilaire I can tell you that we worked a lot to improve it. > > Stef This is how I fell it, and apparently other feel the same. No doubt a lot of care is put into it

Re: [Pharo-users] Multiple method deletion

Le 10/10/2015 07:57, stepharo a écrit : > Are you sure? > Because I code daily with it and I never got this behavior. > I will try. > Hilaire I can tell you that we worked a lot to improve it. > > Stef > > I experienced it 4-5 times this week. -- Cyril Ferlicot http://www.synectique.eu 165

Re: [Pharo-users] Multiple method deletion

Are you sure? Because I code daily with it and I never got this behavior. I will try. Hilaire I can tell you that we worked a lot to improve it. Stef Le 9/10/15 19:10, Alexandre Bergel a écrit : Pharo 5, lastest version Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre

Re: [Pharo-users] Better Code Completion

the code should be in the image :) Le 7/10/15 18:31, Werner Kassens a écrit : Hi Peter, the difference between the paper i mentioned (JASE-completion) and ASE2008-completion (both accessible) is, i think, that in the first one also the class-level code completion of ocompletion is explained.