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

Re: [Pharo-dev] Capturing stdout

by Sean P. DeNigris

Max Leske wrote > Forget what I saidâ¦ Just ramblingâ¦ Ha ha, I was doing the confused-puppy-head-tilt (see http://da0cb6511396a92928c7-488d28a6573db6ac4a247063b638fcb9.r77.cf2.rackcd…) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Capturing-stdout-tp4751320p4751409.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Release Mode

by Sean P. DeNigris

While I was on holiday, it seems my dear friends have gone feature crazy... almost as bad as me in the run up to the 2.0 release, ha ha. As cool as they are, are: - changing the look of Nautilus buttons - evaluate arbitrary expressions in Spotlight - etc, etc showstopping bugs?! This beta time is reserved specifically for finding the bugs that may inevitably be introduced with these enhancements. We really may be creating a mess, as end users find them in our "stable" release instead. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Release-Mode-tp4751408.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Re: [Pharo-dev] someone using Magritte-Morph?

by Sean P. DeNigris

EstebanLM wrote > should instead be... Without an image handy, your change looks like good. IIRC I did the display string stuff after I implemented the relation morphs and probably forgot to change it there. ----- Cheers, Sean -- View this message in context: http://forum.world.st/someone-using-Magritte-Morph-tp4751095p4751404.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

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

by Tudor Girba

Yes, I can confirm. But, this is a known issue that in practice has little impact, and it was not related to the issue of rendering in Athens. So, from my point of you, the critical issue is now solved. Thanks! :) Doru On Fri, Mar 28, 2014 at 3:33 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > yes but if you uncheck and recheck freetype > the embedded fonts are lost > -> substition > -> substitution failed. > -> get a strike font and boum. > > Can you confirm? > > On 28 Mar 2014, at 15:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Excellent. > > I confirm the same result in the latest Moose image (which no longer loads > anything related to Athens). > > It works out of the box without any resetting of the fonts (by using the > already installed Source Sans Pro. > > Cheers, > Doru > > > <a WorldMorph(511705088) [wo.png> > > > On Fri, Mar 28, 2014 at 3:15 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> >> >> On 28 March 2014 15:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> 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 >>> >> >> and that code snippet works only if you have FreeSans font in your >> system.. which not exists on Mac OS (at least in my installation).. >> >> i took the latest pharo 3.0 image: >> >> curl get.pharo.org/30 | bash >> % Total % Received % Xferd Average Speed Time Time Time >> Current >> Dload Upload Total Spent Left >> Speed >> 100 2587 100 2587 0 0 70999 0 --:--:-- --:--:-- --:--:-- >> 421k >> Downloading the latest 30 Image: >> http://files.pharo.org/image/30/latest.zip >> Pharo.image >> 193-51-236-207:pharo sig$ ./pharo-ui Pharo.image >> >> - went to font settings and updated the font list from system. >> >> >> And then evaluated: >> >> AthensSceneView new scene: [ :canvas | |s| >> canvas setFont: (LogicalFont familyName: 'Arial' >> 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 here's what i got: >> <Screen Shot 2014-03-28 at 3.11.25 PM.png> >> >> And the screenshot you given cannot be true, because 20 points font size >> should be much larger than 10 point (the font used for label above with >> zoom/pan metrics). >> >> Note, i did not loaded anything into pharo image.. just evaluated the >> above snippet.. >> on my machine, which is: 10.8.3 mac os >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > 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] [Moose-dev] Re: Re: Fwd: Font problem is still there

by Blondeau Vincent

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 15:39 Ã : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there In Pharo 3.0 this is is normal because FreeSans does not exist. I think that we should embed a default FT font and use is as default. Isn't the StandardFonts defaultFont ? Vincent Now since embedded fonts are lost when reloading Freetrype fonts. The reloading of FreeType should be fixed. Stef 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] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by Blondeau Vincent

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 15:30 Ã : Moose-related development Cc : Pharo Development List Objet : [Moose-dev] Re: [Pharo-dev] Re: Re: Fwd: Font problem is still there On 28 Mar 2014, at 14:55, Tudor Girba <tudor(a)tudorgirba.com<mailto:tudor@tudorgirba.com>> wrote: In the Moose image, the fonts are already set to free type fonts. yes but if you uncheck and recheck freetype the embedded fonts are lost -> substition -> substitution failed. -> get a strike font and boum. I confirm ! [cid:image001.png@01CF4A9B.F64977F0] [cid:image002.png@01CF4A9B.F64977F0] And if you can see under the A character, there is a square that should not be here... (under w7) Vincent Doru On Fri, Mar 28, 2014 at 2:50 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: No, I did not change the Free type in the pharo settings. But if I do it under Moose, I got : <image001.png> De : moose-dev-bounces(a)iam.unibe.ch<mailto:moose-dev-bounces@iam.unibe.ch> [mailto:moose-dev-bounces@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. -- www.tudorgirba.com<http://www.tudorgirba.com/> "Every thing has its own flow" _______________________________________________ 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 ________________________________ 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] [Moose-dev] Re: Re: Fwd: Font problem is still there

by Pharo4Stef

yes but if you uncheck and recheck freetype the embedded fonts are lost -> substition -> substitution failed. -> get a strike font and boum. Can you confirm? On 28 Mar 2014, at 15:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Excellent. > > I confirm the same result in the latest Moose image (which no longer loads anything related to Athens). > > It works out of the box without any resetting of the fonts (by using the already installed Source Sans Pro. > > Cheers, > Doru > > > <a WorldMorph(511705088) [wo.png> > > > On Fri, Mar 28, 2014 at 3:15 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 28 March 2014 15:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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 > > and that code snippet works only if you have FreeSans font in your system.. which not exists on Mac OS (at least in my installation).. > > i took the latest pharo 3.0 image: > > curl get.pharo.org/30 | bash > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 2587 100 2587 0 0 70999 0 --:--:-- --:--:-- --:--:-- 421k > Downloading the latest 30 Image: > http://files.pharo.org/image/30/latest.zip > Pharo.image > 193-51-236-207:pharo sig$ ./pharo-ui Pharo.image > > - went to font settings and updated the font list from system. > > > And then evaluated: > > AthensSceneView new scene: [ :canvas | |s| > canvas setFont: (LogicalFont familyName: 'Arial' 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 here's what i got: > <Screen Shot 2014-03-28 at 3.11.25 PM.png> > > And the screenshot you given cannot be true, because 20 points font size should be much larger than 10 point (the font used for label above with > zoom/pan metrics). > > Note, i did not loaded anything into pharo image.. just evaluated the above snippet.. > on my machine, which is: 10.8.3 mac os > > -- > Best regards, > Igor Stasenko. > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

March 28, 2014

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

by Pharo4Stef

On 28 Mar 2014, at 15:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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. but is it? Can you check? > > 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. > > > <an AthensSceneView(824442880).png> > > Doru > > > -- > Best regards, > Igor Stasenko. > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

March 28, 2014

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

by Tudor Girba

Excellent. I confirm the same result in the latest Moose image (which no longer loads anything related to Athens). It works out of the box without any resetting of the fonts (by using the already installed Source Sans Pro. Cheers, Doru [image: Inline image 2] On Fri, Mar 28, 2014 at 3:15 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 28 March 2014 15:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> 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 >> > > and that code snippet works only if you have FreeSans font in your > system.. which not exists on Mac OS (at least in my installation).. > > i took the latest pharo 3.0 image: > > curl get.pharo.org/30 | bash > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 2587 100 2587 0 0 70999 0 --:--:-- --:--:-- --:--:-- > 421k > Downloading the latest 30 Image: > http://files.pharo.org/image/30/latest.zip > Pharo.image > 193-51-236-207:pharo sig$ ./pharo-ui Pharo.image > > - went to font settings and updated the font list from system. > > > And then evaluated: > > AthensSceneView new scene: [ :canvas | |s| > canvas setFont: (LogicalFont familyName: 'Arial' > 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 here's what i got: > [image: Inline images 2] > > And the screenshot you given cannot be true, because 20 points font size > should be much larger than 10 point (the font used for label above with > zoom/pan metrics). > > Note, i did not loaded anything into pharo image.. just evaluated the > above snippet.. > on my machine, which is: 10.8.3 mac os > > -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "Every thing has its own flow"

March 28, 2014

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

by Igor Stasenko

On 28 March 2014 15:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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 > and that code snippet works only if you have FreeSans font in your system.. which not exists on Mac OS (at least in my installation).. i took the latest pharo 3.0 image: curl get.pharo.org/30 | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2587 100 2587 0 0 70999 0 --:--:-- --:--:-- --:--:-- 421k Downloading the latest 30 Image: http://files.pharo.org/image/30/latest.zip Pharo.image 193-51-236-207:pharo sig$ ./pharo-ui Pharo.image - went to font settings and updated the font list from system. And then evaluated: AthensSceneView new scene: [ :canvas | |s| canvas setFont: (LogicalFont familyName: 'Arial' 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 here's what i got: [image: Inline images 2] And the screenshot you given cannot be true, because 20 points font size should be much larger than 10 point (the font used for label above with zoom/pan metrics). Note, i did not loaded anything into pharo image.. just evaluated the above snippet.. on my machine, which is: 10.8.3 mac os -- Best regards, Igor Stasenko.

March 28, 2014