[Pharo-dev] About fonts (again)
tudor at tudorgirba.com
Tue Apr 22 03:21:15 EDT 2014
I think my message generated a misunderstanding.
I am not arguing for dropping of bitmap fonts at all. I am only arguing for
removing the option of not having freetype. People on slow devices will
still be able to use the bitmap fonts.
Is that wrong?
On Tue, Apr 22, 2014 at 9:09 AM, Nicolas Cellier <
nicolas.cellier.aka.nice at gmail.com> wrote:
> 2014-04-22 6:30 GMT+02:00 Tudor Girba <tudor at tudorgirba.com>:
> One question is why do still have the disable free type fonts option?
>> This was useful when free type was still in development, but I think now
>> it is no longer useful.
>> Or are there still use cases for it?
> At the risk of repeating myself (that's maybe 10 times I say it here, but
> it's like shouting in the desert...) ,
> freetype is pretty inefficient because it displays characters one by one
> (call a primitive foreach and every character).
> So if you are on a not so fast device, strike fonts are still a good
> option because the primitive displays groups of characters in a batch.
> So please, please, please, for once before breaking things that works and
> replacing them by a thing that works only partially,
> do it the other way around:
> - first make it fully work (that means add a new freetype primitive
> displaying batch of chars)
> - then drop any historical bits you want
> Of course, you are free to completely drop support for slow machines, but
> it must be consciously.
>> On Mon, Apr 21, 2014 at 7:32 PM, stepharo <stepharo at free.fr> wrote:
>>> when freetype is on do you think that it makes sense to have strikeFont
>>> proposed as default fonts? Like it is done right now, I get bitmapVera
>>> even if I
>>> want to see FreeType fonts.
>> "Every thing has its own flow"
"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev