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

Re: [Pharo-project] [update] #10500

by Henrik Sperre Johansen

On 06.12.2009 19:43, Levente Uzonyi wrote: > On Sun, 6 Dec 2009, Adrian Lienhard wrote: > > >> Thanks, Marcus! >> >> One step closer to 1.0. >> >> Damien, I suggest not to select FreeType font in the Pharo image >> anymore but keep the Bitmap DejaVu font that comes with the core image >> now. The bitmap font is not that perfect, but apparently the speed >> > Not that perfect? What's the problem with it? FreeType's anti-aliasing is > crappy compared to BitmapDejaVu. > > > Levente > > In my experience, the character spacing can be a bit wonky in some cases. As well, the rendering method of FuzzyLabelMorphs, as used in some parts of Polymorph (most noticeably the Monticello browser), does not go well with them at all. Other than that, I agree with you that they look just as good. Cheers, Henry

Dec. 6, 2009

Re: [Pharo-project] [update] #10500

by Levente Uzonyi

On Sun, 6 Dec 2009, Adrian Lienhard wrote: > Thanks, Marcus! > > One step closer to 1.0. > > Damien, I suggest not to select FreeType font in the Pharo image > anymore but keep the Bitmap DejaVu font that comes with the core image > now. The bitmap font is not that perfect, but apparently the speed Not that perfect? What's the problem with it? FreeType's anti-aliasing is crappy compared to BitmapDejaVu. Levente > differs enough. People that prefer the FreeType fonts can then easily > switch if they like. > > Adrian >

Dec. 6, 2009

Re: [Pharo-project] [update] #10500

by Henrik Sperre Johansen

On 06.12.2009 15:28, Adrian Lienhard wrote: > Thanks, Marcus! > > One step closer to 1.0. > Humm, better hope new VM versions are out before final release :) Without the BitBlt fixes, it looks kind of horrible when dragging a window... Cheers, Henry

Dec. 6, 2009

Re: [Pharo-project] EventInterceptor and MessageSendTree

by csrabak＠bol.com.br

Em 06/12/2009 05:25, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> escreveu: > Dear all, > I've attached a little cool tool for intercepting Morphic events I > just resurrected today, from the class comments: [snipped] Interesting! Let's see if with help of it we manage to squash two bugs pending for release of Pharo 1.0!! -- Cesar Rabak

Dec. 6, 2009

Re: [Pharo-project] [update 1.1] #11073

by StÃ©phane Ducasse

thanks man! Stef ( still cleaning my office ...) On Dec 6, 2009, at 5:46 PM, Damien Cassou wrote: > 11073 > ----- > > - Updates Gofer > - Reverts fix 1293 as it prevents some websites from being fetched correctly > > -- > 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

Dec. 6, 2009

[Pharo-project] [update 1.1] #11073

by Damien Cassou

11073 ----- - Updates Gofer - Reverts fix 1293 as it prevents some websites from being fetched correctly -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Dec. 6, 2009

Re: [Pharo-project] [update] #10500

by Damien Cassou

2009/12/6 Adrian Lienhard <adi(a)netstyle.ch>: > Damien, I suggest not to select FreeType font in the Pharo image > anymore but keep the Bitmap DejaVu font that comes with the core image > now. The bitmap font is not that perfect, but apparently the speed > differs enough. People that prefer the FreeType fonts can then easily > switch if they like. ok -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Dec. 6, 2009

Re: [Pharo-project] [squeak-dev] AST-Core for Pharo and Squeak?

by HernÃ¡n Morales Durand

