- Pharo-dev - lists.pharo.org

Re: [Pharo-project] issue 794

by Miguel Enrique CobÃ¡ Martinez

El lun, 07-12-2009 a las 01:34 -0500, Sean Allen escribiÃ³: > Using 64 bit debian lenny, I'm experiencing issue 794. > > The issue was closed but there doesn't seem to be any definitive how > it was resolved for others. > Can someone give me an idea of what the fix is? > > I see one where upgrading to an unstable version of debian worked but > I'm try to avoid that. I appears to me that the issue was never solved on Debian stable (lenny at the time) only worked for me after upgrading to squeeze. In my case I don't have any 64 bit server with lenny in production, only 32 bit servers, so the network issue doesn't affected me. Hopefully when I use 64 bit servers in production I will use Squeeze (that should be stable by then) and the problem will never hit me. Anyway, as I said, the problem was never correctly addressed or even the main cause discovered. Potentially, when the Pharo 1.0 get released, it will hit several users using Lenny 64 bit. Maybe this should be confirmed and the tickets opened again. Cheers > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Dec. 7, 2009

[Pharo-project] SLICE-PreferencesMigrationPart5

by Alain Plantec

------------------ SLICE-PreferencesMigrationPart5 is in InBox * remove projectPreferenceFlagDictionary inst var from Project * migrate "docking bars" group * migrate "fileout" group * remove all remaining deprecated popup (hope it makes OB using ok) ------------------ Alain

Dec. 7, 2009

[Pharo-project] [update 1.1] #11075

by Marcus Denker

11075 ----- Issue 1505: remove TheWorldMenu>>#loadSqueakMap (not removed, just moved to SARInstaller) Issue 1406: #ofSize: should be defined in SequenceableCollection class rather than Collection Issue 1399: Add missing CreateMethod button to the debugger stack view Issue 1374: String >> #matchesRegex: should accept both strings AND regular expressions Issue 705: closures: strange error in SyntaxError apparently it may happen that the category is nil Marcus

Dec. 7, 2009

Re: [Pharo-project] A centralized repository (Going a step forward Gofer and Metacello)

by Esteban Lorenzano

