August 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Make the auto completion pop-up appear faster

by Franck Warlouzet

You are too patient guys, but yes 200 is nice Date: Mon, 10 Aug 2015 22:36:40 +0200 From: heniart.thomas(a)gmail.com To: pharo-dev(a)lists.pharo.org Subject: Re: [Pharo-dev] Make the auto completion pop-up appear faster 2015-08-10 22:17 GMT+02:00 Merwan Ouddane <merwanouddane(a)gmail.com>: 200 seems perfect to me. Same feeling :) Does anyone else have other preferences ? :) Le 10/08/2015 21:56, stepharo a Ã©crit : may be the default should be 250. Can you try and let us know? Le 10/8/15 17:39, Merwan Ouddane a Ã©crit : Yes. Specially if you have a bad timing, you start to type your method name and the pop-up shows up just before you press enter >< On lun., 2015-08-10 at 17:27 +0200, Franck Warlouzet wrote: On every image I take, I replace the delay from 500 to 100 and it is fast (too much maybe for some people) enough, 500 is far too much, you finished to type in a half second. Franck ______________________________________________________________________ Date: Mon, 10 Aug 2015 17:22:05 +0200 From: i.uhnak(a)gmail.com To: pharo-dev(a)lists.pharo.org Subject: Re: [Pharo-dev] Make the auto completion pop-up appear faster Yes, there is Settings > Code Browsing > Code Completion... > Popup appearance delay So I guess the question should be whether the _default_ delay should be shorter. Showing popup immediately may not be so useful, because you haven't typed much... I personally prefer to use shortcut to force the popup to show up. Peter On Mon, Aug 10, 2015 at 4:29 PM, Thomas Heniart <heniart.thomas(a)gmail.com> wrote: Hi, There is a setting for this Cheers, Thomas 2015-08-10 16:16 GMT+02:00 Merwan Ouddane <merwanouddane(a)gmail.com>: Hi, I wanted to have your opinion on this case: https://pharo.fogbugz.com/f/cases/15697/Speed-up-the-autocompletion-pop-up-… Cheers, Merwan

Aug. 10, 2015

Re: [Pharo-dev] Make the auto completion pop-up appear faster

by Thomas Heniart

2015-08-10 22:17 GMT+02:00 Merwan Ouddane <merwanouddane(a)gmail.com>: > 200 seems perfect to me. > Same feeling :) > > Does anyone else have other preferences ? :) > > > Le 10/08/2015 21:56, stepharo a Ã©crit : > >> may be the default should be 250. >> Can you try and let us know? >> >> >> Le 10/8/15 17:39, Merwan Ouddane a Ã©crit : >> >>> Yes. >>> Specially if you have a bad timing, you start to type your method name >>> and the pop-up shows up just before you press enter >< >>> >>> On lun., 2015-08-10 at 17:27 +0200, Franck Warlouzet wrote: >>> >>>> On every image I take, I replace the delay from 500 to 100 and it is >>>> fast (too much maybe for some people) enough, 500 is far too much, you >>>> finished to type in a half second. >>>> >>>> Franck >>>> >>>> >>>> ______________________________________________________________________ >>>> Date: Mon, 10 Aug 2015 17:22:05 +0200 >>>> From: i.uhnak(a)gmail.com >>>> To: pharo-dev(a)lists.pharo.org >>>> Subject: Re: [Pharo-dev] Make the auto completion pop-up appear faster >>>> >>>> Yes, there is >>>> Settings > Code Browsing > Code Completion... > Popup appearance delay >>>> >>>> >>>> So I guess the question should be whether the _default_ delay should >>>> be shorter. >>>> >>>> >>>> Showing popup immediately may not be so useful, because you haven't >>>> typed much... >>>> I personally prefer to use shortcut to force the popup to show up. >>>> >>>> >>>> Peter >>>> >>>> On Mon, Aug 10, 2015 at 4:29 PM, Thomas Heniart >>>> <heniart.thomas(a)gmail.com> wrote: >>>> Hi, >>>> There is a setting for this >>>> Cheers, >>>> Thomas >>>> 2015-08-10 16:16 GMT+02:00 Merwan Ouddane >>>> <merwanouddane(a)gmail.com>: >>>> Hi, >>>> I wanted to have your opinion on this >>>> case: >>>> >>>> https://pharo.fogbugz.com/f/cases/15697/Speed-up-the-autocompletion-pop-up-… >>>> Cheers, >>>> Merwan >>>> >>>> >>>> >>> >>> >>> >> >> > >

Aug. 10, 2015

Re: [Pharo-dev] Make the auto completion pop-up appear faster

by Merwan Ouddane

