Fonts - Moose-dev - INF Mailman

List overview All Threads
Download

Fonts

Arrowed Edges in Roassal 2

Relations with source code

Stéphane Ducasse

8 Apr 2014 8 Apr '14

5:35 p.m.

Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef

Reply

Show replies by date

Alexandre Bergel

8 Apr 8 Apr

5:41 p.m.

Excellent! I will try ROPlatform belongs to Roassal1, and Roassal1 is deprecated. Roassal2 will not suffer from this. Alexandre On Apr 8, 2014, at 12:35 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote:

Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Reply

Stéphane Ducasse

9:17 p.m.

ok but we should fix that because so far we get red cross at client site and this is why I want to fix all the problems. On 08 Apr 2014, at 17:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:

Excellent! I will try ROPlatform belongs to Roassal1, and Roassal1 is deprecated. Roassal2 will not suffer from this. Alexandre On Apr 8, 2014, at 12:35 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote:

Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

Tudor Girba

9:15 p.m.

Hi, Thanks! Roassal1 should not be much of a problem in the Moose image given that we install the fonts by default before using Roassal. For Moose, it would be great to have the code committed, but you are right that if it breaks it would be better to wait until the fix is integrated in Pharo. I will not have much time until next week to look at this. Cheers, Doru On Tue, Apr 8, 2014 at 5:35 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr>wrote;wrote:

Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef _______________________________________________ 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"

Reply

Stéphane Ducasse

9:19 p.m.

On 08 Apr 2014, at 21:15, Tudor Girba <tudor(a)tudorgirba.com> wrote:

Hi, Thanks! Roassal1 should not be much of a problem in the Moose image given that we install the fonts by default before using Roassal.

No Because if you disable and reenable freeType you lose the font you manually loaded and then if you open roassal then you are skwred.

For Moose, it would be great to have the code committed, but you are right that if it breaks it would be better to wait until the fix is integrated in Pharo.

I hope to push it tomorrow.

I will not have much time until next week to look at this.

Ok the problem is that we have to commit in your repo with the freeType package and we do not have access.

Cheers, Doru On Tue, Apr 8, 2014 at 5:35 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote: Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef _______________________________________________ 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" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

Tudor Girba

9 Apr 9 Apr

12:35 a.m.

I added you to the repo. Doru On Tue, Apr 8, 2014 at 9:19 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr>wrote;wrote:

On 08 Apr 2014, at 21:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: Hi, Thanks! Roassal1 should not be much of a problem in the Moose image given that we install the fonts by default before using Roassal. No Because if you disable and reenable freeType you lose the font you manually loaded and then if you open roassal then you are skwred. For Moose, it would be great to have the code committed, but you are right that if it breaks it would be better to wait until the fix is integrated in Pharo. I hope to push it tomorrow. I will not have much time until next week to look at this. Ok the problem is that we have to commit in your repo with the freeType package and we do not have access. Cheers, Doru On Tue, Apr 8, 2014 at 5:35 PM, Stéphane Ducasse < stephane.ducasse(a)inria.fr> wrote:

Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef _______________________________________________ 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" _______________________________________________ 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"

Reply

Stéphane Ducasse

15 Apr 15 Apr

11:44 p.m.

not time to work on it.

I added you to the repo. Doru On Tue, Apr 8, 2014 at 9:19 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote: On 08 Apr 2014, at 21:15, Tudor Girba <tudor(a)tudorgirba.com> wrote:

Hi, Thanks! Roassal1 should not be much of a problem in the Moose image given that we install the fonts by default before using Roassal.

No Because if you disable and reenable freeType you lose the font you manually loaded and then if you open roassal then you are skwred.

For Moose, it would be great to have the code committed, but you are right that if it breaks it would be better to wait until the fix is integrated in Pharo.

I hope to push it tomorrow.

I will not have much time until next week to look at this.

Ok the problem is that we have to commit in your repo with the freeType package and we do not have access.

Cheers, Doru On Tue, Apr 8, 2014 at 5:35 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote: Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef _______________________________________________ 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" _______________________________________________ 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" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Reply

Tudor Girba

11:52 p.m.

I fixed the problem in the meantime. Doru On Tue, Apr 15, 2014 at 11:44 PM, Stéphane Ducasse < stephane.ducasse(a)inria.fr> wrote:

not time to work on it. I added you to the repo. Doru On Tue, Apr 8, 2014 at 9:19 PM, Stéphane Ducasse < stephane.ducasse(a)inria.fr> wrote:

On 08 Apr 2014, at 21:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: Hi, Thanks! Roassal1 should not be much of a problem in the Moose image given that we install the fonts by default before using Roassal. No Because if you disable and reenable freeType you lose the font you manually loaded and then if you open roassal then you are skwred. For Moose, it would be great to have the code committed, but you are right that if it breaks it would be better to wait until the fix is integrated in Pharo. I hope to push it tomorrow. I will not have much time until next week to look at this. Ok the problem is that we have to commit in your repo with the freeType package and we do not have access. Cheers, Doru On Tue, Apr 8, 2014 at 5:35 PM, Stéphane Ducasse < stephane.ducasse(a)inria.fr> wrote:

Hi guys With igor we added a registration mechanism for Freetype fonts for 13149. We fixed the one of Moose and we should publish the moose packages (but if we publish it in Moose it will break moose). Now Roassal should not cache the fonts in ROPlatform current because this means that you always get bitmap if you get bitmap the first time. So let us know how we proceed? Stef _______________________________________________ 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" _______________________________________________ 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" _______________________________________________ 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"

Reply

3904

days inactive

3911

days old

moose-dev@list.inf.unibe.ch

Manage subscription

7 comments

3 participants

tags (0)

participants (3)

Alexandre Bergel
Stéphane Ducasse
Tudor Girba