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

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

by Tudor Girba

Exactly. This is why he pointed out that he got this error in a fresh Pharo 3.0 image :). In a Moose image, free type fonts are installed properly, hence we do not get the error. We only get the wrong rendering. Doru On Fri, Mar 28, 2014 at 3:00 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > This error message usually happens because it cannot find the freetype > font for given font name, > and substitutes it with system-default bitmap font, which are *not* > supported by Athens. > > (LogicalFont familyName: 'crazy non existing font name' pointSize:10) > realFont => a StrikeFont(Bitmap DejaVu Sans 9 14) > > so, please check your font(s) setup and fonts you using. > > > > On 28 March 2014 14:50, Blondeau Vincent <vincent.blondeau(a)worldline.com>wrote: > >> No, I did not change the Free type in the pharo settings. >> >> >> >> But if I do it under Moose, I got : >> >> >> >> *De :* moose-dev-bounces(a)iam.unibe.ch [mailto: >> moose-dev-bounces(a)iam.unibe.ch] *De la part de* StÃ©phane Ducasse >> *EnvoyÃ© :* vendredi 28 mars 2014 14:44 >> *Ã :* Pharo Development List >> *Cc :* Moose-related development >> *Objet :* [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still >> there >> >> >> >> vincent >> >> >> >> Did you changed the freetype settings? >> >> >> >> Setf >> >> >> >> On 28 Mar 2014, at 14:36, Blondeau Vincent < >> vincent.blondeau(a)worldline.com> wrote: >> >> >> >> +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 : >> >> <image001.png> >> >> <image002.png> >> >> >> >> And under a fresh Pharo 3.0 : >> >> >> >> <image003.png> >> >> >> >> Vincent >> >> >> >> *De :* moose-dev-bounces(a)iam.unibe.ch [ >> mailto:moose-dev-bounces@iam.unibe.ch <moose-dev-bounces(a)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> 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> >> >> *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> >> >> *Reply-To: *Pharo Development List <pharo-dev(a)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: >> >> >> <image004.jpg> >> >> >> >> 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 >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> >> >> >> -- >> >> 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. >> >> >> >> ------------------------------ >> >> 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. >> > > > > -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] New website about Spec - http://spec.st

by Benjamin

On 28 Mar 2014, at 14:43, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > What is the best github repo to edit the chapter? https://github.com/spec-framework/documentation, since I would like to gather as much as possible all the things related to spec at only one place :) Ben

March 28, 2014

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

by Tudor Girba

I added the code in the mail precisely to leave out any ambiguities :). The first part of the snippet (as also listed by Vincent) loads the very latest development version of Athens configuration. So, yes, I think I loaded the latest code. Doru On Fri, Mar 28, 2014 at 2:57 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 28 March 2014 14:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> I also tried based on a Moose 5.0 image on OS X 10.9.2: >> >> Gofer new >> smalltalkhubUser: 'Pharo' project: 'Athens'; >> configuration; >> loadDevelopment. >> >> 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 still get the problem: >> > > by 'still' you mean you loaded up-to-date version of Athens into your > moose image and it still doesn't works? > because Moose 5.0 image which i downloaded earlier today has very old > Athens version. > > >> [image: Inline image 1] >> >> Doru >> >> >> -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

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

by Igor Stasenko

