April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Esteban Lorenzano

Well... I disagree with your disagreement :) We are talking about two different things: 1) the current defaults 2) some possible broken configuration about the current defaults, "enter" is the one that is choose for 99% of IDEs around the world (and yes, the 1% default is probably just Pharo 1.4). so, we took the world default and placed there because we want to be friendly with newcomers (and frankly, I'm tired of see students learning Pharo pressing enter each time they want a completion and complaining when they don't have the answer they expect) The enter as default should stay, because that's the world standard. For power users like you, there is a settings browser to disable it... and you know, there is also a way to store your settings, so you can put them there and never ever in your life realize that you have different defaults. Now, in the settings: Go to code completion configuration: 1) Disable the option "Complete common prefixes using TAB in the suggested completions". This is for provide something like the bash completion (that completes until the chars are equal and allows you to introduce a character to continue refining the completion) 2) Disable the option "Use ENTER to accept a suggested completion" and then you have exactly the same behavior as before :) (but yes, the message explaining the options could be better) you can also then press "Export Settings" (button in top-right), and all your images will share same configuration. how to doit directly in the settings? go to ~/Library/Preferences/pharo/2.0 (for Mac) (if it does not exist, just create it) then create a file settings.st, with this content: StartupLoader default executeAtomicItems: { StartupAction name: 'Settings 2.0' code: [ NECPreferences expandPrefixes: false; useEnterToAccept: false. ] runOnce: true. }. I don't think that this is perfect, and there are some things that certainly can be enhanced... but you actually can configure your settings. It is impossible to believe that everybody will share same taste for programming, what you believe is obvious is obscure for others... that's why we try to match standards when we can, and to provide settings enough for those who does not follow them :) cheers, Esteban On Apr 4, 2013, at 2:19 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> theres a setting to: >> >> - disable ENTER to accept the completion >> - to increase the popup delay >> >> so I think that is invalid bug report then... >> > > i tend to disagree. > The defaults which we have now in 2.0 for autocompletion > is breaking my workflow badly too. > > Yes, i can go to settings and disable/reconfigure stuff but that doesn't > nullifying the fact, that my workflow is broken with ambiguous and inconsistent > reaction(s) to my keystrokes by UI if i keep defaults. > > For instance i am still clueless, why 'enter' is default for autocompletion, > and disabling it and enabling 'tab' simply doesn't works. > That leaves me with the only option: keep using 'enter' for > autocompletion, if i ever want to use it. > We have to fix that. > > >> On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >> >>> From >>> https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… >>> : >>> >>>> The combination of enter on accept, with the current behavior to select >>>> the first completion suggestion by default = trouble. For example: >>>> >>>> 1. Type "printOn: aStream"... pretty common method start >>>> 2. Hit enter to go to the next line >>>> >>>> You will now have "printOn: MCDataStream" WTF!! I get burned by this >>>> pretty regularly and it's annoying. I'm not sure what the fix should be... >>>> probably no default selection in the suggestion menu, but possibly only >>>> when enter on accept is enabled (t would require an extra key press to >>>> complete and when do you ever type a tab in the middle of a line?) >>> >>> >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> > > > > -- > Best regards, > Igor Stasenko. >

April 4, 2013

Re: [Pharo-project] Configuration Browser - CI link

by Esteban Lorenzano

what will happen (eventually) is that all the configurations in the "verified" panel will pass an acceptance test before be placed there. but since conceptually CI is more or less opposite to "Stable Release", I don't think that a marriage between them would be cool (also, that would mean that we need a CI process for each project in configs browser, and I frankly don't see that happening) Esteban On Apr 4, 2013, at 2:49 AM, Ben Coman <btc(a)openInWorld.com> wrote: > Just a random idea... (Not for implementing any time soon, just sharing) > > It might be cool if Configuration Browser items could be linked to status on a CI server, displaying a smiley or weather icon next to the item. Those items would tend to draw more user attention and be an incentive for developers to get a green job on the Contribution CI server. > > cheers -ben >

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Johan Brichau