Done. It is named "MetacelloRepository" :) On 2009-12-07 10:28:05 -0300, Mariano Martinez Peck <marianopeck(a)gmail.com> said: > > > On Mon, Dec 7, 2009 at 1:57 PM, Esteban Lorenzano > <estebanlm(a)gmail.com>wrot= > e: > >> Ok, that is all the blessing needed :) >> I will start work on a first version of tools needed (there are not >> mutch at all) and I will upload a meta-package as soon as I have it >> working, to test it. >> On first stage, we will use a centralized repository on SqueakSource, >> and on second stage we can think on a more fashionable way to show the >> catalog :) >> >> About the SqueakSource repository, the name I first proposed >> (PharoMetacelloRepository) is not admited for SqueakSource (too large), >> so I need variants... what do you think? >> I have this in mind: >> >> -ConfigurationOfPharo >> -MetaPharo >> -MetacelloRepository >> >> I like the first one most, because it uses the same convention as the >> metacello suggested convention. >> >> > I don't know if I like to put "Pharo" in the name. The idea of Metacello is > also to be able to easily port form one dialect to other. So, suppose I wan= > t > to create the ConfigurationOfFFI, maybe I will have something for #squeak > and something for #pharo or even for gemstone. > > So, I rather a name, not hardcoded to pharo, so that the configurations > there should have the conditions. > > I like MetacelloRepository. > > Best, > > Mariano > > Cheers, >> Esteban >> >> On 2009-12-05 07:27:25 -0300, St=E9phane Ducasse >> <stephane.ducasse(a)inria.fr> said: >> >>> Hi lorenzo >>> >>> YES! we need a catalog in place of Universe package. I think that using >> mon >>> ticello as a way to store metacello config is the way to go. >>> We do not need to integrate metacello for now (even if the goal is to >> succe >>> ed to manage >>> Pharo with metacello). We could do Gofer loadMetacelloRepository or >> somethi >>> ng like that. >>> Then this is important because the testServer could also use this >> informati >>> on. >>> >>> >>> Stef >>> >>> >>> On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote: >>> >>>> Hi all, >>>> I=92m begining to transfer all my projects to metacello (I think this = > is >>> >>>> the best package manager present today for pharo), and I have an idea = > I >>> >>>> want to share and discuss: >>>> >>> >>>> I think we need a metacello based centered repository. >>>> >>> >>>> The universe doesn=92t fit with metacello and squeakmap even less. >>>> >>> >>>> So this is my idea (it is based on =93ibiblio=94 for maven/java and ap= > t-g >>> et >>> >>>> for ubuuntu): >>>> -we can create a project on squeaksource called >>> >>>> =93PharoMetacelloRepository=94, where people can put its public metace= > llo >>> >>>> configuration packages (for example ConfigurationOfSeaside30, >>> >>>> ConfigurationOfDeimos, etc.). >>>> -we should integrate metacello to pharo core (like Gofer now) >>>> -we=92ll need to create a new class =93Loader=94 >>>> >>> >>>> What =93Loader=94 does? it loads versions from =93metacello repositori= > es >>> =94, >>> >>>> for example: >>>> >>> >>>> Loader default latest: =91Seaside30=92. =93This will load latest versi= > on >>> of >>> >>>> ConfigurationOfSeaside30=92 >>>> >>> >>>> Loader class>>#default answers a loader pointing to >>> >>>> =93PharoMetacelloRepository=94, but you could define others (for your >>> >>>> private projects). >>>> >>> >>>> How Loader works? >>>> 1) validate loading a valid metacello configuration package (we=92ll n= > eed >>> >>>> to define this later >>>> 2) load metacello package >>>> 3) do something like =93MetacelloConfigurationClass project >>> >>>> loadLatestVersion=94 (for #latest), and the corresponding sends for >>> >>>> specific versions, etc. >>>> >>> >>>> I think this will solve any package management problem, by using >>> >>>> something already present (SqueakSource), and of course, we could thin= > k >>> >>>> on better repository places/formats later (but we will be =93on the ro= > ad >>> =94) >>>> >>> >>>> So, what do you think? >>>> >>> >>>> btw: If the community agree, I=92m offering my self to implement this = > ide >>> a ;) >>>> >>> >>>> Cheers, >>>> Esteban >>>> >>> >>>> >>> >>>> >>> >>>> _______________________________________________ >>>> 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 >> > > > <div class=3D"gmail_quote">On Mon, Dec 7, 2009 at 1:57 PM, Esteban = > Lorenzano <<a > href=3D"mailto:estebanlm@gmail.com">este= > banlm(a)gmail.com</a>> > wrote: <blockquote class=3D"gmail_quote" = > style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8= > ex; padding-left: 1ex;"> > Ok, that is all the blessing needed =A0:) > I will start work on a first version of tools needed (there are not > mutch at all) and I will upload a meta-package as soon as I have it > working, to test it. > On first stage, we will use a centralized repository on SqueakSource, > and on second stage we can think on a more fashionable way to show the > catalog :) > > About the SqueakSource repository, the name I first proposed > (PharoMetacelloRepository) is not admited for SqueakSource (too large), > so I need variants... what do you think? > I have this in mind: > > -ConfigurationOfPharo > -MetaPharo > -MetacelloRepository > > I like the first one most, because it uses the same convention as the > metacello suggested convention. > </blockquote><div> I don't know if I like to put "Pharo&quo= > t; in the name. The idea of Metacello is also to be able to easily port for= > m one dialect to other. So, suppose I want to create the ConfigurationOfFFI= > , maybe I will have something for #squeak and something for #pharo or even = > for gemstone. > So, I rather a name, not hardcoded=A0 to pharo, so that the configurati= > ons there should have the conditions. I like MetacelloRepository. <= > br> Best, Mariano </div><blockquote class=3D"gmail_quote"= > style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.= > 8ex; padding-left: 1ex;"> > > Cheers, > Esteban > > On 2009-12-05 07:27:25 -0300, St=E9phane Ducasse > <div><div></div><div class=3D"h5"><<a href=3D"mailto:stephane.ducasse@in= > ria.fr">stephane.ducasse(a)inria.fr</a>> said: > > > Hi lorenzo > > > > YES! we need a catalog in place of Universe package. I think that usin= > g mon > > ticello as a way to store metacello config is the way to go. > > We do not need to integrate metacello for now (even if the goal is to = > succe > > ed to manage > > Pharo with metacello). We could do Gofer loadMetacelloRepository or so= > methi > > ng like that. > > Then this is important because the testServer could also use this info= > rmati > > on. > > > > > > Stef > > > > > > On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote: > > > >> Hi all, > >> I=92m begining to transfer all my projects to metacello (I think t= > his is > > > >> the best package manager present today for pharo), and I have an i= > dea I > > > >> want to share and discuss: > >> > > > >> I think we need a metacello based centered repository. > >> > > > >> The universe doesn=92t fit with metacello and squeakmap even less.= > > >> > > > >> So this is my idea (it is based on =93ibiblio=94 for maven/java an= > d apt-g > > et > > > >> for ubuuntu): > >> -we can create a project on squeaksource called > > > >> =93PharoMetacelloRepository=94, where people can put its public me= > tacello > > > >> configuration packages (for example ConfigurationOfSeaside30, > > > >> ConfigurationOfDeimos, etc.). > >> -we should integrate metacello to pharo core (like Gofer now) > >> -we=92ll need to create a new class =93Loader=94 > >> > > > >> What =93Loader=94 does? it loads versions from =93metacello reposi= > tories > > =94, > > > >> for example: > >> > > > >> Loader default latest: =91Seaside30=92. =93This will load latest v= > ersion > > of > > > >> ConfigurationOfSeaside30=92 > >> > > > >> Loader class>>#default answers a loader pointing to > > > >> =93PharoMetacelloRepository=94, but you could define others (for y= > our > > > >> private projects). > >> > > > >> How Loader works? > >> 1) validate loading a valid metacello configuration package (we=92= > ll need > > > >> to define this later > >> 2) load metacello package > >> 3) do something like =93MetacelloConfigurationClass project > > > >> loadLatestVersion=94 (for #latest), and the corresponding sends fo= > r > > > >> specific versions, etc. > >> > > > >> I think this will solve any package management problem, by using<b= > r> > > > >> something already present (SqueakSource), and of course, we could = > think > > > >> on better repository places/formats later (but we will be =93on th= > e road > > =94) > >> > > > >> So, what do you think? > >> > > > >> btw: If the community agree, I=92m offering my self to implement t= > his ide > > a ;) > >> > > > >> Cheers, > >> Esteban > >> > > > >> > > > >> > > > >> _______________________________________________ > >> Pharo-project mailing list > >> <a > href=3D"mailto:Pharo-project@lists.gforge.inria.fr">Pharo-proje= ct(a)lists.gforge.inria.fr</a> >> > > <a href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/p= > haro-project" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailma= > n/listinfo/pharo-project</a> > > > > > _______________________________________________ > Pharo-project mailing list > <a > href=3D"mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project(a)lists.= gforge.inria.fr</a> <a > > href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-proj= > ect" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinf= > o/pharo-project</a></div></div></blockquote></div> > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 7, 2009

