April 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Unicode fonts and MultiCompositionScaner

by StÃ©phane Ducasse

thanks, I'm pretty bad with font :) On Apr 16, 2009, at 10:05 PM, Andrey Larionov wrote: > Investigating reasons of fail FontTest tests i found bug in > MultiCompositionScaner (or it maybe some related class). Looks like > what Character value: 257 had a special meaning in squeak. If not use > StrikeFont everything is well, but if you choose FreeType font the > doing something > (Character value: 257) asString asTextMorph openInWorld > creates an endles loop in composer. It founds character falls in > crossedX method (this character is stopCondition) and then remove > character from composition and starts again. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009

[Pharo-project] Unicode fonts and MultiCompositionScaner

by Andrey Larionov

Investigating reasons of fail FontTest tests i found bug in MultiCompositionScaner (or it maybe some related class). Looks like what Character value: 257 had a special meaning in squeak. If not use StrikeFont everything is well, but if you choose FreeType font the doing something (Character value: 257) asString asTextMorph openInWorld creates an endles loop in composer. It founds character falls in crossedX method (this character is stopCondition) and then remove character from composition and starts again.

April 16, 2009

Re: [Pharo-project] WeakArray class>>#finalizationProcess

by StÃ©phane Ducasse

On Apr 16, 2009, at 5:49 PM, Igor Stasenko wrote: > 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> We are always interested in better solutions. >> Do you have code and got good feedback? >> > Nope :) > But i can write one. Currently, the problem is that i don't know when > i have time to do it :) This is not currently for me. This is endlessly :) So I try to take one item on the list of stuff that I should do and do it but the list is huge. :)

April 16, 2009

Re: [Pharo-project] linux version download problem

by Schwab,Wilhelm K

Damien, I think so, but is there a specific test that would answer it for you? I'm happy to try it and report back, but I fear that I could miss something if left to my own devices to plan the test. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Damien Cassou Sent: Tuesday, April 14, 2009 8:59 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] linux version download problem On Tue, Apr 14, 2009 at 3:23 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Are you sure about the cd to get a local path to the image? Â I just give the full path to both the vm and image, and it seems to work. do you get the directory package-cache in the image directory if you load things through monticello? -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 16, 2009

Re: [Pharo-project] New Pharo-dev based on 10277

by Schwab,Wilhelm K

Damien, Let's see, you are making the web images as a courtesy to the rest of us, so, yeah, I GUESS it's ok :) Your efforts are much appreciated. My primary rhetorical question is not how often you should produce web images, but whether or not the developer image plus scripting is good enough. I ask in part because of things like FFI/Alien, etc. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Damien Cassou Sent: Thursday, April 16, 2009 5:12 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] New Pharo-dev based on 10277 On Wed, Apr 15, 2009 at 11:27 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > It's nice to not be the only one nagging you for updates of Pharo-web :) Â However, I'm the first to admit that if comes down to running a script or two on top of Pharo-dev, that should do the job. Is it ok if I only once a month? -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 16, 2009

Re: [Pharo-project] WeakArray class>>#finalizationProcess

by Igor Stasenko

2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > We are always interested in better solutions. > Do you have code and got good feedback? > Nope :) But i can write one. Currently, the problem is that i don't know when i have time to do it :) > Stef > > >> Btw, if anyone interested, i explored what the finalizationProcess >> does in the past.. >> and found some things i don't like. >> Maybe now in Pharo, you can cosider about fixing/improving this stuff. >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-July/119052.html >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-July/119054.html >> >> 2009/4/16 Markus Fritsche <fritsche.markus(a)gmx.net>: >>> StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> Strange I fixed those ones. Can you check if you have the same >>>> problem >>>> in the latest? >>> >>> It could have happened that I did overwrite those by loading new >>> PolyMorph >>> packages. >>> >>>> See the other email :) >>> >>> Merci! >>> >>>> Torsten sent us a loadFFI now available in scriptLoader in one the >>>> latest updates. >>>> Can you check? >>> >>> Seems to work well. Thanks for the pointer. >>> >>>> If you can reproduce that with the latest (updated image). >>>> Let us know. We are chasing bugs now. >>> >>> Nope, working now I think. >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 16, 2009

Re: [Pharo-project] Please publish Slice

by Lukas Renggli

> Can some Monticello wiz come up with some magic script to run to check > all dirty packages for changes, so that packages that don't have > changes get reset to clean? Seaside 2.9alpha3 has several scripts in the class WADevelopment in the package Seaside-Squeak-Development that do exactly that (and other stuff). If there are many packages involved it takes a long time though. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

April 16, 2009

Re: [Pharo-project] Please publish Slice

by Michael Rueger

On Thu, Apr 16, 2009 at 2:22 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > OK Stef, sorry I didn't follow the procedure. > This is because the annoying fact that running some of the tests > result in dirty packages... Can some Monticello wiz come up with some magic script to run to check all dirty packages for changes, so that packages that don't have changes get reset to clean? Michael

April 16, 2009

Re: [Pharo-project] The System Package

by Alexandre Bergel

> I don't have a package registered called 'System', Strange, I do not know what went wrong. Sorry, we should have checked in a fresh image before. > That does not solve the problem of overlapping packages. See > <http://code.google.com/p/seaside/wiki/PackageNaming> for a large > scale packaging scheme that works. Why using - in package names where it is a special character for MC. Why not _ instead? Just wondering. In Moose, we have Moose-All, Moose-OBBrowser, ..., but if one define a package Moose, then we are a kind of screwed. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 16, 2009

Re: [Pharo-project] Please publish Slice

by StÃ©phane Ducasse

On Apr 16, 2009, at 2:22 PM, Nicolas Cellier wrote: > OK Stef, sorry I didn't follow the procedure. > This is because the annoying fact that running some of the tests > result in dirty packages... I see :) Stef > > > Nicolas > > 2009/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> because after this is much more difficult for me to integrate >> For example now I have new event mixed with closure fixes.... >> This is simple to publish a slice you create it and add the dirty >> packages as dependent. >> >> Stef >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2009