This error message usually happens because it cannot find the freetype font for given font name, and substitutes it with system-default bitmap font, which are *not* supported by Athens. (LogicalFont familyName: 'crazy non existing font name' pointSize:10) realFont => a StrikeFont(Bitmap DejaVu Sans 9 14) so, please check your font(s) setup and fonts you using. On 28 March 2014 14:50, Blondeau Vincent <vincent.blondeau(a)worldline.com>wrote: > No, I did not change the Free type in the pharo settings. > > > > But if I do it under Moose, I got : > > > > *De :* moose-dev-bounces(a)iam.unibe.ch [mailto: > moose-dev-bounces(a)iam.unibe.ch] *De la part de* StÃ©phane Ducasse > *EnvoyÃ© :* vendredi 28 mars 2014 14:44 > *Ã :* Pharo Development List > *Cc :* Moose-related development > *Objet :* [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there > > > > vincent > > > > Did you changed the freetype settings? > > > > Setf > > > > On 28 Mar 2014, at 14:36, Blondeau Vincent <vincent.blondeau(a)worldline.com> > wrote: > > > > +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 : > > <image001.png> > > <image002.png> > > > > And under a fresh Pharo 3.0 : > > > > <image003.png> > > > > Vincent > > > > *De :* moose-dev-bounces(a)iam.unibe.ch [ > mailto:moose-dev-bounces@iam.unibe.ch <moose-dev-bounces(a)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> 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> > > *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> > > *Reply-To: *Pharo Development List <pharo-dev(a)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: > > > <image004.jpg> > > > > 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 > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > -- > > 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. > > > > ------------------------------ > > 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. > -- Best regards, Igor Stasenko.

March 28, 2014

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

by Igor Stasenko

On 28 March 2014 14:42, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I also tried based on a Moose 5.0 image on OS X 10.9.2: > > Gofer new > smalltalkhubUser: 'Pharo' project: 'Athens'; > configuration; > loadDevelopment. > > 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 still get the problem: > by 'still' you mean you loaded up-to-date version of Athens into your moose image and it still doesn't works? because Moose 5.0 image which i downloaded earlier today has very old Athens version. > [image: Inline image 1] > > Doru > > > -- Best regards, Igor Stasenko.

March 28, 2014

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

by Tudor Girba

In the Moose image, the fonts are already set to free type fonts. Doru On Fri, Mar 28, 2014 at 2:50 PM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > No, I did not change the Free type in the pharo settings. > > > > But if I do it under Moose, I got : > > > > *De :* moose-dev-bounces(a)iam.unibe.ch [mailto: > moose-dev-bounces(a)iam.unibe.ch] *De la part de* StÃ©phane Ducasse > *EnvoyÃ© :* vendredi 28 mars 2014 14:44 > *Ã :* Pharo Development List > *Cc :* Moose-related development > *Objet :* [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there > > > > vincent > > > > Did you changed the freetype settings? > > > > Setf > > > > On 28 Mar 2014, at 14:36, Blondeau Vincent <vincent.blondeau(a)worldline.com> > wrote: > > > > +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 : > > <image001.png> > > <image002.png> > > > > And under a fresh Pharo 3.0 : > > > > <image003.png> > > > > Vincent > > > > *De :* moose-dev-bounces(a)iam.unibe.ch [ > mailto:moose-dev-bounces@iam.unibe.ch <moose-dev-bounces(a)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> 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> > > *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> > > *Reply-To: *Pharo Development List <pharo-dev(a)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: > > > <image004.jpg> > > > > 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 > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > -- > > 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. > > > > ------------------------------ > > 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. > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

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

by Blondeau Vincent

No, I did not change the Free type in the pharo settings. But if I do it under Moose, I got : [cid:image001.png@01CF4A95.077A93D0] De : moose-dev-bounces(a)iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de StÃ©phane Ducasse EnvoyÃ© : vendredi 28 mars 2014 14:44 Ã : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there vincent Did you changed the freetype settings? Setf On 28 Mar 2014, at 14:36, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: +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 : <image001.png> <image002.png> And under a fresh Pharo 3.0 : <image003.png> Vincent De : moose-dev-bounces(a)iam.unibe.ch<mailto:moose-dev-bounces@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: <image004.jpg> 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. ________________________________ 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

Re: [Pharo-dev] New website about Spec - http://spec.st

by Pharo4Stef

Thanks ben This is really to see my ideas coming to live ;D > > 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. What is the best github repo to edit the chapter? > 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] [Moose-dev] Re: Fwd: Font problem is still there

by Tudor Girba

I also tried based on a Moose 5.0 image on OS X 10.9.2: Gofer new smalltalkhubUser: 'Pharo' project: 'Athens'; configuration; loadDevelopment. 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 still get the problem: [image: Inline image 1] Doru On Fri, Mar 28, 2014 at 2:36 PM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > +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 : > > > > And under a fresh Pharo 3.0 : > > > > > > Vincent > > > > *De :* moose-dev-bounces(a)iam.unibe.ch [mailto: > moose-dev-bounces(a)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> 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> > > *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> > > *Reply-To: *Pharo Development List <pharo-dev(a)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: > > > [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. > > > > > _______________________________________________ > 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" > > ------------------------------ > > 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. > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

Re: [Pharo-dev] [Pharo-users] [ANN] Application Security for your domains

by HernÃ¡n Morales Durand

Thank you for reporting. I have added links to Pharo and Fuel websites. Cheers, HernÃ¡n 2014-03-28 4:53 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: > the linke o your blog leads to > > http://www.smalltalkhub.com/#%21/%7Ehernan/ApplicationSecurity > > > On 28 Mar 2014, at 00:58, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > Hello guys, > I'm doing a double announcement here. > > First, a new blog about development with Pharo, and Smalltalk: > > http://80738163270632.blogspot.com.ar/ > > Second, my first entry contains a post about Application Security, a new > package to make Pharo applications more secure. You can start playing with > the objects right now, while more documentation is being written for the > next release. > > Hope you like it and I'm looking forward to hearing from you. > Cheers, > > HernÃ¡n > >

March 28, 2014