January 2014 - Pharo-dev - lists.pharo.org

Advanced Reflection in Pharo

by btc＠openinworld.com

Jan. 9, 2014

Re: [Pharo-dev] Spotlight Demo

by Sebastian Sastre

BTW I want to let you know that I love the insensitive search It makes it so much valuable (by reducing assumptions on how much the user should know apriori) I'ts a nice little bit of the OS X experience bring to the smalltalk image fantastic On Dec 30, 2013, at 12:23 PM, Sean DeNigris <sean(a)clipperadams.com> wrote: > I needed an entry completion with groups, like Mac's Spotlight. While I was at it, I figured it would also be useful as a UI for the existing Spotlight. So I made a SpotlightMorph, which is a very Mac-like stand-alone Morph, which is a textField + results morph, and an adaptor for EntryCompetion, SpotlightEntryCompletion, which can be passed to #entryCompletion: > > A short screencast will be available at https://vimeo.com/82953583 in about 45 minutes. > > And here's a screenshot for the impatient ;) > > <Screen Shot 2013-12-30 at 9.23.02 AM.png> > > To load (tested in Pharo 2.0 latest): > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > package: 'Spotlight'; > load. > > Then try: > SpotlightCompletionExample open. > or > SpotlightMorphExample exampleFileSearch. > or > SpotlightMorphExample exampleSmalltalkSearch.

Jan. 9, 2014

Re: [Pharo-dev] Do you want to accept???????? Discard???????

by Nicolai Hess

I made a new bug report, not for removing the question dialog but for fixing the bug that it is uncloseable. 12605 <https://pharo.fogbugz.com/default.asp?12605> promptForCancel is sometimes unclosable 2014/1/9 Igor Stasenko <siguctua(a)gmail.com> > > > > On 9 January 2014 14:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 09 Jan 2014, at 13:59, kilon alios <kilon.alios(a)gmail.com> wrote: >> >> > yes this lead to endless debate, but I think this is good because we >> see diffirent ways into looking into things. I have to admit till today I >> never expected that someone would be against confirm dialogs to such extend >> of wanting them to be removed completely, but I can see now that for people >> that dont make mistakes or they rather live with these mistakes would >> prefer a non confirmation approach. Its good to discuss these things >> because next time I will try to "fix" something I will try to do it in a >> way that pleases most people and not interrupting their workflow. >> > >> > And its endless because people prefer diffirent things, and thats ok. >> Opinions should be expressed and be respected. Opinions matter to make >> software better . Afterall software is made to please people by doing the >> things they want . No software of course is perfect. :) >> > >> > I completely respect Igor's opinion. And Igor its great you have worked >> on these things and thank you :) You should promote your work I think >> progress should be more carefully logged so we can all appreciate the work >> that goes inside pharo :) >> > >> >> A editor key combination that looses code because is does not support >> undo is *wrong*. Completely and utterly *wrong*. >> >> > Crippling the feature is *wrong*. Completely and utterly *wrong*. > As we all agreed , the proper fix to cmd-l problem is make it undoable. > An *improper* fix is put warnings everywhere. Warnings do not prevent from > mistakes, > they just do things worse at times. > That's all what wanted to say. > > >> >> Marcus >> > > > > -- > Best regards, > Igor Stasenko. >

Jan. 9, 2014

Re: [Pharo-dev] [Pharo3] Issues "for review" and "for integration" empy

by Esteban Lorenzano

give me 15â ;) On 09 Jan 2014, at 14:01, Marcus Denker <marcus.denker(a)inria.fr> wrote: > â¦ so we finally managed to have no issues anymore that are > -> fix review needed + pre-check by the monkey > -> fix to integrate > > Wow.. that never happened before ;-) > > Marcus

Jan. 9, 2014

Re: [Pharo-dev] CI server account creation

by Christophe Demarey

