Hi people!
I think I missed the announcement of the SM upgrade... :) Anyway, I posted about the improvements in this release in an earlier post:
http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-November/09 8168.html
...but essentially this is what you need to know:
- When you do "update map from the net" your client will notice that the server (map.squeak.org) is running SM2.1 and it will ask you to upgrade your image. If you don't it can't update the map.
- While upgrading it will start blabbering about Monticello vs MCInstaller for upgrading the loader, pick Monticello. Using MCInstaller might work too, but I haven't looked carefully.
- Eventually it will reopen the loader and all should be fine. The loader doesn't contain much any change at all so you can't really see it is version 2.1. :)
If you are running multiple images in the same directory (as most of us probably do) and you upgrade one of them to SM 2.1 then you will end up with a map snapshot version 2.1 in the "/sm" dir.
If you now start *another* non updated image and do "upgrade from net" in the SqueakMap Package Loader it will end up asking about what class to convert to yaddayadda... This is a "problem" I will try to fix in the next SM release (it doesn't detect that a new snapshot is already on disk in the new format) but right now you need to press alt-. and then manually execute in a workspace:
SMSqueakMap bootStrap
...to trigger the upgrade and then it should work as above.
regards, Göran
PS. The main difference in this release from the client perspective is that it now has a fallback on a server cache so the problem with packages not being online should hopefully be a problem of the past.
goran@krampe.se wrote:
- Eventually it will reopen the loader and all should be fine. The
loader doesn't contain much any change at all so you can't really see it is version 2.1. :)
Why is the SMLoader a sub class of SystemWindow and not Model. I made a quick hack to change that and I got SMLoader window colors to work again. WOHOO! Karl
Hi!
karl karl.ramberg@chello.se wrote:
goran@krampe.se wrote:
- Eventually it will reopen the loader and all should be fine. The
loader doesn't contain much any change at all so you can't really see it is version 2.1. :)
Why is the SMLoader a sub class of SystemWindow and not Model.
Well, I felt it was simpler. The zip archive viewer use the same approach.
I made a quick hack to change that and I got SMLoader window colors to work again. WOHOO!
And if I am not mistaken the colors do work in 3.8. But I am not picky, I can change.
Karl
regards, Göran
Suggestion: would it be an idea to push an update into the 3.8 stream that takes care of the upgrade? If you fetch the latest 3.8 image currently, you have to sit through the upgrade on the first SM access...
Cees De Groot cdegroot@gmail.com wrote:
Suggestion: would it be an idea to push an update into the 3.8 stream that takes care of the upgrade? If you fetch the latest 3.8 image currently, you have to sit through the upgrade on the first SM access...
I would agree - and we could also see if there are a few other "riskless" fixes we would like to bundle up as well. 3.8 will probably be the preferred deployment platform for a bit of time. And note that this is not criticism from my side - I am actually thrilled that 3.9 is finally taking some larger steps. :)
regards, Göran
On 10-Jan-06, at 10:04 PM, goran@krampe.se wrote:
Cees De Groot cdegroot@gmail.com wrote:
Suggestion: would it be an idea to push an update into the 3.8 stream that takes care of the upgrade? If you fetch the latest 3.8 image currently, you have to sit through the upgrade on the first SM access...
I would agree - and we could also see if there are a few other "riskless" fixes we would like to bundle up as well. 3.8 will probably be the preferred deployment platform for a bit of time. And note that this is not criticism from my side - I am actually thrilled that 3.9 is finally taking some larger steps. :)
There are at least a couple of updates slowly molding in the queue that are crucial to VMMaker.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: FSE: Fake Serious Error
Tim
could you tell us what are the changes that you need to get in 3.9? My time is right now getting too tight. We will try to get in beta before 15 of february.
Stef
On 11 janv. 06, at 18:40, tim Rowledge wrote:
On 10-Jan-06, at 10:04 PM, goran@krampe.se wrote:
Cees De Groot cdegroot@gmail.com wrote:
Suggestion: would it be an idea to push an update into the 3.8 stream that takes care of the upgrade? If you fetch the latest 3.8 image currently, you have to sit through the upgrade on the first SM access...
I would agree - and we could also see if there are a few other "riskless" fixes we would like to bundle up as well. 3.8 will probably be the preferred deployment platform for a bit of time. And note that this is not criticism from my side - I am actually thrilled that 3.9 is finally taking some larger steps. :)
There are at least a couple of updates slowly molding in the queue that are crucial to VMMaker.
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: FSE: Fake Serious Error
squeak-dev@lists.squeakfoundation.org