[Pharo-project] Dealing with Preferences in external packages?

by StÃ©phane Ducasse

Now that setting is starting to get integrated (great) we will also face the problem of branching. For example, how do we manage that OB uses Preferences.... and that we don't. Any idea or process is welcome. Of course we can have a package full of override but this is the ultimate solution before complete fork. Stef

Dec. 7, 2009

Re: [Pharo-project] A centralized repository (Going a step forward Gofer and Metacello)

by Mariano Martinez Peck

On Mon, Dec 7, 2009 at 1:57 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Ok, that is all the blessing needed :) > I will start work on a first version of tools needed (there are not > mutch at all) and I will upload a meta-package as soon as I have it > working, to test it. > On first stage, we will use a centralized repository on SqueakSource, > and on second stage we can think on a more fashionable way to show the > catalog :) > > About the SqueakSource repository, the name I first proposed > (PharoMetacelloRepository) is not admited for SqueakSource (too large), > so I need variants... what do you think? > I have this in mind: > > -ConfigurationOfPharo > -MetaPharo > -MetacelloRepository > > I like the first one most, because it uses the same convention as the > metacello suggested convention. > > I don't know if I like to put "Pharo" in the name. The idea of Metacello is also to be able to easily port form one dialect to other. So, suppose I want to create the ConfigurationOfFFI, maybe I will have something for #squeak and something for #pharo or even for gemstone. So, I rather a name, not hardcoded to pharo, so that the configurations there should have the conditions. I like MetacelloRepository. Best, Mariano Cheers, > Esteban > > On 2009-12-05 07:27:25 -0300, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> said: > > > Hi lorenzo > > > > YES! we need a catalog in place of Universe package. I think that using > mon > > ticello as a way to store metacello config is the way to go. > > We do not need to integrate metacello for now (even if the goal is to > succe > > ed to manage > > Pharo with metacello). We could do Gofer loadMetacelloRepository or > somethi > > ng like that. > > Then this is important because the testServer could also use this > informati > > on. > > > > > > Stef > > > > > > On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote: > > > >> Hi all, > >> Iâm begining to transfer all my projects to metacello (I think this is > > > >> the best package manager present today for pharo), and I have an idea I > > > >> want to share and discuss: > >> > > > >> I think we need a metacello based centered repository. > >> > > > >> The universe doesnât fit with metacello and squeakmap even less. > >> > > > >> So this is my idea (it is based on âibiblioâ for maven/java and apt-g > > et > > > >> for ubuuntu): > >> -we can create a project on squeaksource called > > > >> âPharoMetacelloRepositoryâ, where people can put its public metacello > > > >> configuration packages (for example ConfigurationOfSeaside30, > > > >> ConfigurationOfDeimos, etc.). > >> -we should integrate metacello to pharo core (like Gofer now) > >> -weâll need to create a new class âLoaderâ > >> > > > >> What âLoaderâ does? it loads versions from âmetacello repositories > > â, > > > >> for example: > >> > > > >> Loader default latest: âSeaside30â. âThis will load latest version > > of > > > >> ConfigurationOfSeaside30â > >> > > > >> Loader class>>#default answers a loader pointing to > > > >> âPharoMetacelloRepositoryâ, but you could define others (for your > > > >> private projects). > >> > > > >> How Loader works? > >> 1) validate loading a valid metacello configuration package (weâll need > > > >> to define this later > >> 2) load metacello package > >> 3) do something like âMetacelloConfigurationClass project > > > >> loadLatestVersionâ (for #latest), and the corresponding sends for > > > >> specific versions, etc. > >> > > > >> I think this will solve any package management problem, by using > > > >> something already present (SqueakSource), and of course, we could think > > > >> on better repository places/formats later (but we will be âon the road > > â) > >> > > > >> So, what do you think? > >> > > > >> btw: If the community agree, Iâm offering my self to implement this ide > > a ;) > >> > > > >> Cheers, > >> Esteban > >> > > > >> > > > >> > > > >> _______________________________________________ > >> 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 >