Hello Alfredo, Le 8 janv. 2014 Ã 23:58, Alfredo Sanzo a Ã©crit : > Hello! > > I am trying to create an account for the CI server and I have bumped into several links and posts to this list and now that I've asked for help I've finally understood the process (I think). > My question is... Can we have this written somewhere? (and corrected, if I'm wrong :) ) > > "Steps to create a new user: > a) Sign up for a user here: https://ci.inria.fr/users/new > It gets processed manually, so you have to wait until your account is activated for you. => not true. There is no manual validation. Once you get registered, ci.inria.fr send you an email to validate your account. You need to click on the provided link. > b) Go to: https://ci.inria.fr/project and look for pharo-contribution. Request to join it. (it also gets processed manually) Yes, an admin of this project has to accept the join request. > c) Ask in pharo-dev(a)lists.pharo.org to be made an Admin, because if not you won't be able to create a Job. Also true. I updated Jenkins to add more permissions to members. All pharo-contibution members are now allowed to manage jobs. > " > > I see that Pharo-Contribution page redirects here: > https://ci.inria.fr/pharo-contribution/job/JobTemplate/ > Can we have that step 1 updated with what I wrote here? Good idea. Done! > --------------------- > Oh, and I can't get through part a) yet.... Apparently no one is accepting my user... Can somebody help? Maybe you should check your spams. If you cannot find the account activation email, tell me. I can force the account activation. Regards, Christophe.

Jan. 9, 2014

Re: [Pharo-dev] Do you want to accept???????? Discard???????

by Goubier Thierry

But the best effect is when the place looks dangerous (visibly very tight curve on entry) and is not that dangerous (opening on exit). The reverse is a bit more 'interesting' : gentle, easy curve on entry tightening up fast :) I like the 'interesting' on the roads I know well :P Thierry Le 09/01/2014 14:29, Esteban A. Maringolo a Ã©crit : >>From time to time, a slippery road warning sign is good even for the > best driver. > > > Esteban A. Maringolo > > > 2014/1/9 Igor Stasenko <siguctua(a)gmail.com>: >> >> >> >> On 9 January 2014 14:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>> On 09 Jan 2014, at 13:59, kilon alios <kilon.alios(a)gmail.com> wrote: >>> >>>> yes this lead to endless debate, but I think this is good because we see >>>> diffirent ways into looking into things. I have to admit till today I never >>>> expected that someone would be against confirm dialogs to such extend of >>>> wanting them to be removed completely, but I can see now that for people >>>> that dont make mistakes or they rather live with these mistakes would prefer >>>> a non confirmation approach. Its good to discuss these things because next >>>> time I will try to "fix" something I will try to do it in a way that pleases >>>> most people and not interrupting their workflow. >>>> >>>> And its endless because people prefer diffirent things, and thats ok. >>>> Opinions should be expressed and be respected. Opinions matter to make >>>> software better . Afterall software is made to please people by doing the >>>> things they want . No software of course is perfect. :) >>>> >>>> I completely respect Igor's opinion. And Igor its great you have worked >>>> on these things and thank you :) You should promote your work I think >>>> progress should be more carefully logged so we can all appreciate the work >>>> that goes inside pharo :) >>>> >>> >>> A editor key combination that looses code because is does not support undo >>> is *wrong*. Completely and utterly *wrong*. >>> >> >> Crippling the feature is *wrong*. Completely and utterly *wrong*. >> As we all agreed , the proper fix to cmd-l problem is make it undoable. >> An *improper* fix is put warnings everywhere. Warnings do not prevent from >> mistakes, >> they just do things worse at times. >> That's all what wanted to say. >> >>> >>> >>> Marcus >> >> >> >> >> -- >> Best regards, >> Igor Stasenko. > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Jan. 9, 2014

Re: [Pharo-dev] Do you want to accept???????? Discard???????

by Esteban A. Maringolo

>From time to time, a slippery road warning sign is good even for the best driver. Esteban A. Maringolo 2014/1/9 Igor Stasenko <siguctua(a)gmail.com>: > > > > On 9 January 2014 14:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> On 09 Jan 2014, at 13:59, kilon alios <kilon.alios(a)gmail.com> wrote: >> >> > yes this lead to endless debate, but I think this is good because we see >> > diffirent ways into looking into things. I have to admit till today I never >> > expected that someone would be against confirm dialogs to such extend of >> > wanting them to be removed completely, but I can see now that for people >> > that dont make mistakes or they rather live with these mistakes would prefer >> > a non confirmation approach. Its good to discuss these things because next >> > time I will try to "fix" something I will try to do it in a way that pleases >> > most people and not interrupting their workflow. >> > >> > And its endless because people prefer diffirent things, and thats ok. >> > Opinions should be expressed and be respected. Opinions matter to make >> > software better . Afterall software is made to please people by doing the >> > things they want . No software of course is perfect. :) >> > >> > I completely respect Igor's opinion. And Igor its great you have worked >> > on these things and thank you :) You should promote your work I think >> > progress should be more carefully logged so we can all appreciate the work >> > that goes inside pharo :) >> > >> >> A editor key combination that looses code because is does not support undo >> is *wrong*. Completely and utterly *wrong*. >> > > Crippling the feature is *wrong*. Completely and utterly *wrong*. > As we all agreed , the proper fix to cmd-l problem is make it undoable. > An *improper* fix is put warnings everywhere. Warnings do not prevent from > mistakes, > they just do things worse at times. > That's all what wanted to say. > >> >> >> Marcus > > > > > -- > Best regards, > Igor Stasenko.

Jan. 9, 2014

Re: [Pharo-dev] Do you want to accept???????? Discard???????

by Sebastian Sastre

