March 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] Re: Fwd: Font problem is still there

by Blondeau Vincent

+1. So, I did on a fresh Moose 5.0 Image under W7: Gofer new smalltalkhubUser: 'Pharo' project: 'Athens'; configuration; loadDevelopment. And : AthensSceneView new scene: [ :canvas | |s| canvas setFont: (LogicalFont familyName: 'FreeSans' pointSize: 20). s:= String newFrom: ($A to: $Z),($a to: $z), ($0 to: $9). canvas pathTransform restoreAfter: [ canvas pathTransform translateX: 0 Y: 50. canvas setPaint: Color black. canvas drawString:s ] ];openInWindow And I got : [cid:image001.png@01CF4A93.11FEC170] [cid:image002.png@01CF4A93.11FEC170] And under a fresh Pharo 3.0 : [cid:image003.png@01CF4A93.11FEC170] Vincent De : moose-dev-bounces(a)iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de Tudor Girba EnvoyÃ© : vendredi 28 mars 2014 14:28 Ã : Moose-related development Objet : [Moose-dev] Re: Fwd: [Pharo-dev] Font problem is still there Hi, This was discussed before both on the Moose and on the Pharo mailing list. We are loading explicitly an older version of Athens because we could not work at all with the one that came from Pharo, and nobody reacted at the time to the font issue: GTImageSetupCommandLineHandler>>loadOlderAthensPackagesToCorrectTheFontCachingProblem " This is a workaround fir the bug described here: https://pharo.fogbugz.com/f/cases/12777/Athens-font-cacheing-bug " Gofer new smalltalkhubUser: 'Pharo' project: 'Pharo30'; package: 'Athens-Cairo' constraint: [ :version | version author = 'MarcusDenker' and: [ version versionNumber = 51 ] ]; package: 'Athens-Core' constraint: [ :version | version author = 'MarcusDenker' and: [ version versionNumber = 34 ] ]; load Now it's great that you are looking at it. So, I now removed it from the setup and the image is now relying on the latest Pharo 3.0. The build is running now: https://ci.inria.fr/moose/job/moose-5.0/1008/ Cheers, Doru On Fri, Mar 28, 2014 at 2:18 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr<mailto:stephane.ducasse@inria.fr>> wrote: Hi guys. This is strange that moose is using a so old version of Athens. Stef Begin forwarded message: From: Igor Stasenko <siguctua(a)gmail.com<mailto:siguctua@gmail.com>> Subject: Re: [Pharo-dev] Font problem is still there Date: 28 Mar 2014 14:03:17 GMT+1 To: Pharo Development List <pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org>> Reply-To: Pharo Development List <pharo-dev(a)lists.pharo.org<mailto:pharo-dev@lists.pharo.org>> so, i checked both in 4.9 and 5.0 Moose images on linux... got weird results and sometimes crashes. in 5.0 image the version is: Athens-Cairo-MarcusDenker.51 - this one uses pretty old code, which renders text using 'toy' cairo api for text rendering. in my working image, where i work every day it is: Athens-Cairo-SvenVanCaekenberghe.64 and there's also couple important fixes since .51 as well as different font rendering code which no longer using toy api.. so, guys, if you want me to continue, please try using latest versions and report problems about it, because it makes no sense to find a fix in something which outdated and thrown away many months ago. Load the latest dev version of Athens from smalltalkhub (it is version 2.5) ConfigurationOfAthens loadDevelopment. try it out. Here's what i got on latest fresh vanilla out of the box Pharo 3.0 image on linux system: [cid:image004.jpg@01CF4A93.11FEC170] P.S. i am not saying that it is *impossible* that there is problems in new version, just asking you to report problems with that version, not one which year(s) old. -- Best regards, Igor Stasenko. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch<mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com<http://www.tudorgirba.com> "Every thing has its own flow" ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

March 28, 2014

New website about Spec - http://spec.st

by Benjamin

Hi guys :) I am glad to announce (even if Philippe already let the cat out :P) a website dedicated to Spec: http://spec.st. You can find a quick introduction, documentation (mainly what is now in the Pharo For The Enterprise book), and a news feed where I will explain the API changes, the news widgets introduce etc. The website contents can be found here (https://github.com/spec-framework/website) so if you want to contribute you are welcome :) Ben PS: I would like to thank Johan Fabry who helped me a lot writing the documentation, Sean P. DeNigris who fixed my english a couple of times and Nicolas Petton who helped me on the website look and feel

