[Pharo-dev] Font problem identified

Igor Stasenko siguctua at gmail.com
Tue Apr 1 09:03:47 EDT 2014

On 1 April 2014 14:56, Ben Coman <btc at 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>

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
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20140401/86ccd56b/attachment-0002.html>

More information about the Pharo-dev mailing list