On Jan 9, 2014, at 5:50 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > I don't think we have to discuss what would be the better alternative. People have different preferences and different workflows. > Why don't we make a setting for this? Something like "Codepanes can discard edits", and let Nautilus and other > codepanes behave like the Workspace (I remember a time when workspaces asked too before discarding edits) If the default is protective, this setting idea will get the best of both worlds Why that default? Because your design is optimist and thinks that a fresh Pharo is the first open on an user that never has seen one before And you protect their experience with the best you can give

Jan. 9, 2014

Re: [Pharo-dev] Do you want to accept???????? Discard???????

by Igor Stasenko

On 9 January 2014 14:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 09 Jan 2014, at 13:59, kilon alios <kilon.alios(a)gmail.com> wrote: > > > yes this lead to endless debate, but I think this is good because we see > diffirent ways into looking into things. I have to admit till today I never > expected that someone would be against confirm dialogs to such extend of > wanting them to be removed completely, but I can see now that for people > that dont make mistakes or they rather live with these mistakes would > prefer a non confirmation approach. Its good to discuss these things > because next time I will try to "fix" something I will try to do it in a > way that pleases most people and not interrupting their workflow. > > > > And its endless because people prefer diffirent things, and thats ok. > Opinions should be expressed and be respected. Opinions matter to make > software better . Afterall software is made to please people by doing the > things they want . No software of course is perfect. :) > > > > I completely respect Igor's opinion. And Igor its great you have worked > on these things and thank you :) You should promote your work I think > progress should be more carefully logged so we can all appreciate the work > that goes inside pharo :) > > > > A editor key combination that looses code because is does not support undo > is *wrong*. Completely and utterly *wrong*. > > Crippling the feature is *wrong*. Completely and utterly *wrong*. As we all agreed , the proper fix to cmd-l problem is make it undoable. An *improper* fix is put warnings everywhere. Warnings do not prevent from mistakes, they just do things worse at times. That's all what wanted to say. > > Marcus > -- Best regards, Igor Stasenko.

Jan. 9, 2014

Re: [Pharo-dev] Do you want to accept???????? Discard???????

by Igor Stasenko

On 9 January 2014 13:58, kilon alios <kilon.alios(a)gmail.com> wrote: > yes this lead to endless debate, but I think this is good because we see > diffirent ways into looking into things. I have to admit till today I never > expected that someone would be against confirm dialogs to such extend of > wanting them to be removed completely, but I can see now that for people > that dont make mistakes or they rather live with these mistakes would > prefer a non confirmation approach. Its good to discuss these things > because next time I will try to "fix" something I will try to do it in a > way that pleases most people and not interrupting their workflow. > > Thanks. I'm glad i've been heard. > And its endless because people prefer diffirent things, and thats ok. > Opinions should be expressed and be respected. Opinions matter to make > software better . Afterall software is made to please people by doing the > things they want . No software of course is perfect. :) > > > I completely respect Igor's opinion. And Igor its great you have worked on > these things and thank you :) You should promote your work I think progress > should be more carefully logged so we can all appreciate the work that goes > inside pharo :) > > > On Thu, Jan 9, 2014 at 2:43 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> >> On 09 Jan 2014, at 12:37, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> >> >> >> On 9 January 2014 12:13, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> >>> >>> >>> On 9 January 2014 11:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>>> >>>> On 09 Jan 2014, at 11:11, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> >>>> I was the one that worked on CMD+L dialog. I posted my slice here and >>>> it was discussed. I tried to implement undo, but trying to understand undo >>>> was a pain in the ass. >>>> >>>> >>>> I reviewed it and you are not to blame: A key combination that *loses >>>> code* is not acceptable, and as we discussed in the past, this >>>> change was needed and good. >>>> >>>> Yes, and i agreed on that. >>> My only complaint is that instead of making things work, we reversed it >>> and made things even worse. >>> >>> >>>> The people who use the (undocumented!) cmd-L can easily get rid of the >>>> warning by implementing Undo. >>>> >>>> how many modern editors document that pressing home key will move >>> cursor to beginning of line? or pressing cmd-v will paste things from >>> clipboard? >>> i do not think this is a good criteria to disable feature(s) only >>> because they either not documented properly or that someone has no idea it >>> exists. >>> >> >> yes, to be fair, the Cmd-L was not disabled, but *crippled* , enough that >> its usefulness become very low. >> because before i knew that i can type any garbage in any editor window >> and undo all with single keystroke, >> and now i have to be interrupted with yes/no popup. >> >> Can i ask, why consoles do not ask you are you sure you want to face >> consequences of you pressed ctrl-c? >> >> >> Undo works for ctrl-c. Fo ctrl-l it does not. >> >> (I really wonder why we have this dissuasion: It was already last time >> said that if the key combination removes >> code *without a change to get it back* it needs to warn, if people do not >> like the warning they should >> a) implement undo for ctrl-l >> b) remove the warning. >> >> Marcus >> > > -- Best regards, Igor Stasenko.

Jan. 9, 2014