March 28, 2014

Re: [Pharo-dev] Font problem is still there

by Igor Stasenko

so, i checked both in 4.9 and 5.0 Moose images on linux... got weird results and sometimes crashes. in 5.0 image the version is: Athens-Cairo-MarcusDenker.51 - this one uses pretty old code, which renders text using 'toy' cairo api for text rendering. in my working image, where i work every day it is: Athens-Cairo-SvenVanCaekenberghe.64 and there's also couple important fixes since .51 as well as different font rendering code which no longer using toy api.. so, guys, if you want me to continue, please try using latest versions and report problems about it, because it makes no sense to find a fix in something which outdated and thrown away many months ago. Load the latest dev version of Athens from smalltalkhub (it is version 2.5) ConfigurationOfAthens loadDevelopment. try it out. Here's what i got on latest fresh vanilla out of the box Pharo 3.0 image on linux system: [image: Inline images 1] P.S. i am not saying that it is *impossible* that there is problems in new version, just asking you to report problems with that version, not one which year(s) old. -- Best regards, Igor Stasenko.

March 28, 2014

Regex groups

by Sean P. DeNigris

I find myself often writing code like: matcher := RxMatcher forString: '<p>SHA-1\: (\w+)</p>'. matcher search: shaLine trimBoth. ^ matcher subexpression: 2. Is there an easier way, or could a convenience method be useful to write e.g.: '<p>SHA-1\: (\w+)</p>' asRegex subexpression: 2 in: aString ----- Cheers, Sean -- View this message in context: http://forum.world.st/Regex-groups-tp4751339.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Re: [Pharo-dev] Capturing stdout

by Max Leske

Forget what I saidâ¦ Just ramblingâ¦ On 28.03.2014, at 13:48, Max Leske <maxleske(a)gmail.com> wrote: > start pharo from the console? > > On 28.03.2014, at 12:57, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> I want to write a test for an NB Mac system call example (Issue 13147). I can >> check the exit code easily, the output goes to stdout of the image. Can I >> capture it somehow? thx :) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Capturing-stdout-tp4751320.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >

March 28, 2014

Re: [Pharo-dev] Capturing stdout

by Max Leske

start pharo from the console? On 28.03.2014, at 12:57, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I want to write a test for an NB Mac system call example (Issue 13147). I can > check the exit code easily, the output goes to stdout of the image. Can I > capture it somehow? thx :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Capturing-stdout-tp4751320.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Tudor Girba

And a last one :). You can find the actual code here: GTImageSetupCommandLineHandler>>installFonts Cheers, Doru On Fri, Mar 28, 2014 at 1:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > And the installation of the font happens like this: > > install > FreeTypeFontProvider current > addFromFileContents: self fontContents > baseName: self originalFileName > > Cheers, > Doru > > > > > On Fri, Mar 28, 2014 at 1:41 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I am not quite sure this is where the problem comes from given that we >> see half of the letters being well drawn and half not well. >> >> Here is how the font is loaded: >> #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' >> 'SourceSansProBold') do: [ :each | >> each asSymbol asClassIfAbsent: [ >> Gofer new >> smalltalkhubUser: 'girba' project: 'FreeFonts'; >> package: each; >> load ]. >> (Smalltalk at: each asSymbol) new install ]. >> FreeTypeSystemSettings loadFt2Library: true. >> FreeTypeFontProvider current updateFromSystem. >> >> StandardFonts >> setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' >> pointSize: 10); >> haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); >> windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: >> 14); >> balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); >> codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) >> >> Did I miss something? >> >> Cheers, >> Doru >> >> >> >> On Fri, Mar 28, 2014 at 12:44 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >> >>> >>> On 28 Mar 2014, at 12:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> wrote: >>> >>> Hi >>> >>> We found with igor the problems that produced red cross in Moose. >>> The problem is that the system is looking Source Sans Pro and does not >>> find it. >>> >>> The logic in findBestFont: does not find it because there is no such >>> font registered in font manager >>> and the default logic is to return TextStyle defaultFont which is a >>> bitmpa one. >>> >>> So question: >>> - may be we should have a FT font default loaded in the system? >>> >>> - Doru we remember that you loaded font in the system? May be >>> you do not register well the fonts. >>> Could you let us know what you did? >>> >>> >>> can you execute the following >>> -0 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >>> realFont >>> you should get a freetype font >>> >>> - 1 Disable the freetrype in the setting >>> - 2 Enable again freetype in the setting >>> - 3 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >>> realFont >>> >>> because you should get a strikeFont and this is the bug >>> So it looks like the image level fonts are lost. >>> >>> Stef and Igor. >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Tudor Girba