200 seems perfect to me. Does anyone else have other preferences ? :) Le 10/08/2015 21:56, stepharo a Ã©crit : > may be the default should be 250. > Can you try and let us know? > > > Le 10/8/15 17:39, Merwan Ouddane a Ã©crit : >> Yes. >> Specially if you have a bad timing, you start to type your method name >> and the pop-up shows up just before you press enter >< >> >> On lun., 2015-08-10 at 17:27 +0200, Franck Warlouzet wrote: >>> On every image I take, I replace the delay from 500 to 100 and it is >>> fast (too much maybe for some people) enough, 500 is far too much, you >>> finished to type in a half second. >>> >>> Franck >>> >>> >>> ______________________________________________________________________ >>> Date: Mon, 10 Aug 2015 17:22:05 +0200 >>> From: i.uhnak(a)gmail.com >>> To: pharo-dev(a)lists.pharo.org >>> Subject: Re: [Pharo-dev] Make the auto completion pop-up appear faster >>> >>> Yes, there is >>> Settings > Code Browsing > Code Completion... > Popup appearance delay >>> >>> >>> So I guess the question should be whether the _default_ delay should >>> be shorter. >>> >>> >>> Showing popup immediately may not be so useful, because you haven't >>> typed much... >>> I personally prefer to use shortcut to force the popup to show up. >>> >>> >>> Peter >>> >>> On Mon, Aug 10, 2015 at 4:29 PM, Thomas Heniart >>> <heniart.thomas(a)gmail.com> wrote: >>> Hi, >>> There is a setting for this >>> Cheers, >>> Thomas >>> 2015-08-10 16:16 GMT+02:00 Merwan Ouddane >>> <merwanouddane(a)gmail.com>: >>> Hi, >>> I wanted to have your opinion on >>> this case: >>> https://pharo.fogbugz.com/f/cases/15697/Speed-up-the-autocompletion-pop-up-… >>> Cheers, >>> Merwan >>> >>> >> >> >> > >

Aug. 10, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by Ferlicot D. Cyril

Le 10/08/2015 21:58, stepharo a Ã©crit : > I know that "bernardo" did many conversions now may be there are some > left. So we should have a deprecation. > Since 50201 Announcer>>on:send:to: and Annoucer>>on:do: are deprecated. > Stef > > -- Cheers Cyril

Aug. 10, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by stepharo

I know that "bernardo" did many conversions now may be there are some left. So we should have a deprecation. Stef Le 10/8/15 18:22, Ben Coman a Ã©crit : > On Mon, Aug 10, 2015 at 11:36 PM, Ferlicot D. Cyril > <cyril.ferlicot(a)gmail.com> wrote: >> Le 30/07/2015 09:04, Marcus Denker a Ã©crit : >>> Hi, >>> >>> We have 622 open issues. There are *a lot* of old issues that nobody will ever look at. >>> Please check those that *you* submitted to see what the status is! >>> >>> If it is just âwould be niceâ, but not even on a level that you yourself are willing to even >>> send a mail to the mailing list to get people interested in helping you to push the case >>> forward, maybe you could think about closing the issue? >>> >>> Maybe someone asked a question? If you submit an issue and there is a question not answered >>> for a month, we should close it: How important can it be? Why should *I* spend the time to fix >>> this issue if *you* are not even willing to answer a question in a minute? >>> >>> It makes no sense to have lots and lots of issues that are not important even for the submitter. >>> >>> Another thing is that issues get fixed, subsystems replaced, code removedâ¦ and the amazing thing >>> is that *never* the submitter of the original report closes it, even in these obvious cases. >>> >>> The issue tracker is not a one way street! >>> >>> Marcus >>> >>> >> >> I think we can close this issue: >> https://pharo.fogbugz.com/f/cases/4399/deprecate-on-send-to-and-use-when-se… >> >> We deprecated Announcer>>on:send:to: and Announcer>>on:do: previously. >> > Do all senders need to be converted first? > cheers -ben > >

Aug. 10, 2015

Re: [Pharo-dev] Make the auto completion pop-up appear faster

by stepharo

may be the default should be 250. Can you try and let us know? Le 10/8/15 17:39, Merwan Ouddane a Ã©crit : > Yes. > Specially if you have a bad timing, you start to type your method name > and the pop-up shows up just before you press enter >< > > On lun., 2015-08-10 at 17:27 +0200, Franck Warlouzet wrote: >> On every image I take, I replace the delay from 500 to 100 and it is >> fast (too much maybe for some people) enough, 500 is far too much, you >> finished to type in a half second. >> >> Franck >> >> >> ______________________________________________________________________ >> Date: Mon, 10 Aug 2015 17:22:05 +0200 >> From: i.uhnak(a)gmail.com >> To: pharo-dev(a)lists.pharo.org >> Subject: Re: [Pharo-dev] Make the auto completion pop-up appear faster >> >> Yes, there is >> Settings > Code Browsing > Code Completion... > Popup appearance delay >> >> >> So I guess the question should be whether the _default_ delay should >> be shorter. >> >> >> Showing popup immediately may not be so useful, because you haven't >> typed much... >> I personally prefer to use shortcut to force the popup to show up. >> >> >> Peter >> >> On Mon, Aug 10, 2015 at 4:29 PM, Thomas Heniart >> <heniart.thomas(a)gmail.com> wrote: >> Hi, >> There is a setting for this >> >> >> Cheers, >> >> Thomas >> >> >> 2015-08-10 16:16 GMT+02:00 Merwan Ouddane >> <merwanouddane(a)gmail.com>: >> Hi, >> >> I wanted to have your opinion on this case: >> https://pharo.fogbugz.com/f/cases/15697/Speed-up-the-autocompletion-pop-up-… >> >> Cheers, >> Merwan >> >> >> >> >> >> > > >

