On Apr 4, 2013, at 7:02 PM, Diego Lont <diego.lont@delware.nl> wrote:
On 4 April 2013 15:45, Esteban Lorenzano <estebanlm@gmail.com> wrote:
really? please, add an issue in the tracker and submit a slice, as everybody else.
calm down, we're just discussing here. I provided code here intentionally for nay-sayers like you to try it and to check if it not breaks something else (your workflow).
Esteban,
Having a new Browser in Pharo 2.0 is a big change. Everyone needs to get used to it. And I agree it is probably a good thing. But ⦠there are some things that worked better in OB that I don't want to loose. There are a lot of people annoyed by how it works nowâ¦. but I think the mailing list is about exchanging arguments not about deciding. So I do not like that you try to end the discussion by shouting: the defaults will not change. So here I will add a new argument.
I'm not closing the discussion. I'm just pointing that the reasons why we took that decision remains more relevant than your argument. And also I'm pointing that you have the settings to adapt to your desired behavior. Finally, I also pointing that if there is something bad or a feature not present (like the coexistence of tab and enter), there is always room to improvement :)
Your argument about other languages is a valid point, but only holds if Smalltalk is similar as other languages. Why does this "enter" annoys me? Because in some cases it replaces my code by garbage. At least when I type a method invocation that does not exist yet, it replaces it by an existing method. And this is repeatable. So when you go back (using backspace and typing it again, because it also adds before the things I typed) and the press enter again, it does the same replacement. So there is a difference here between smalltalk and other languages. When I do test-driven development (that I do a lot), I first write my test, invoking a lot of methods that do not exist yet. I do not do this in another language, because my environment isn't good enough then.
A feeble argument too. We are not talking about a language but about a language's IDE (and yes, I know that Pharo, as any other smalltalk is language+IDE, and you cannot separate them). The IDE should help the developer. The defaults should help the newcomers, and the settings should be available for power users to adapt the IDE to their preferred ways to do things. So, now... I know that completion is working bad, but the "enter" issue is not the problem. I can point several other problems: 1) the most important: the answers are not accurate, and not even close. Yes, it returns symbols starting with your entry, but they are not context aware (the old completion was doing a better job by just arranging results and presenting first the latest things you entered) 2) It offers completions in bad places (like appearing after you put colon and before letting you press space) 3) Some times it changes code intead inserting it, or inserts it in bad places. 4) There are some options users desire that are not present. So... your feedback is valuable, of course, and many many times you are right. But in this case I still thing you are just wrong, and your solution is use the settings. cheers, Esteban