Thanks for you suggestion I will check how to implement a registration mechanism. I was wondering if I missed the obvious. Stef

i'd like to point out, that there is of course easy brute-force solution to this problem (simply put dirty patch to force re-loading fonts)..

however, i think we should wisely consider, how to deal with it in graceful manner by providing a font-registration mechanism for any potential 3-rd party package(s). Like that, we will solve the problem for longer time period than just the single next day.

-- Best regards, Igor Stasenko.

Thanks I will have a look. I was thinking to put in place a registration mechanism. Stef On 30 Mar 2014, at 19:56, Ben Coman <btc@openInWorld.com> wrote:

Pharo4Stef wrote:

...

Thanks for you suggestion I will check how to implement a registration mechanism. I was wondering if I missed the obvious.

Stef

...

i'd like to point out, that there is of course easy brute-force solution to this problem (simply put dirty patch to force re-loading fonts)..

however, i think we should wisely consider, how to deal with it in graceful manner by providing a font-registration mechanism for any potential 3-rd party package(s). Like that, we will solve the problem for longer time period than just the single next day.

-- Best regards, Igor Stasenko.

I've uploaded a possible solution. I learnt something new today. That is very cool to be able to embed fonts in the image like that. cheers -ben

On 1 April 2014 11:34, Tudor Girba <tudor@tudorgirba.com> wrote:

I reviewed the changes of Ben, and he implemented a registration mechanism based on subclassing an abstract font class. I would prefer a registration mechanism based on pragmas that is similar to the settings one.

yeah, could be something like:

myFonts: fontManager <embeddedFonts> ^ fontManager addFonts: { A. B. C. }

Doru

On Tue, Apr 1, 2014 at 11:01 AM, Pharo4Stef <pharo4Stef@free.fr> wrote:

...

Thanks I will have a look. I was thinking to put in place a registration mechanism.

Stef

On 30 Mar 2014, at 19:56, Ben Coman <btc@openInWorld.com> wrote:

...

Pharo4Stef wrote:

...

Thanks for you suggestion I will check how to implement a registration

mechanism.

...

I was wondering if I missed the obvious.

Stef

...

i'd like to point out, that there is of course easy brute-force solution to this problem (simply put dirty patch to force re-loading fonts)..

however, i think we should wisely consider, how to deal with it in graceful manner by providing a font-registration mechanism for any potential 3-rd party package(s). Like that, we will solve the problem for longer time period than just the single next day.

-- Best regards, Igor Stasenko.

I've uploaded a possible solution. I learnt something new today. That is very cool to be able to embed fonts in the image like that. cheers -ben

-- www.tudorgirba.com

"Every thing has its own flow"

-- Best regards, Igor Stasenko.

On 1 April 2014 14:56, Ben Coman <btc@openinworld.com> wrote:

I only did the simplest thing that I could think of. I now notice it has the downside of dirtying the package. I'll have a go at pragma solution. What would you suggest to name the pragma? <embeddedFont> ?

<embeddedFontS> or <extraFontS>

and method should take an argument - the font manager instance, so the method's implementor can control the way how to register fonts.. else if it will be <embeddedFont> then it will imply that method will have to answer a single instance of single font... which will mean, you'll have to implement a method per each font.. which is not always a good way, in case if you want a centralized control over registering a bunch of fonts at once, instead of duplicating same code over may methods.

cheers -ben

-- Best regards, Igor Stasenko.