Smalltalk › Squeak › Squeak - Dev

Transcript>>show: slowness.

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Igor Stasenko

Transcript>>show: slowness.

I know that Transcript is slow :)
But i found more disturbing problem.
I put 'Transcript show:' in Canvas code, for tracing different drawing
commands, and found that Transcript morph updates itself directly
after receiving this command.

So, each time you sending #show: it redraws morph window. I think this
is why Transcript is slow at first place. And also it makes Transcript
useless for tracing different drawing commands ( because some of them
can cause infinite recursion).

I want to ask, if someone knows, why transcript (or maybe underlaying
morphs) designed in such manner, that it forcibly updates itself on
screen at each #show: message sent. And also, maybe someone knows how
make fast and effective fix to this? I don't think that updating
transcript window contents immediately after something putted into it
is critical.
A more effective would be to simply mark transcript window as dirty,
and then during next world update cycle is will automatically get
updated.

--
Best regards,
Igor Stasenko AKA sig.

Gary Chambers-4

RE: Transcript>>show: slowness.

Workaound is to use #nextPutAll: then do a show: '' when you are ready...

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On
> Behalf Of Igor Stasenko
> Sent: 09 September 2007 2:12 pm
> To: The general-purpose Squeak developers list
> Cc: Squeak's User Interface
> Subject: Transcript>>show: slowness.
>
>
> I know that Transcript is slow :)
> But i found more disturbing problem.
> I put 'Transcript show:' in Canvas code, for tracing
> different drawing commands, and found that Transcript morph
> updates itself directly after receiving this command.
>
> So, each time you sending #show: it redraws morph window. I
> think this is why Transcript is slow at first place. And also
> it makes Transcript useless for tracing different drawing
> commands ( because some of them can cause infinite recursion).
>
> I want to ask, if someone knows, why transcript (or maybe underlaying
> morphs) designed in such manner, that it forcibly updates
> itself on screen at each #show: message sent. And also, maybe
> someone knows how make fast and effective fix to this? I
> don't think that updating transcript window contents
> immediately after something putted into it is critical. A
> more effective would be to simply mark transcript window as
> dirty, and then during next world update cycle is will
> automatically get updated.
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>

Bert Freudenberg

Re: Transcript>>show: slowness.

In reply to this post by Igor Stasenko

On Sep 9, 2007, at 15:11 , Igor Stasenko wrote:

> I want to ask, if someone knows, why transcript (or maybe underlaying
> morphs) designed in such manner, that it forcibly updates itself on
> screen at each #show: message sent.

So that you can see log entries even if you are in a longer
computation that blocks the UI.

- Bert -