+1 btw, if I disable that <enter> selects the current suggestion, how can I select the suggestion without using the mouse? imho, <tab> should select the suggestion eventually. On 04 Apr 2013, at 09:06, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > +1 > Very annoying. > > > 2013/4/4 Igor Stasenko <siguctua(a)gmail.com> > On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > theres a setting to: > > > > - disable ENTER to accept the completion > > - to increase the popup delay > > > > so I think that is invalid bug report then... > > > > i tend to disagree. > The defaults which we have now in 2.0 for autocompletion > is breaking my workflow badly too. > > Yes, i can go to settings and disable/reconfigure stuff but that doesn't > nullifying the fact, that my workflow is broken with ambiguous and inconsistent > reaction(s) to my keystrokes by UI if i keep defaults. > > For instance i am still clueless, why 'enter' is default for autocompletion, > and disabling it and enabling 'tab' simply doesn't works. > That leaves me with the only option: keep using 'enter' for > autocompletion, if i ever want to use it. > We have to fix that. > > > > On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > > > >> From > >> https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… > >> : > >> > >>> The combination of enter on accept, with the current behavior to select > >>> the first completion suggestion by default = trouble. For example: > >>> > >>> 1. Type "printOn: aStream"... pretty common method start > >>> 2. Hit enter to go to the next line > >>> > >>> You will now have "printOn: MCDataStream" WTF!! I get burned by this > >>> pretty regularly and it's annoying. I'm not sure what the fix should be... > >>> probably no default selection in the suggestion menu, but possibly only > >>> when enter on accept is enabled (t would require an extra key press to > >>> complete and when do you ever type a tab in the middle of a line?) > >> > >> > >> > >> > >> > >> ----- > >> Cheers, > >> Sean > >> -- > >> View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… > >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >> > > > > > > > > -- > Best regards, > Igor Stasenko. > >

April 4, 2013

Re: [Pharo-project] Nautilus accessor over-generation

by Benjamin

Since Nautilus is meant to also work without the refactoring engine, I have provided the Analyze menu, which is far lees powerful that the refactoring engine, but it's working out of the box. Ben On Apr 3, 2013, at 9:23 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > There is: > Nautilus class context menu > 1. - Analyze -> Create inst var accessors (which allows you to multiple inst > vars, but not omit setters/getters) > - Refactoring > 2. -> Class refactoring -> Generate accessors (which generates all by > default, but allows you to omit whichever methods you want) > 3. -> Inst Var Refactoring -> Accessors (which operates on a single inst > var, and allows you to omit getter or setter) > > #1 seems to add nothing to the party. It's the least flexible and is covered > by #2. > > My confusion: I was always using #3 and didn't even realize #1 and #2 > existed. I started to write code to select multiple inst vars at once in #3 > and stumbled upon #1 and #2. Maybe #2 could be duplicated next to #3 with a > more-differentiated name. > > Slightly OT, it seems that listing the inst var "refactorings" (is adding an > inst var really a refactoring?) is kind of a hack. For me, it'd make more > sense and be more OO if the browser knew how to deal with inst vars > explicitly, maybe as a sidebar to the class definition, or maybe the class > definition should be abstracted behind a real UI. i.e. inst var widgets > instead of a string... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nautilus-accessor-over-generation-tp4679480.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by phil＠highoctane.be

+1 Very annoying. 2013/4/4 Igor Stasenko <siguctua(a)gmail.com> > On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > theres a setting to: > > > > - disable ENTER to accept the completion > > - to increase the popup delay > > > > so I think that is invalid bug report then... > > > > i tend to disagree. > The defaults which we have now in 2.0 for autocompletion > is breaking my workflow badly too. > > Yes, i can go to settings and disable/reconfigure stuff but that doesn't > nullifying the fact, that my workflow is broken with ambiguous and > inconsistent > reaction(s) to my keystrokes by UI if i keep defaults. > > For instance i am still clueless, why 'enter' is default for > autocompletion, > and disabling it and enabling 'tab' simply doesn't works. > That leaves me with the only option: keep using 'enter' for > autocompletion, if i ever want to use it. > We have to fix that. > > > > On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> > wrote: > > > >> From > >> > https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… > >> : > >> > >>> The combination of enter on accept, with the current behavior to select > >>> the first completion suggestion by default = trouble. For example: > >>> > >>> 1. Type "printOn: aStream"... pretty common method start > >>> 2. Hit enter to go to the next line > >>> > >>> You will now have "printOn: MCDataStream" WTF!! I get burned by this > >>> pretty regularly and it's annoying. I'm not sure what the fix should > be... > >>> probably no default selection in the suggestion menu, but possibly only > >>> when enter on accept is enabled (t would require an extra key press to > >>> complete and when do you ever type a tab in the middle of a line?) > >> > >> > >> > >> > >> > >> ----- > >> Cheers, > >> Sean > >> -- > >> View this message in context: > http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… > >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >> > > > > > > > > -- > Best regards, > Igor Stasenko. > >

April 4, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by Sean P. DeNigris

Igor Stasenko wrote > Any feedback & help & contributions & improvements is welcome. Really nice :) That was my first time using the zero conf scripts... very slick :) And the tutorial was extremely clear and thorough. This active essay embodies the dynabook spirit. I added a "The end" page and a little edit to prevent stepping past the last page. No repo access, attaching to Nabble... Athens-Tutorial-SeanDeNigris.2.mcz <http://forum.world.st/file/n4679523/Athens-Tutorial-SeanDeNigris.2.mcz> ----- Cheers, Sean -- View this message in context: http://forum.world.st/FYI-Athens-tutorial-tp4679512p4679523.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Tudor Girba