Dec. 7, 2009

Re: [Pharo-project] A centralized repository (Going a step forward Gofer and Metacello)

by StÃ©phane Ducasse

On Dec 7, 2009, at 1:57 PM, Esteban Lorenzano wrote: > Ok, that is all the blessing needed :) > I will start work on a first version of tools needed (there are not > mutch at all) and I will upload a meta-package as soon as I have it > working, to test it. > On first stage, we will use a centralized repository on SqueakSource, > and on second stage we can think on a more fashionable way to show the > catalog :) > > About the SqueakSource repository, the name I first proposed > (PharoMetacelloRepository) is not admited for SqueakSource (too large), > so I need variants... what do you think? > I have this in mind: > > -ConfigurationOfPharo but this one will be used for pharo > -MetaPharo > -MetacelloRepository I like the last one :) even if the second one is tempting :) > > I like the first one most, because it uses the same convention as the > metacello suggested convention. > > Cheers, > Esteban > > On 2009-12-05 07:27:25 -0300, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> said: > >> Hi lorenzo >> >> YES! we need a catalog in place of Universe package. I think that using mon >> ticello as a way to store metacello config is the way to go. >> We do not need to integrate metacello for now (even if the goal is to succe >> ed to manage >> Pharo with metacello). We could do Gofer loadMetacelloRepository or somethi >> ng like that. >> Then this is important because the testServer could also use this informati >> on. >> >> >> Stef >> >> >> On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote: >> >>> Hi all, >>> Iâm begining to transfer all my projects to metacello (I think this is >> >>> the best package manager present today for pharo), and I have an idea I >> >>> want to share and discuss: >>> >> >>> I think we need a metacello based centered repository. >>> >> >>> The universe doesnât fit with metacello and squeakmap even less. >>> >> >>> So this is my idea (it is based on âibiblioâ for maven/java and apt-g >> et >> >>> for ubuuntu): >>> -we can create a project on squeaksource called >> >>> âPharoMetacelloRepositoryâ, where people can put its public metacello >> >>> configuration packages (for example ConfigurationOfSeaside30, >> >>> ConfigurationOfDeimos, etc.). >>> -we should integrate metacello to pharo core (like Gofer now) >>> -weâll need to create a new class âLoaderâ >>> >> >>> What âLoaderâ does? it loads versions from âmetacello repositories >> â, >> >>> for example: >>> >> >>> Loader default latest: âSeaside30â. âThis will load latest version >> of >> >>> ConfigurationOfSeaside30â >>> >> >>> Loader class>>#default answers a loader pointing to >> >>> âPharoMetacelloRepositoryâ, but you could define others (for your >> >>> private projects). >>> >> >>> How Loader works? >>> 1) validate loading a valid metacello configuration package (weâll need >> >>> to define this later >>> 2) load metacello package >>> 3) do something like âMetacelloConfigurationClass project >> >>> loadLatestVersionâ (for #latest), and the corresponding sends for >> >>> specific versions, etc. >>> >> >>> I think this will solve any package management problem, by using >> >>> something already present (SqueakSource), and of course, we could think >> >>> on better repository places/formats later (but we will be âon the road >> â) >>> >> >>> So, what do you think? >>> >> >>> btw: If the community agree, Iâm offering my self to implement this ide >> a ;) >>> >> >>> Cheers, >>> Esteban >>> >> >>> >> >>> >> >>> _______________________________________________ >>> 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

