Hi Michael -

No reason to be apologetic. We always keep learning more about the 
system. Even I learn new stuff every day (see the discussion about the 
traits problem this morning :-) Thanks for your help and keep it up!

Cheers,
   - Andreas

Michael Perscheid wrote:
> Hello ---,
> 
> Sorry, it was my fault to implement this idea without knowing this option. During the development of the two mentioned issues, I recognized that after disabling the Monticello preference #logToFile all log events will be stored within a Transcript. For that reason, I have discarded my workspace idea and extended this existing feature. If the #logToFile preference is disabled and no Transcript window is already open, I will open a new window and all update log events will be displayed in the new opened Transcript. You can find the current changes in the inbox (Collections-mpe.290 (add a helper method to count Transcript instances) and MonticelloConfigurations-mpe.74 (extend #log method to open a new Transcript window if no other is already existent)). 
> 
> Best regards,
> Michael
> 
> On 02.02.2010, at 04:08, David T. Lewis wrote:
> 
>> On Mon, Feb 01, 2010 at 06:58:01PM -0800, Andreas Raab wrote:
>>> Folks -
>>>
>>> Just as an FYI, I'm going to move this submission out of the inbox and 
>>> into treated because there is an issue with its interplay with the 
>>> MCConfiguration>>logToFile preference. The code breaks if logToFile is 
>>> off and it's not clear to me how one would reconcile the two preferences 
>>> (i.e., whether turning on showUpdatesinWorkspace should automatically 
>>> enable logToFile etc).
>> It seems like a good idea, although it did not seem to display the
>> correct update information when I tried it, presumably for the reasons
>> mentioned above.
>>
>>> I'd encourage a resubmission with those two topics addressed.
>> +1
>>
>>> Cheers,
>>>  - Andreas
>>>
>>> -------- Original Message --------
>>> Subject: 	System-mpe.241.mcz
>>> Date: 	Thu, 28 Jan 2010 15:27:05 +0000
>>> From: 	<Squeak Releases>
>>>
>>>
>>>
>>> Open a workspace with current update information after trunk updates are
>>> completed. (Preference to disable this feature is included-category
>>> #updates)
> 
> 
>