Hi Lukas 2009/12/6 Lukas Renggli <renggli(a)gmail.com>: > Did you run the tests, especially RBParserTest? They do all pass on Pharo. > I couldn't do a clean load the Refactoring-Tests package in Squeak 3.10.2, there is a Syntax Error testLiteralArray | tree collection | tree := RBParser parseExpression: '#( a #b #''c'' . + - 1 -2 3.4 #true true #false false #nil nil "comment" ''string'' #[ 1 2 3 ] #(1 2 3))'. collection := OrderedCollection new. collection add: #a; add: #b; add: #c; add: #'.'; add: #+; add: #-; add: 1; add: -2; add: 3.4; add: #true; add: true; add: #false; add: false; add: #nil; add: nil; add: 'string'; add: #[Nothing more expected ->1 2 3]; add: #(1 2 3). tree value with: collection do: [ :token :value | self assert: token value = value ] I removed that one to complete the loading, there are 8 failures and 5 errors, most of them in RBSmallintTest and two in RBParserTest: RBParserTest>>testBestNodeFor RBParserTest>>testIntervals but it seems to be unrelated with the #isVariable problem. In Pharo-Core #11072 I have just one failure in #testRemoveSameMethodButSendsSuper, let me know if you cannot reproduce it. > Does Squeak implement #isVariable on Object? > No, it doesn't at least in the official image. Cheers, HernÃ¡n > Lukas > > 2009/12/6 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: >> Hi guys, >> Â I've noticed a different behavior relating the RBParseTreeSearcher >> between Pharo and Squeak, using AST-Core-lr.33, the following code: >> >> | rbMethodNode | >> rbMethodNode := RBParser parseMethod: 'test [ Â ]'. >> ( RBParseTreeSearcher new >> Â Â Â Â matches: '`{:node | node isVariable }' >> Â Â Â Â do:[: aNode : answer | answer add: aNode; yourself ] ) >> Â Â Â Â Â Â Â Â executeTree: rbMethodNode initialAnswer: Set new. >> >> gives an empty Set in Pharo-Core (#11072) and Â a Set(RBSequenceNode()) >> in Squeak 3.10.2 >> Does anybody know if I should use a different AST-Core version for >> Squeak? An alternative repository maybe? >> >> HernÃ¡n >> >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > 2009/12/6 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: >> Hi guys, >> Â I've noticed a different behavior relating the RBParseTreeSearcher >> between Pharo and Squeak, using AST-Core-lr.33, the following code: >> >> | rbMethodNode | >> rbMethodNode := RBParser parseMethod: 'test [ Â ]'. >> ( RBParseTreeSearcher new >> Â Â Â Â matches: '`{:node | node isVariable }' >> Â Â Â Â do:[: aNode : answer | answer add: aNode; yourself ] ) >> Â Â Â Â Â Â Â Â executeTree: rbMethodNode initialAnswer: Set new. >> >> gives an empty Set in Pharo-Core (#11072) and Â a Set(RBSequenceNode()) >> in Squeak 3.10.2 >> Does anybody know if I should use a different AST-Core version for >> Squeak? An alternative repository maybe? >> >> HernÃ¡n >> >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > >

Dec. 6, 2009

Re: [Pharo-project] [update] #10500

by Adrian Lienhard

Thanks, Marcus! One step closer to 1.0. Damien, I suggest not to select FreeType font in the Pharo image anymore but keep the Bitmap DejaVu font that comes with the core image now. The bitmap font is not that perfect, but apparently the speed differs enough. People that prefer the FreeType fonts can then easily switch if they like. Adrian On Dec 6, 2009, at 14:11 , Marcus Denker wrote: > 10500 > ----- > > Issue 1497: Saving preferences to disk gives an error > Issue 1478: ScriptLoader loadFFI fails with a dependency error > Issue 1437: Bitmap #decompress:fromByteArray:at: not wellformed > Issue 1536: Use Bitmap DejaVu as default fonts > > > Postscript does: > > Preferences removePreference: #automaticFlapLayout; > removePreference: #navigatorOnLeftEdge; > removePreference: #classicNavigatorEnabled. > > StrikeFont installDejaVu. > Preferences setDefaultFonts: #( > (setBalloonHelpFontTo: 'BitmapDejaVu' 9) > (setButtonFontTo: 'BitmapDejaVu' 9) > (setCodeFontTo: 'BitmapDejaVu' 9) > (setHaloLabelFontTo: 'BitmapDejaVu' 9) > (setListFontTo: 'BitmapDejaVu' 9) > (setMenuFontTo: 'BitmapDejaVu' 9) > (setSystemFontTo: 'BitmapDejaVu' 9) > (setWindowTitleFontTo: 'BitmapDejaVuBold' 12)) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 6, 2009

Re: [Pharo-project] Protocol extension proposal: Boolean>>asBit ?

by CÃ©drick BÃ©ler

2009/12/5 <csrabak(a)bol.com.br> > I understand the motivation and the implementation, but IMNHO the name of > the > method should be #asSmallInteger or if you want more general #asNumber. > Why not #asBitNumber ? > > Returning 1 or 0 is not the same thing as returning a bit, except if we > agree on > creating a class called bit where the operations on it abide to what it is > expected for a bit. > > my .019999... > > CÃ©drick

Dec. 6, 2009