Dec. 7, 2009

Re: [Pharo-project] A centralized repository (Going a step forward Gofer and Metacello)

by Esteban Lorenzano

Ok, that is all the blessing needed :) I will start work on a first version of tools needed (there are not mutch at all) and I will upload a meta-package as soon as I have it working, to test it. On first stage, we will use a centralized repository on SqueakSource, and on second stage we can think on a more fashionable way to show the catalog :) About the SqueakSource repository, the name I first proposed (PharoMetacelloRepository) is not admited for SqueakSource (too large), so I need variants... what do you think? I have this in mind: -ConfigurationOfPharo -MetaPharo -MetacelloRepository I like the first one most, because it uses the same convention as the metacello suggested convention. Cheers, Esteban On 2009-12-05 07:27:25 -0300, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> said: > Hi lorenzo > > YES! we need a catalog in place of Universe package. I think that using mon > ticello as a way to store metacello config is the way to go. > We do not need to integrate metacello for now (even if the goal is to succe > ed to manage > Pharo with metacello). We could do Gofer loadMetacelloRepository or somethi > ng like that. > Then this is important because the testServer could also use this informati > on. > > > Stef > > > On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote: > >> Hi all, >> Iâm begining to transfer all my projects to metacello (I think this is > >> the best package manager present today for pharo), and I have an idea I > >> want to share and discuss: >> > >> I think we need a metacello based centered repository. >> > >> The universe doesnât fit with metacello and squeakmap even less. >> > >> So this is my idea (it is based on âibiblioâ for maven/java and apt-g > et > >> for ubuuntu): >> -we can create a project on squeaksource called > >> âPharoMetacelloRepositoryâ, where people can put its public metacello > >> configuration packages (for example ConfigurationOfSeaside30, > >> ConfigurationOfDeimos, etc.). >> -we should integrate metacello to pharo core (like Gofer now) >> -weâll need to create a new class âLoaderâ >> > >> What âLoaderâ does? it loads versions from âmetacello repositories > â, > >> for example: >> > >> Loader default latest: âSeaside30â. âThis will load latest version > of > >> ConfigurationOfSeaside30â >> > >> Loader class>>#default answers a loader pointing to > >> âPharoMetacelloRepositoryâ, but you could define others (for your > >> private projects). >> > >> How Loader works? >> 1) validate loading a valid metacello configuration package (weâll need > >> to define this later >> 2) load metacello package >> 3) do something like âMetacelloConfigurationClass project > >> loadLatestVersionâ (for #latest), and the corresponding sends for > >> specific versions, etc. >> > >> I think this will solve any package management problem, by using > >> something already present (SqueakSource), and of course, we could think > >> on better repository places/formats later (but we will be âon the road > â) >> > >> So, what do you think? >> > >> btw: If the community agree, Iâm offering my self to implement this ide > a ;) >> > >> Cheers, >> Esteban >> > >> > >> > >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 7, 2009

