>>> 
>> 
>> The question why to have registry for something what is not necessary.
>> Some applications may  want to remove tools from the image so to place
>> tools support to the kernel is a regression. The only tool that is
>> required for the Kernel now is Transcript for some Compiler messages
>> etc. I think that there is one much better solution - to remove
>> Transcript dependency from the kernel and for such messages to use
>> UIManager (something like #log: or maybe better #logStream).
>> MorphicUIManager then will use Transcript.
>> 
>> -- Pavel
>> 
>> 
> 
> Then it could be (Smalltalk ui crLog:) instead of (Smalltalk tools
> transcript...)
> Or (UIManager deault crLog: ).
> The question is whether there is any interest in replacing a bunch of
> ThisOrThatManagerHandlerOrWhatever by a message send, and dispatch all
> these message to the System (Smalltalk).

Nicolas

This is a good question and we experimenting to find the right answer. 
We should have less as possible reference to classes. 
So that we can replace them easily. 
The experience changing Transcript was not really a good illustration of that 
point
because Transcript is a global and since the class binding is shared in compile 
methods
normally we would not have to recompile everything, but still. 
Now more generally I like the idea of newspeak that we could get the notion of 
from this module 
we pick and access only what we use. 


Stef





Reply via email to