+1 Doru On Apr 4, 2013, at 2:19 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> theres a setting to: >> >> - disable ENTER to accept the completion >> - to increase the popup delay >> >> so I think that is invalid bug report then... >> > > i tend to disagree. > The defaults which we have now in 2.0 for autocompletion > is breaking my workflow badly too. > > Yes, i can go to settings and disable/reconfigure stuff but that doesn't > nullifying the fact, that my workflow is broken with ambiguous and inconsistent > reaction(s) to my keystrokes by UI if i keep defaults. > > For instance i am still clueless, why 'enter' is default for autocompletion, > and disabling it and enabling 'tab' simply doesn't works. > That leaves me with the only option: keep using 'enter' for > autocompletion, if i ever want to use it. > We have to fix that. > > >> On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >> >>> From >>> https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… >>> : >>> >>>> The combination of enter on accept, with the current behavior to select >>>> the first completion suggestion by default = trouble. For example: >>>> >>>> 1. Type "printOn: aStream"... pretty common method start >>>> 2. Hit enter to go to the next line >>>> >>>> You will now have "printOn: MCDataStream" WTF!! I get burned by this >>>> pretty regularly and it's annoying. I'm not sure what the fix should be... >>>> probably no default selection in the suggestion menu, but possibly only >>>> when enter on accept is enabled (t would require an extra key press to >>>> complete and when do you ever type a tab in the middle of a line?) >>> >>> >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> > > > > -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

April 4, 2013

Re: [Pharo-project] [Pharo-users] [FYI] Athens tutorial

by Tudor Girba

Hi, Indeed, we just followed this tutorial at PharoConf, and it is well made. Thanks, Igor. Doru On Apr 4, 2013, at 2:07 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hello, there > > i prepared a small tutorial for Athens, which i did today at PharoConf. > But the code i did can be reused by non-participants of conference :) > > Here the instructions. > > Download Pharo 2.0 > > wget -O - get.pharo.org | bash > > Run Pharo 2.0 > > ./pharo-ui Pharo.image > > In a workspace, evaluate (line after line) > > Gofer it smalltalkhubUser: 'Pharo' project: 'Athens'; configuration; load. > > ConfigurationOfAthens loadVersion: '2.0'. > > Gofer it smalltalkhubUser: 'Pharo' project: 'Athens'; > package:'Athens-Tutorial'; load. > > AthensTutorial new openWithSpec. > > > Took from here > https://gist.github.com/SergeStinckwich/44ca34b54cde83b687a3 > (just removed duplicates ;) > > Thanks, Serge for compiling it down ;) > > Once you load the code and have window open, skip step one (you already did it), > and then just follow the steps by pressing doit button changing the > code , pressing doit again , going forwards etc .. and playing with > it. > I put some comments there to serve as a small description/detail. > > Any feedback & help & contributions & improvements is welcome. > > P.S. if you get a DNU at step 30, enable Freetype in settings and try again. > > -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

April 4, 2013

[Pharo-project] Configuration Browser - CI link

by Ben Coman

Just a random idea... (Not for implementing any time soon, just sharing) It might be cool if Configuration Browser items could be linked to status on a CI server, displaying a smiley or weather icon next to the item. Those items would tend to draw more user attention and be an incentive for developers to get a green job on the Contribution CI server. cheers -ben

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Igor Stasenko

On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: > theres a setting to: > > - disable ENTER to accept the completion > - to increase the popup delay > > so I think that is invalid bug report then... > i tend to disagree. The defaults which we have now in 2.0 for autocompletion is breaking my workflow badly too. Yes, i can go to settings and disable/reconfigure stuff but that doesn't nullifying the fact, that my workflow is broken with ambiguous and inconsistent reaction(s) to my keystrokes by UI if i keep defaults. For instance i am still clueless, why 'enter' is default for autocompletion, and disabling it and enabling 'tab' simply doesn't works. That leaves me with the only option: keep using 'enter' for autocompletion, if i ever want to use it. We have to fix that. > On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> From >> https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… >> : >> >>> The combination of enter on accept, with the current behavior to select >>> the first completion suggestion by default = trouble. For example: >>> >>> 1. Type "printOn: aStream"... pretty common method start >>> 2. Hit enter to go to the next line >>> >>> You will now have "printOn: MCDataStream" WTF!! I get burned by this >>> pretty regularly and it's annoying. I'm not sure what the fix should be... >>> probably no default selection in the suggestion menu, but possibly only >>> when enter on accept is enabled (t would require an extra key press to >>> complete and when do you ever type a tab in the middle of a line?) >> >> >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > -- Best regards, Igor Stasenko.

April 4, 2013