Aug. 10, 2015

Re: [Pharo-dev] Nautilus leak symptom

by stepharo

> Its been noted before there may be some leak in Nautilus. Yes because probably of announcer. Thanks for reporting them. We started to clean Nautilus and we already simplified a lot some dark corners but there was and still certainly a lot of places for improvements. > I bumped > into a possible symptom... > > 1. Open fresh image (e.g. 50216) > > 2. Open Transcript. > > 3. Open *one* System Browser > > 4. Add instrumentation to method Nautilus >>> NautilusUI >> methodModified: > e.g.... Transcript crShow: '>>>' , thisContext printString; tab; > show: anAnnouncement printString ; tab ; show: sourceTextModel text. > > 5. In same System Browser, > add method MyPackage >>> MyClass >> test1 > > Observe steps (4.) and (5.) each logged a single item to Transcript. > > 6. Open a *second* System Browser and > add method MyPackage >>> MyClass >> test2 > > Observe step (6.) logged two items to Transcript, one for each open > System Browser. > > 7. Close *second* System Browser. > 8. In *first* System Browser, modify #test1. > > Observe step (8.) logged two items to Transcript. I would expect only one. > > > Is there any issue open for this? I couldn't find one. > > cheers -ben > >

Aug. 10, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by Ferlicot D. Cyril

Le 10/08/2015 18:22, Ben Coman a Ã©crit : > Do all senders need to be converted first? > cheers -ben > I already did it. Maybe I missed one but we should have a warning if that's the case. -- Cheers Cyril

Aug. 10, 2015

Nautilus leak symptom & possible fix

by Ben Coman

Its been noted before there may be some leak in Nautilus. I bumped into a possible symptom... 1. Open fresh image (e.g. 50216) 2. Open Transcript. 3. Open *one* System Browser 4. Add instrumentation to method Nautilus >>> NautilusUI >> methodModified: e.g.... Transcript crShow: '>>>' , thisContext printString; tab; show: anAnnouncement printString ; tab ; show: sourceTextModel text. 5. In same System Browser, add method MyPackage >>> MyClass >> test1 Observe steps (4.) and (5.) each logged a single item to Transcript. 6. Open a *second* System Browser and add method MyPackage >>> MyClass >> test2 Observe step (6.) logged two items to Transcript, one for each open System Browser. 7. Close *second* System Browser. 8. In *first* System Browser, modify #test1. Observe step (8.) logged two items to Transcript. I would expect only one. Is there any issue open for this? I couldn't find one. ----------------- Try 1, not sure yet if this is all that is required, but its a start... NautilusWindow >> delete | mod | mod := self model. super delete. ">>>" SystemAnnouncer uniqueInstance unsubscribe: mod. "<<<added" mod ifNotNil: [ mod announce: (WindowClosed new window: self) ] cheers -ben

Aug. 10, 2015

Re: [Pharo-dev] [Issue tracker] *Please* look at your old reported issues!

by Ben Coman

On Mon, Aug 10, 2015 at 11:36 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > Le 30/07/2015 09:04, Marcus Denker a Ã©crit : >> Hi, >> >> We have 622 open issues. There are *a lot* of old issues that nobody will ever look at. >> Please check those that *you* submitted to see what the status is! >> >> If it is just âwould be niceâ, but not even on a level that you yourself are willing to even >> send a mail to the mailing list to get people interested in helping you to push the case >> forward, maybe you could think about closing the issue? >> >> Maybe someone asked a question? If you submit an issue and there is a question not answered >> for a month, we should close it: How important can it be? Why should *I* spend the time to fix >> this issue if *you* are not even willing to answer a question in a minute? >> >> It makes no sense to have lots and lots of issues that are not important even for the submitter. >> >> Another thing is that issues get fixed, subsystems replaced, code removedâ¦ and the amazing thing >> is that *never* the submitter of the original report closes it, even in these obvious cases. >> >> The issue tracker is not a one way street! >> >> Marcus >> >> > > > I think we can close this issue: > https://pharo.fogbugz.com/f/cases/4399/deprecate-on-send-to-and-use-when-se… > > We deprecated Announcer>>on:send:to: and Announcer>>on:do: previously. > Do all senders need to be converted first? cheers -ben

Aug. 10, 2015