[Pharo-project] Slow text input?
Hi all, I opened an old 1.2.1 image and text input was incredibly slow. I tried the latest one click and text input is very slow and jerky. Has anyone else ever experienced something like this on a Mac? Its really frustrating. Every pharo image I have is seemingly unusable. -Sean-
Hi all,
I opened an old 1.2.1 image and text input was incredibly slow.
I tried the latest one click and text input is very slow and jerky.
Has anyone else ever experienced something like this on a Mac? Its really frustrating. Every pharo image I have is seemingly unusable.
Never say such things about Pharo here!!! Be aware of ProfStef. Too much bad energy! Think positive. Say: "Pharo is brilliant, maybe sometimes a bit slow!" Ok?
On Mon, Nov 14, 2011 at 9:52 PM, Guido Stepken <gstepken@googlemail.com>wrote:
Hi all,
I opened an old 1.2.1 image and text input was incredibly slow.
I tried the latest one click and text input is very slow and jerky.
Has anyone else ever experienced something like this on a Mac? Its really frustrating. Every pharo image I have is seemingly unusable.
Never say such things about Pharo here!!! Be aware of ProfStef. Too much bad energy! Think positive. Say: "Pharo is brilliant, maybe sometimes a bit slow!"
Ok?
This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
How should they notice? At 2 Gigaherz CPU power even the worst and totally messed up code seems to run fine!!! :-) And when they build up simple web servers with seaside on pharo, they use to use 5 Images on three machines with a load balancer in between and a "wakeup daemon" for the case, that one or more pharo images die a sudden death due to "overload at perhaps 50 simultaneous clients" This is modern software engineering! Have fun! Guido Stepken Am 15.11.2011 um 04:02 schrieb Sean Allen <sean@monkeysnatchbanana.com>:
On Mon, Nov 14, 2011 at 9:52 PM, Guido Stepken <gstepken@googlemail.com> wrote:
Hi all,
I opened an old 1.2.1 image and text input was incredibly slow.
I tried the latest one click and text input is very slow and jerky.
Has anyone else ever experienced something like this on a Mac? Its really frustrating. Every pharo image I have is seemingly unusable.
Never say such things about Pharo here!!! Be aware of ProfStef. Too much bad energy! Think positive. Say: "Pharo is brilliant, maybe sometimes a bit slow!"
Ok?
This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
On 15 November 2011 05:02, Sean Allen <sean@monkeysnatchbanana.com> wrote:
On Mon, Nov 14, 2011 at 9:52 PM, Guido Stepken <gstepken@googlemail.com> wrote:
Hi all,
I opened an old 1.2.1 image and text input was incredibly slow.
I tried the latest one click and text input is very slow and jerky.
Has anyone else ever experienced something like this on a Mac? Its really frustrating. Every pharo image I have is seemingly unusable.
Never say such things about Pharo here!!! Be aware of ProfStef. Too much bad energy! Think positive. Say: "Pharo is brilliant, maybe sometimes a bit slow!"
Ok?
Guido, what is your problem with Pharo? If you don't like it, nobody forcing you to use it. If you want to use it, but it doesn't meets your high standards, feel free to help improve it. Trolling won't change anything.
This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
Can you provide more details? What is VM version you using, what is OS version etc. -- Best regards, Igor Stasenko.
This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
Can you provide more details? What is VM version you using, what is OS version etc.
Mac OS X 10.6.8 I deleted the vm I had. Tried various one clicks. 1.2.1 & latest 1.3 ( downloaded an hour ago ) and both have the issue. I deleted the vm I had for non one click images and am going to trying installing a new one to see if that helps.
Sean, On 15 Nov 2011, at 04:39, Sean Allen wrote:
Mac OS X 10.6.8
I deleted the vm I had. Tried various one clicks.
1.2.1 & latest 1.3 ( downloaded an hour ago )
and both have the issue.
I deleted the vm I had for non one click images and am going to trying installing a new one to see if that helps.
This is _definitively_ not normal, many Pharo developers are on Mac, using it all day long, this would unbearable for any of us. This must be a local problem. Do you have a chance to try this on some other mac so that you have a reference for yourself ? Sven
On Tuesday, November 15, 2011 at 4:14 AM, Sven Van Caekenberghe wrote:
Sean,
On 15 Nov 2011, at 04:39, Sean Allen wrote:
Mac OS X 10.6.8
I deleted the vm I had. Tried various one clicks.
1.2.1 & latest 1.3 ( downloaded an hour ago )
and both have the issue.
I deleted the vm I had for non one click images and am going to trying installing a new one to see if that helps.
This is _definitively_ not normal, many Pharo developers are on Mac, using it all day long, this would unbearable for any of us.
This must be a local problem. Do you have a chance to try this on some other mac so that you have a reference for yourself ?
I used pharo for every day development for 2 years so ya, I know this isn't normal. Unfortunately, I'm left with the situation where something is causing this but I have no idea what and it crosses image versions. If no one else has ever had the same local problem, I have a long road to figure this out most likely. Sean hoping someone has experienced this before and knows a solution.
Am 15.11.2011 um 04:39 schrieb Sean Allen:
This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
Can you provide more details? What is VM version you using, what is OS version etc.
Mac OS X 10.6.8
I deleted the vm I had. Tried various one clicks.
1.2.1 & latest 1.3 ( downloaded an hour ago )
and both have the issue.
I deleted the vm I had for non one click images and am going to trying installing a new one to see if that helps.
Sean, do you have another machine handy? In this cases it might be a good idea to make a quick check with the same image on another machine. Norbert
On Tuesday, November 15, 2011 at 4:19 AM, Norbert Hartl wrote:
Am 15.11.2011 um 04:39 schrieb Sean Allen:
This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
Can you provide more details? What is VM version you using, what is OS version etc.
Mac OS X 10.6.8
I deleted the vm I had. Tried various one clicks.
1.2.1 & latest 1.3 ( downloaded an hour ago )
and both have the issue.
I deleted the vm I had for non one click images and am going to trying installing a new one to see if that helps.
Sean,
do you have another machine handy? In this cases it might be a good idea to make a quick check with the same image on another machine.
Norbert
I do have another Mac I could try one of the images on. I'm pretty sure it would work on another and this is an issue on my machine. -Sean-
On Tue, Nov 15, 2011 at 4:19 AM, Norbert Hartl <norbert@hartl.name> wrote:
Am 15.11.2011 um 04:39 schrieb Sean Allen:
This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
Can you provide more details? What is VM version you using, what is OS version etc.
Mac OS X 10.6.8
I deleted the vm I had. Tried various one clicks.
1.2.1 & latest 1.3 ( downloaded an hour ago )
and both have the issue.
I deleted the vm I had for non one click images and am going to trying installing a new one to see if that helps.
Sean,
do you have another machine handy? In this cases it might be a good idea to make a quick check with the same image on another machine.
Norbert
Ya everything is indeed fine on another Mac ( older model ) running 10.6.8 I copied over a 1.2.1 one click that I had been messing around with a few months back and its very usable.
On 15 Nov 2011, at 14:03, Sean Allen wrote:
Ya everything is indeed fine on another Mac ( older model ) running 10.6.8
I copied over a 1.2.1 one click that I had been messing around with a few months back and its very usable.
That is indeed very annoying, Sean. Now you have to find out what is wrong with your main Mac. Is there anything else that works slower than usual ? Can you remember anything that you did that might have had this effect ? Any strange background things running ? I hope you can find the cause. Sven
On Tuesday, November 15, 2011 at 8:28 AM, Sven Van Caekenberghe wrote:
On 15 Nov 2011, at 14:03, Sean Allen wrote:
Ya everything is indeed fine on another Mac ( older model ) running 10.6.8
I copied over a 1.2.1 one click that I had been messing around with a few months back and its very usable.
That is indeed very annoying, Sean.
Now you have to find out what is wrong with your main Mac.
Is there anything else that works slower than usual ? Can you remember anything that you did that might have had this effect ? Any strange background things running ?
I hope you can find the cause.
I found the cause with a key remapper I use. I had tested it a couple weeks ago by 'disabling it' which apparently is rather different than having it not in memory at all. Thanks for the help and no so much for the thread hijacking.
I found the cause with a key remapper I use. I had tested it a couple weeks ago by 'disabling it' which apparently is rather different than having it not in memory at all.
In pharo or on mac? You think that this is something that change the event fed to the VM?
Thanks for the help and no so much for the thread hijacking.
Guido, what is your problem with Pharo? If you don't like it, nobody forcing you to use it.
Nobody forces me.
If you want to use it, but it doesn't meets your high standards, feel free to help improve it. Trolling won't change anything.
I'm not trolling. I am tester. It usually takes ... hmmm ... 10 Minutes of klicking around a bit, until Pharo freezes. Last time it happened 2 days ago, all patches applied. Have fun, Guido Stepken
Em 15/11/2011 01:48, Guido Stepken < gstepken@googlemail.com > escreveu:
Guido, what is your problem with Pharo? If you don't like it, nobody forcing you to use it. Nobody forces me. If you want to use it, but it doesn't meets your high standards, feel free to help improve it. Trolling won't change anything. I'm not trolling. I am tester. It usually takes ... hmmm ... 10 Minutes of klicking around a bit, until Pharo freezes. Last time it happened 2 days ago, all patches applied.
Guido, Your post above can be analysed in several ways. I'll concede for start that Igor's first impression /might/ be wrong and your assertion "I'm not trolling." is sincere. However, the rest of the post evaluates to the following: If you really believe in your second affirmation "I am tester." there are some possible explanations: 1) You're delusional about your testing skills and need to improve them, learning how to give us reproducible examples with accurate reports so your "tests" mean something; or 2) You keep poking the mouse at the world area of a Pharo launched image and when you get bored you declare "a freeze" and come here to tease us. For the first I'd advise you to learn to do tests which are actionable and post your results here. For the second, make a self assessment on what is the contribution for Pharo, or the craft of programming of your present behaviour in this list.
On 15 November 2011 06:03, <csrabak@bol.com.br> wrote:
Em 15/11/2011 01:48, Guido Stepken < gstepken@googlemail.com > escreveu:
Guido,  what is  your problem  with Pharo? If  you don't  like it, nobody forcing you to use it.  Nobody forces me.  > If you want to use  it, but it doesn't meets your high standards, feel free to help improve it. Trolling won't change anything.  I'm not  trolling. I am  tester. It usually  takes ... hmmm  ... 10 Minutes of klicking around a  bit, until Pharo freezes. Last time it happened 2 days ago, all patches applied.
Guido,
Your post above can be analysed in several ways. I'll concede for start that Igor's first impression /might/ be wrong and your assertion "I'm not trolling." Â is sincere.
However, the rest of the post evaluates to the following: If you really believe in your second affirmation "I am  tester." there are some possible explanations:
1) You're delusional about your testing skills and need to improve them, learning how to give us reproducible examples with accurate reports so your "tests" mean something; or
2) You keep poking the mouse at the world area of a Pharo launched image and when you get bored you declare "a freeze" and come here to tease us.
For the first I'd advise you to learn to do tests which are actionable and post your results here. For the second, make a self assessment on what is the contribution for Pharo, or the craft of programming of your present behaviour in this list.
There's one more option: Yes, Guido is tester. But his test subject(s) is not a software but us, or our reaction. This is the only conclusion which i can draw by reading his posts which doesn't leads to contradiction. :) -- Best regards, Igor Stasenko.
Hey, it's much simpler. I install, i look around what is new, has changed, and the Pharo dies. VM freezes, virtual machine crashes, whatever. So i simply uninstall and wait patiently for the next release. Ok? Guido Stepken Am 15.11.2011 um 05:11 schrieb Igor Stasenko <siguctua@gmail.com>:
On 15 November 2011 06:03, <csrabak@bol.com.br> wrote:
Em 15/11/2011 01:48, Guido Stepken < gstepken@googlemail.com > escreveu:
Guido, what is your problem with Pharo? If you don't like it, nobody forcing you to use it. Nobody forces me. If you want to use it, but it doesn't meets your high standards, feel free to help improve it. Trolling won't change anything. I'm not trolling. I am tester. It usually takes ... hmmm ... 10 Minutes of klicking around a bit, until Pharo freezes. Last time it happened 2 days ago, all patches applied.
Guido,
Your post above can be analysed in several ways. I'll concede for start that Igor's first impression /might/ be wrong and your assertion "I'm not trolling." is sincere.
However, the rest of the post evaluates to the following: If you really believe in your second affirmation "I am tester." there are some possible explanations:
1) You're delusional about your testing skills and need to improve them, learning how to give us reproducible examples with accurate reports so your "tests" mean something; or
2) You keep poking the mouse at the world area of a Pharo launched image and when you get bored you declare "a freeze" and come here to tease us.
For the first I'd advise you to learn to do tests which are actionable and post your results here. For the second, make a self assessment on what is the contribution for Pharo, or the craft of programming of your present behaviour in this list.
There's one more option: Yes, Guido is tester. But his test subject(s) is not a software but us, or our reaction. This is the only conclusion which i can draw by reading his posts which doesn't leads to contradiction. :)
-- Best regards, Igor Stasenko.
Am 15.11.2011 um 05:30 schrieb Guido Stepken:
Hey, it's much simpler. I install, i look around what is new, has changed, and the Pharo dies. VM freezes, virtual machine crashes, whatever.
So i simply uninstall and wait patiently for the next release.
Ok?
It is ok for you. For everyone that would like to use pharo would do it in a more systematic way. The person would probably tell which VM version he uses, which image he downloaded, what he really did and especially what he did when the problem ocurred. And the person would be able to tell if it was a freeze or a crash. As you are not after problem solving but after nagging it seems to work quite ok. Norbert
Guido Stepken
Am 15.11.2011 um 05:11 schrieb Igor Stasenko <siguctua@gmail.com>:
On 15 November 2011 06:03, <csrabak@bol.com.br> wrote:
Em 15/11/2011 01:48, Guido Stepken < gstepken@googlemail.com > escreveu:
Guido, what is your problem with Pharo? If you don't like it, nobody forcing you to use it. Nobody forces me. If you want to use it, but it doesn't meets your high standards, feel free to help improve it. Trolling won't change anything. I'm not trolling. I am tester. It usually takes ... hmmm ... 10 Minutes of klicking around a bit, until Pharo freezes. Last time it happened 2 days ago, all patches applied.
Guido,
Your post above can be analysed in several ways. I'll concede for start that Igor's first impression /might/ be wrong and your assertion "I'm not trolling." is sincere.
However, the rest of the post evaluates to the following: If you really believe in your second affirmation "I am tester." there are some possible explanations:
1) You're delusional about your testing skills and need to improve them, learning how to give us reproducible examples with accurate reports so your "tests" mean something; or
2) You keep poking the mouse at the world area of a Pharo launched image and when you get bored you declare "a freeze" and come here to tease us.
For the first I'd advise you to learn to do tests which are actionable and post your results here. For the second, make a self assessment on what is the contribution for Pharo, or the craft of programming of your present behaviour in this list.
There's one more option: Yes, Guido is tester. But his test subject(s) is not a software but us, or our reaction. This is the only conclusion which i can draw by reading his posts which doesn't leads to contradiction. :)
-- Best regards, Igor Stasenko.
Over remote desktop connections, I have found Pharo to be noticeably slower than Dolphin when similarly disadvantaged. Otherwise, no complaints, but that is on Linux and Windows. With very long methods, I sometimes notice code rendered in black and then again with Shout's coloring. It might be Shout working as designed, or it could be exposing wasted screen updates?? Bill ________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Sean Allen [sean@monkeysnatchbanana.com] Sent: Monday, November 14, 2011 10:02 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Slow text input? On Mon, Nov 14, 2011 at 9:52 PM, Guido Stepken <gstepken@googlemail.com<mailto:gstepken@googlemail.com>> wrote:
Hi all,
I opened an old 1.2.1 image and text input was incredibly slow.
I tried the latest one click and text input is very slow and jerky.
Has anyone else ever experienced something like this on a Mac? Its really frustrating. Every pharo image I have is seemingly unusable.
Never say such things about Pharo here!!! Be aware of ProfStef. Too much bad energy! Think positive. Say: "Pharo is brilliant, maybe sometimes a bit slow!" Ok? This is new. This wasn't happening before. This is happening with images that were fine the last time I opened them in the spring. Something is messed up on my machine. Hoping someone else has gone through this and fixed it.
On 15 Nov 2011, at 20:27, Schwab,Wilhelm K wrote:
With very long methods, I sometimes notice code rendered in black and then again with Shout's coloring. It might be Shout working as designed, or it could be exposing wasted screen updates??
That is on purpose, very long methods are a no go ;-) Sven
Sean this is really strange because we are all on mac and we use the 1.3 daily and it does not have such problems. I mean we plan to build a company around moose and pharo and we are working hard on that so you imagine easily that we would not if we could not edit code. Stef On Nov 15, 2011, at 3:31 AM, Sean T Allen wrote:
Hi all,
I opened an old 1.2.1 image and text input was incredibly slow.
I tried the latest one click and text input is very slow and jerky.
Has anyone else ever experienced something like this on a Mac? Its really frustrating. Every pharo image I have is seemingly unusable.
-Sean-
participants (9)
-
csrabak＠bol.com.br -
Guido Stepken -
Igor Stasenko -
Norbert Hartl -
Schwab,Wilhelm K -
Sean Allen -
Sean T Allen
-
Stéphane Ducasse -
Sven Van Caekenberghe