28 Mar
2014
28 Mar
'14
2:18 p.m.
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:
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.
28 Mar
28 Mar
2:27 p.m.
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"
2:36 p.m.
+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@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@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@lists.pharo.org<mailto:pharo-dev@lists.pharo.org>>
Reply-To: Pharo Development List
<pharo-dev@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@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.
2:42 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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"
2:44 p.m.
New subject: [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] 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.
2:45 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
Did you check that you get the latest version of athens 2.5 ?
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:
<an AthensSceneView(824442880).png>
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 :
<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] 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.
--
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
2:48 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
Yes, I did. The script loads the latest development version which is 2.5.
Doru
On Fri, Mar 28, 2014 at 2:45 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr
wrote:
> Did you check that you get the latest version of athens 2.5 ?
>
>
> 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:
>
> <an AthensSceneView(824442880).png>
>
> 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 :
>>
>> <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(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.
>>
>
>
>
> --
> 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
>
>
>
> _______________________________________________
> 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"
2:50 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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@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@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@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@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@lists.pharo.org<mailto:pharo-dev@lists.pharo.org>>
Reply-To: Pharo Development List
<pharo-dev@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@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.
2:55 p.m.
New subject: [Pharo-dev] Re: Re: Fwd: Font problem is still there
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"
2:57 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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.
3 p.m.
New subject: [Pharo-dev] Re: Re: Fwd: Font problem is still there
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;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.
3:01 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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:
--
www.tudorgirba.com
"Every thing has its own flow"
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.
3:04 p.m.
New subject: [Pharo-dev] Re: Re: Fwd: Font problem is still there
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;wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
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.
3:15 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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.
3:26 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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:
--
www.tudorgirba.com
"Every thing has its own flow"
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.
3:29 p.m.
New subject: [Pharo-dev] Re: Re: Fwd: Font problem is still there
On 28 Mar 2014, at 14:55, Tudor Girba <tudor(a)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.
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 :
<image001.png>
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> 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] 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"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3:30 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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
3:33 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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
3:39 p.m.
New subject: [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.
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] 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.
3:39 p.m.
New subject: [Pharo-dev] Re: Re: Fwd: Font problem is still there
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@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@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@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@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@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@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@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@lists.pharo.org<mailto:pharo-dev@lists.pharo.org>>
Reply-To: Pharo Development List
<pharo-dev@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@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@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.
3:46 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
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@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@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@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@lists.pharo.org<mailto:pharo-dev@lists.pharo.org>>
Reply-To: Pharo Development List
<pharo-dev@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@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.
3:46 p.m.
New subject: [Pharo-dev] Re: Fwd: Font problem is still there
Exactly.
Doru
On Fri, Mar 28, 2014 at 3:39 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr
wrote:
> 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.
> 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 <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.
>
>
>
> _______________________________________________
> 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"
4:01 p.m.
New subject: [Pharo-dev] Re: Re: Re: Fwd: Font problem is still there
Ookkayy..
so, current status:
- finally we got an agreement that big red square because of font loading
issues and font rendering artifacts is two separate issues.
Thanks!
- i am not going to address font-loading issue here and now.. (because we
spent time on it earlier today with Stef already and you should have the
report on it in separate mail).
- we seem to be agreed that it is best to use same (up-to-date version) of
software when reporting issues to work on them. Thanks again. :)
- while on linux and mac things seem to be working fine, i can confirm that
there is rendering artifacts (same as reported by Vincent) on Windows.
so i going to explore what causing this problem..
--
Best regards,
Igor Stasenko.
4:27 p.m.
New subject: [Pharo-dev] Re: Re: Re: Fwd: Font problem is still there
On 28 March 2014 16:01, Igor Stasenko <siguctua(a)gmail.com> wrote:
Ookkayy..
so, current status:
- finally we got an agreement that big red square because of font loading
issues and font rendering artifacts is two separate issues.
Thanks!
- i am not going to address font-loading issue here and now.. (because we
spent time on it earlier today with Stef already and you should have the
report on it in separate mail).
- we seem to be agreed that it is best to use same (up-to-date version) of
software when reporting issues to work on them. Thanks again. :)
- while on linux and mac things seem to be working fine, i can confirm
that there is rendering artifacts (same as reported by Vincent) on Windows.
so i going to explore what causing this problem..
... and found the cause:
On windows, for unknown reason, the structure (cairo_glyph_t) uses
different memory space alignment than on mac and linux
fieldsDesc
^ #(
ulong index;
double x;
double y;
)
on mac and linux , the size of this structure in memory = 4 + 8 + 8 = 20
bytes,
on windows, however, due to 8-byte alignment, it is 4 + 8 + 8 + (4
alignment) bytes...
this causing the effect that if you copy array of glyphs in memory,
it does not copying whole array by slightly less (because it uses wrong
struct size which is smaller than it is)..
and because of that, you got weird artefacts at the tail of string,
replaced by misplaced/invalid characters etc..
because it is basically read from uninitialized part of memory with random
data.
i going to fix structure alignment for windows from default 4 bytes to 8
bytes..
but this is not very good news.. because this affecting many things... (as
you can imagine, not only cairo/athens working with external structures,
which need to be properly aligned).
--
Best regards,
Igor Stasenko.
4:42 p.m.
New subject: [Pharo-dev] Re: Re: Re: Fwd: Font problem is still there
so, the quick and dirty fix is to put:
CairoGlyph class>>byteAlignment
NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue:
[ ^ 8 ].
^ super byteAlignment
and then:
CairoGlyph rebuildFieldAccessors
CairoGlyphsArray initialize
(note you must run this snippet each time your image changes platform)..
and i need more time to fix it for real, because it is NB issue, to
automatically recalculate the structs size
if it changes platform.. (which also means you cannot store instances of
struct in image which survive the session)
... damn.. that's going to be complicated.
---
On 28 March 2014 16:27, Igor Stasenko <siguctua(a)gmail.com> wrote:
On 28 March 2014 16:01, Igor Stasenko <siguctua(a)gmail.com> wrote:
--
Best regards,
Igor Stasenko.
Ookkayy..
so, current status:
- finally we got an agreement that big red square because of font
loading issues and font rendering artifacts is two separate issues.
Thanks!
- i am not going to address font-loading issue here and now.. (because we
spent time on it earlier today with Stef already and you should have the
report on it in separate mail).
- we seem to be agreed that it is best to use same (up-to-date version)
of software when reporting issues to work on them. Thanks again. :)
- while on linux and mac things seem to be working fine, i can confirm
that there is rendering artifacts (same as reported by Vincent) on Windows.
so i going to explore what causing this problem..
... and found the cause:
On windows, for unknown reason, the structure (cairo_glyph_t) uses
different memory space alignment than on mac and linux
fieldsDesc
^ #(
ulong index;
double x;
double y;
)
on mac and linux , the size of this structure in memory = 4 + 8 + 8 = 20
bytes,
on windows, however, due to 8-byte alignment, it is 4 + 8 + 8 + (4
alignment) bytes...
this causing the effect that if you copy array of glyphs in memory,
it does not copying whole array by slightly less (because it uses wrong
struct size which is smaller than it is)..
and because of that, you got weird artefacts at the tail of string,
replaced by misplaced/invalid characters etc..
because it is basically read from uninitialized part of memory with random
data.
i going to fix structure alignment for windows from default 4 bytes to 8
bytes..
but this is not very good news.. because this affecting many things... (as
you can imagine, not only cairo/athens working with external structures,
which need to be properly aligned).
--
Best regards,
Igor Stasenko.
5:19 p.m.
New subject: [Pharo-dev] Re: Re: Re: Fwd: Font problem is still there
https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe…
On 28 March 2014 16:42, Igor Stasenko <siguctua(a)gmail.com> wrote:
so, the quick and dirty fix is to put:
CairoGlyph class>>byteAlignment
NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue:
[ ^ 8 ].
^ super byteAlignment
and then:
CairoGlyph rebuildFieldAccessors
CairoGlyphsArray initialize
(note you must run this snippet each time your image changes platform)..
and i need more time to fix it for real, because it is NB issue, to
automatically recalculate the structs size
if it changes platform.. (which also means you cannot store instances of
struct in image which survive the session)
... damn.. that's going to be complicated.
---
On 28 March 2014 16:27, Igor Stasenko <siguctua(a)gmail.com> wrote:
--
Best regards,
Igor Stasenko.
On 28 March 2014 16:01, Igor Stasenko <siguctua(a)gmail.com> wrote:
--
Best regards,
Igor Stasenko.
Ookkayy..
so, current status:
- finally we got an agreement that big red square because of font
loading issues and font rendering artifacts is two separate issues.
Thanks!
- i am not going to address font-loading issue here and now.. (because
we spent time on it earlier today with Stef already and you should have the
report on it in separate mail).
- we seem to be agreed that it is best to use same (up-to-date version)
of software when reporting issues to work on them. Thanks again. :)
- while on linux and mac things seem to be working fine, i can confirm
that there is rendering artifacts (same as reported by Vincent) on Windows.
so i going to explore what causing this problem..
... and found the cause:
On windows, for unknown reason, the structure (cairo_glyph_t) uses
different memory space alignment than on mac and linux
fieldsDesc
^ #(
ulong index;
double x;
double y;
)
on mac and linux , the size of this structure in memory = 4 + 8 + 8 = 20
bytes,
on windows, however, due to 8-byte alignment, it is 4 + 8 + 8 + (4
alignment) bytes...
this causing the effect that if you copy array of glyphs in memory,
it does not copying whole array by slightly less (because it uses wrong
struct size which is smaller than it is)..
and because of that, you got weird artefacts at the tail of string,
replaced by misplaced/invalid characters etc..
because it is basically read from uninitialized part of memory with
random data.
i going to fix structure alignment for windows from default 4 bytes to 8
bytes..
but this is not very good news.. because this affecting many things...
(as you can imagine, not only cairo/athens working with external
structures, which need to be properly aligned).
--
Best regards,
Igor Stasenko.
9:13 p.m.
New subject: [Pharo-dev] Re: Re: Re: Fwd: Font problem is still there
thanks Igor.
I’m trying to look at the font reloading bug.
On 28 Mar 2014, at 17:19, Igor Stasenko <siguctua(a)gmail.com> wrote:
https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe…
On 28 March 2014 16:42, Igor Stasenko <siguctua(a)gmail.com> wrote:
so, the quick and dirty fix is to put:
CairoGlyph class>>byteAlignment
NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue: [ ^ 8 ].
^ super byteAlignment
and then:
CairoGlyph rebuildFieldAccessors
CairoGlyphsArray initialize
(note you must run this snippet each time your image changes platform)..
and i need more time to fix it for real, because it is NB issue, to automatically
recalculate the structs size
if it changes platform.. (which also means you cannot store instances of struct in image
which survive the session)
... damn.. that's going to be complicated.
---
On 28 March 2014 16:27, Igor Stasenko <siguctua(a)gmail.com> wrote:
On 28 March 2014 16:01, Igor Stasenko <siguctua(a)gmail.com> wrote:
Ookkayy..
so, current status:
- finally we got an agreement that big red square because of font loading issues and
font rendering artifacts is two separate issues.
Thanks!
- i am not going to address font-loading issue here and now.. (because we spent time on
it earlier today with Stef already and you should have the report on it in separate
mail).
- we seem to be agreed that it is best to use same (up-to-date version) of software when
reporting issues to work on them. Thanks again. :)
- while on linux and mac things seem to be working fine, i can confirm that there is
rendering artifacts (same as reported by Vincent) on Windows.
so i going to explore what causing this problem..
... and found the cause:
On windows, for unknown reason, the structure (cairo_glyph_t) uses different memory space
alignment than on mac and linux
fieldsDesc
^ #(
ulong index;
double x;
double y;
)
on mac and linux , the size of this structure in memory = 4 + 8 + 8 = 20 bytes,
on windows, however, due to 8-byte alignment, it is 4 + 8 + 8 + (4 alignment) bytes...
this causing the effect that if you copy array of glyphs in memory,
it does not copying whole array by slightly less (because it uses wrong struct size
which is smaller than it is)..
and because of that, you got weird artefacts at the tail of string, replaced by
misplaced/invalid characters etc..
because it is basically read from uninitialized part of memory with random data.
i going to fix structure alignment for windows from default 4 bytes to 8 bytes..
but this is not very good news.. because this affecting many things... (as you can
imagine, not only cairo/athens working with external structures, which need to be properly
aligned).
--
Best regards,
Igor Stasenko.
--
Best regards,
Igor Stasenko.
--
Best regards,
Igor Stasenko.
1 Apr
1 Apr
6:27 p.m.
New subject: [Pharo-dev] Re: Re: Re: Fwd: Font problem is still there
okay i uploaded updated configs for NativeBoost and Athens into official
repositories for these projects.
Gofer new smalltalkhubUser: 'Pharo' project: 'NativeBoost';
configuration;
load.
ConfigurationOfNativeBoost loadDevelopment.
Gofer new smalltalkhubUser: 'Pharo' project: 'Athens';
configuration;
load.
ConfigurationOfAthens loadDevelopment.
shall do the trick..
for more details see
https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe…
On 28 March 2014 21:13, Pharo4Stef <pharo4Stef(a)free.fr> wrote:
thanks Igor.
I’m trying to look at the font reloading bug.
On 28 Mar 2014, at 17:19, Igor Stasenko <siguctua(a)gmail.com> wrote:
https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe…
On 28 March 2014 16:42, Igor Stasenko <siguctua(a)gmail.com> wrote:
--
Best regards,
Igor Stasenko.
so, the quick and dirty fix is to put:
CairoGlyph class>>byteAlignment
NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue:
[ ^ 8 ].
^ super byteAlignment
and then:
CairoGlyph rebuildFieldAccessors
CairoGlyphsArray initialize
(note you must run this snippet each time your image changes platform)..
and i need more time to fix it for real, because it is NB issue, to
automatically recalculate the structs size
if it changes platform.. (which also means you cannot store instances of
struct in image which survive the session)
... damn.. that's going to be complicated.
---
On 28 March 2014 16:27, Igor Stasenko <siguctua(a)gmail.com> wrote:
--
Best regards,
Igor Stasenko.
On 28 March 2014 16:01, Igor Stasenko <siguctua(a)gmail.com> wrote:
--
Best regards,
Igor Stasenko.
Ookkayy..
so, current status:
- finally we got an agreement that big red square because of font
loading issues and font rendering artifacts is two separate issues.
Thanks!
- i am not going to address font-loading issue here and now.. (because
we spent time on it earlier today with Stef already and you should have the
report on it in separate mail).
- we seem to be agreed that it is best to use same (up-to-date version)
of software when reporting issues to work on them. Thanks again. :)
- while on linux and mac things seem to be working fine, i can confirm
that there is rendering artifacts (same as reported by Vincent) on Windows.
so i going to explore what causing this problem..
... and found the cause:
On windows, for unknown reason, the structure (cairo_glyph_t) uses
different memory space alignment than on mac and linux
fieldsDesc
^ #(
ulong index;
double x;
double y;
)
on mac and linux , the size of this structure in memory = 4 + 8 + 8 = 20
bytes,
on windows, however, due to 8-byte alignment, it is 4 + 8 + 8 + (4
alignment) bytes...
this causing the effect that if you copy array of glyphs in memory,
it does not copying whole array by slightly less (because it uses wrong
struct size which is smaller than it is)..
and because of that, you got weird artefacts at the tail of string,
replaced by misplaced/invalid characters etc..
because it is basically read from uninitialized part of memory with
random data.
i going to fix structure alignment for windows from default 4 bytes to 8
bytes..
but this is not very good news.. because this affecting many things...
(as you can imagine, not only cairo/athens working with external
structures, which need to be properly aligned).
--
Best regards,
Igor Stasenko.
3681
days inactive
3685
days old
27 comments
5 participants
participants (5)
-
Blondeau Vincent -
Igor Stasenko -
Pharo4Stef -
Stéphane Ducasse -
Tudor Girba