[UPDATES] 57 for Squeak3.7alpha

Ned Konz ned at bike-nomad.com
Sat Mar 6 02:10:11 UTC 2004


On Friday 05 March 2004 3:36 pm, Doug Way wrote:
> Actually, it looks like the update stream problem is a bit more
> serious... if you start with a 5707 or earlier alpha image, and load
> updates, it will stop at 5764 even if there are more updates in the
> stream after that.  Kind of makes sense that that would happen, since
> the UI process is being terminated.
>
> To see this in action, file in the attached seeInternalUpdates-dew.cs to
> see the internal/test update stream, where I've added an additional test
> update 5765, and then load updates (by selecting "SqC Internal
> Updates*").  The updates stop at 5764 since the UI process is terminated
> (it doesn't even redraw the screen).  Then you have to go re-fetch
> updates again to proceed, click past the "Sorry that name is already
> used" dialog, to get up to 5765.
>
> I think we should probably try to avoid this.  Here are some possible
> solutions:
>
> 1. Re-do the postscript of 5764GenieRemoval-nk so that it no longer does
> a "Project spawnNewProcessAndTerminateOld: true".  Is there any other
> way that the appropriate cleanup can happen for this changeset besides
> killing the UI process?  I don't think any previous updates have ever
> killed the UI process.

I'll take a look at it.

> 2. Somehow change the behavior of the update stream loading so that it
> spawns a separate process for each update, so that it will still
> continue on even if an update kills its UI process.  I'm not sure if
> this is easily doable.
>
> 3. Other solutions?

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE



More information about the Squeak-dev mailing list