[ANN] 3.9a-7022

hi guys

After this release we will try to integrate the changes of diego (who  
already did a pass) and the fixes for traits.....and we go BETA...
Because we are getting exxxxxxxxhausted.........;)

As usual a fresh and nice image is waiting for you on the ftp site.

Thanks to marcus for most of the integration work.

        Tests for Heap
        Tests for SystemChangeNotifications
        Fix of roel for double event notification when class recategorisation
        0003440: UTF8TextConverter>>nextFromStream: silently truncates input
        0003375: mcz files saved in 3.9 don't load in 3.8
        0003376: mpeg plugin has changes to image to support read from  
buffer versus file
        0000521: [BUG] Button properties Morph need to be fixed or removed.
        0002116: Halo rotation of a true type font throws up a debug window.
        0001608: [BUG][FIX] Morphic: File Selection Dialog
        0003378: Add FloatMathPluginTests class to Tests-VM package/category
        0003377: mpeg plugin has changes to image to support dropping bits  
into an offset into a
                        form so you can write to say Display
        OmniBrowser:
                - format non-local methods (e.g from traits) in italic (does also  
work in images that do not have support for traits)
        0001604: [FIX] [BUG] smoothOrSegmentedPhrase-wiz
        0001200: Outdent/Indent issue if code contains WideStrings
        SUnit: Merged in SUnit extensions by Mercap Software.


Stef

Stéphane Ducasse <[hidden email]> wrote...

>As usual a fresh and nice image is waiting for you on the ftp site.

I notice that when you open a PackageLoader, it has to run through an entire re-load.  Would it be possible to go through this update before releasing?

Thanks
        - Dan

Hi dan

you mean squeakmap?
Yes I would like that but I was confused recently with the exchange  
with goran.
So if goran can tell what to do I will in the next version. I got  
some problems in the past (I forgot
what goran explained to me ;)) and this was not clear to me if we  
should include the sm folder or not.

Stef

On 11 avr. 06, at 18:06, Dan Ingalls wrote:

Hi!

=?ISO-8859-1?Q?st=E9phane_ducasse?= <[hidden email]> wrote:
> Hi dan
>
> you mean squeakmap?
> Yes I would like that but I was confused recently with the exchange  
> with goran.

Not sure which exchange that was. :)

> So if goran can tell what to do I will in the next version. I got  
> some problems in the past (I forgot
> what goran explained to me ;)) and this was not clear to me if we  
> should include the sm folder or not.
>
> Stef

Well, we are talking about two different aspects:

a) That the latest image should be updated with the latest SM code.
b) That the released image should (or should not) have a recent map
inside it.

Regarding a) - that boils down to doing the "same thing" as the load
script does (the "SqueakMap" package on SM is a .st script):
        http://map.squeak.org/accountbyid/9bdedc18-1525-44a6-9b79-db5d4a87f6f8/
files/SqueakMap6.st
Essentially it upgrades the SMBase and SMLoader packages using
Monticello and clears the map instance in the image *without* losing the
information about what packages are installed in the image.

I will sit down and compress that script into a specific script for 3.9.

For b) there are two ways, either we distribute with a "recent" map
inside the image or with no map at all inside the image. Even if we
distribute the image with a map in the image it will be old very
quickly. Today the SqueakMap PackageLoader asks if it should update the
map if it is more than 10 days old. Personally I think that we should
distribute the "normal" images with a "purged" map. A purged map means a
map that is "empty" but still has the installation registry in it with
info about installed packages.

If we decide to distribute a prepopulated client side cache then we
should probably do that on the "side". Simply a zipped up "sm" dir to
drop into the dir where people have their images.

Mmmm, ok, so what did I say:

1. I will post a script that properly updates SM in 3.9. You can then
apply it in some suitable fashion.

2. We should purge the map from the image before distributing. This is
done with "SMSqueakMap default purge". You get it back from disk with
"SMSqueakMap default reload".

regards, Göran