Hu Stef,

On Thu, Sep 24, 2015 at 11:45 AM, stepharo <stepharo@free.fr> wrote:

Guys

may be you do not understand or I'm too stupid.
My point is what are the preconditions (tools loaded in the system) that DummyUIManager should have.
I thought that DummyUIManager (which should not be morphic else I do not understand what is
MorphicUIManager) was for a system without a Morphic UI. So how it is possible that a system without
UI could report error using a UI tool?

1. The object referred to by the Transcript variable *is not necessarily* a UI tool.�� It may be headless and have no UI component; it may send output ti stdout or a file or... There is no assumption in DummyUIManager's use that Transcript is a UI component.

2. In testing DummyUIManager it may indeed be useful to have DummyUIManager output to a GUI transcript window.

HTH

Stef

Le 23/9/15 11:16, stepharo a ��crit :

Hi

I have the impression that some references to Transcript should be rewritten as File stdout

For example

DummyUIManager>>unhandledErrorDefaultAction: anException

�� Transcript show: '*** EXCEPTION ***'; cr.
�� Transcript show: anException; cr.
�� Transcript show: (thisContext stack first: (20 min: thisContext stack size)); cr.
�� anException isResumable ifTrue: [ anException resume ]

Stef

_,,,^..^,,,_

best,��Eliot