And the installation of the font happens like this: install FreeTypeFontProvider current addFromFileContents: self fontContents baseName: self originalFileName Cheers, Doru On Fri, Mar 28, 2014 at 1:41 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I am not quite sure this is where the problem comes from given that we see > half of the letters being well drawn and half not well. > > Here is how the font is loaded: > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' > 'SourceSansProBold') do: [ :each | > each asSymbol asClassIfAbsent: [ > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load ]. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > FreeTypeFontProvider current updateFromSystem. > > StandardFonts > setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' > pointSize: 10); > haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); > balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) > > Did I miss something? > > Cheers, > Doru > > > > On Fri, Mar 28, 2014 at 12:44 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> >> On 28 Mar 2014, at 12:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> >> Hi >> >> We found with igor the problems that produced red cross in Moose. >> The problem is that the system is looking Source Sans Pro and does not >> find it. >> >> The logic in findBestFont: does not find it because there is no such font >> registered in font manager >> and the default logic is to return TextStyle defaultFont which is a >> bitmpa one. >> >> So question: >> - may be we should have a FT font default loaded in the system? >> >> - Doru we remember that you loaded font in the system? May be you >> do not register well the fonts. >> Could you let us know what you did? >> >> >> can you execute the following >> -0 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >> realFont >> you should get a freetype font >> >> - 1 Disable the freetrype in the setting >> - 2 Enable again freetype in the setting >> - 3 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) >> realFont >> >> because you should get a strikeFont and this is the bug >> So it looks like the image level fonts are lost. >> >> Stef and Igor. >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Problem with fonts

by Tudor Girba

I am not quite sure this is where the problem comes from given that we see half of the letters being well drawn and half not well. Here is how the font is loaded: #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | each asSymbol asClassIfAbsent: [ Gofer new smalltalkhubUser: 'girba' project: 'FreeFonts'; package: each; load ]. (Smalltalk at: each asSymbol) new install ]. FreeTypeSystemSettings loadFt2Library: true. FreeTypeFontProvider current updateFromSystem. StandardFonts setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) Did I miss something? Cheers, Doru On Fri, Mar 28, 2014 at 12:44 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > On 28 Mar 2014, at 12:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > Hi > > We found with igor the problems that produced red cross in Moose. > The problem is that the system is looking Source Sans Pro and does not > find it. > > The logic in findBestFont: does not find it because there is no such font > registered in font manager > and the default logic is to return TextStyle defaultFont which is a bitmpa > one. > > So question: > - may be we should have a FT font default loaded in the system? > > - Doru we remember that you loaded font in the system? May be you > do not register well the fonts. > Could you let us know what you did? > > > can you execute the following > -0 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) > realFont > you should get a freetype font > > - 1 Disable the freetrype in the setting > - 2 Enable again freetype in the setting > - 3 (LogicalFont familyName: 'Source Sans Pro' pointSize: 12) > realFont > > because you should get a strikeFont and this is the bug > So it looks like the image level fonts are lost. > > Stef and Igor. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] DateAndTime>>#= slow?

by Pharo4Stef

Hi johan Please let us know because I would be in favor of integrating such speed up if your system fully work. stef On 28 Mar 2014, at 09:17, Johan Brichau <johan(a)inceptive.be> wrote: > > On 28 Mar 2014, at 06:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Bugs are errors that prevents the system to run. > > <nagging> > Some performance problems make the system impossible to work with > </nagging> > > Anyway, going to check in Sven's changes today. > > cheers > Johan >

March 28, 2014