[Pharo-dev] About fonts (again)
stepharo at free.fr
Tue Apr 22 15:26:47 EDT 2014
I agree with you :). My goal is not to drop strike fonts because I think
that the code is working and it can be useful
for some people. I just want to make sure that StandardFonts (TextStyle
and others...) does not mess up FreeType
and StrikeFonts. We got a lot of problems with this for our clients.
On 22/4/14 09:09, Nicolas Cellier wrote:
> 2014-04-22 6:30 GMT+02:00 Tudor Girba <tudor at tudorgirba.com
> <mailto: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
> <mailto:stepharo at free.fr>> wrote:
> when freetype is on do you think that it makes sense to have
> proposed as default fonts? Like it is done right now, I get
> bitmapVera even if I
> want to see FreeType fonts.
> www.tudorgirba.com <http://www.tudorgirba.com>
> "Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev