[Pharo-dev] Font problem identified

Tudor Girba tudor at tudorgirba.com
Tue Apr 1 05:34:13 EDT 2014


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.

Doru


On Tue, Apr 1, 2014 at 11:01 AM, Pharo4Stef <pharo4Stef at 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 at 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"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20140401/f1efced6/attachment-0002.html>


More information about the Pharo-dev mailing list