[Pharo-project] [update 1.1] #11074

by StÃ©phane Ducasse

11074 ----- - Issue 1547 by aplantec: Preferences migration part4 - Issue 1353-keysArray-part2 - Issue 1082: PharoDebug.log uses MacOS X line end convention on all systems

Dec. 7, 2009

Re: [Pharo-project] New pharo images

by Adrian Lienhard

Ok, I changed the link for the Unix VM on the webpage to point to http://www.squeakvm.org/unix/ Adrian On Dec 7, 2009, at 12:19 , Pavel Krivanek wrote: > Hi, > > this seems to be a problem of the exupery vm that is offered by Pharo > web site. The version 3.11.3-2135 works fine. > > Cheers, > -- Pavel > > 2009/12/7 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: >> Are you using an up-to-date Unix VM? >> IIRC, that particular issue was fixed back in June or so, and I think >> they're included in the latest version on squeakvm.org. >> Cheers, >> Henry >> On Dec 7, 2009, at 11:11 15AM, laurent laffont wrote: >> >> On Linux with composition enabled (I use KDE 4.3 on ArchLinux) >> there's a >> problem with font rendering. See screenshot. >> Laurent >> On Mon, Dec 7, 2009 at 10:08 AM, Damien Cassou <damien.cassou(a)gmail.com >> > >> wrote: >>> >>> Based on 1.0 rc1 and 1.1 alpha: http://pharo-project.org/pharo-download >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Lambdas are relegated to relative obscurity until Java makes them >>> popular by not having them." James Iry >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> <pharo_10500.png>_______________________________________________ >> 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 7, 2009