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.