On 16.08.2009, at 22:35, Ian Trudel wrote:

> 2009/8/15 Andreas Raab <andreas.raab at gmx.de>:
>> Ian Trudel wrote:
>>>
>>> Editing the workspace doesn't produce a change set nor monticello
>>> recognize the change. I am not exactly sure how to push this  
>>> change in
>>> a monticello way. If you give me quick instructions, I will be  
>>> glad to
>>> do it.
>>
>> One of the weaknesses of Monticello. I'd recommend adding a menu  
>> entry in
>> the help menu (or reusing the "about this system..." entry) to put  
>> up a
>> workspace with the proper text. Then you can construct the text via:
>>
>> text := 'Here goes the red bold text.!
>> ]style[(14 3 1 4 6)f1,f1cred;,f1,f1b,f1!' readStream nextChunkText.
>> (Workspace new contents: text) openLabel: 'About this image'.
>>
>> To create the formatting for the text, simply inspect a workspace and
>> execute:
>>
>> String streamContents: [:s| s nextChunkPutWithStyle: model contents].
>>
>> This should do the trick.
>
> Now everything seems clear. My first thought was to save an image,
> which isn't gonna cut it with Monticello. What you propose is to add a
> button to open a new window, rather than providing a trunk image with
> the license notice already present. It doesn't feel quite right.
> Wouldn't it be possible to save a project and upload it to a
> repository? Or, perhaps, we should have a container class to prepare
> the trunk image, where a project could be stored.


Add it to a subclass of ReleaseBuilder. This is run to produce a  
release image from a developer image. For example, for the Etoys  
release we pre-load a couple of projects, including the project first  
visible when starting up an image.

- Bert -