I am about to fix some issues related to TextMorphs and fonts:
wrong choose list from TextMorph editor halo chooseStyle halo from TextMorph lists only one StrikeFont choose Font halo from TextMorph lists only one StrikeFont But I have some questions: TextStyle and fonts, this is bound to StrikeFonts for now, because only StrikeFonts register themself at "TextSharedInformation" and therefore: TextStyle actualTextStyles -> only lists the one Font "Bitmap DejaVu Sans". There are other places that work with TextStyle default / TextStyle .... Should I add the FreeType fonts to TextStyles TextSharedInformation or should I use "LogicalFontManager allFamilies" instead of "TextStyle actualTextStyles"`? I would like to remove/cleanup all places where we use some TextStyle methods that only work for StrikeFonts, but I don't know what was the idea behind this current state, that only works partly. Remove and Replace TextStyle with LogicalFontManager or use TextStyle for Strike and FreeType fonts? thanks in advance nicolai |
2015-05-17 19:01 GMT+02:00 Nicolai Hess <[hidden email]>:
Anyone?
|
In reply to this post by Nicolai Hess
Hi nicolai
this part is a epic mess. Just for the record we (ben and me) extracted from a global dictionary TextConstants :) TextSharedInformation It was strange to have a changing part in a TextConstants. So TextSharedInformation is really something that we can clean/kill/replace. Now I think that the fact that the "findBestFont" when request for a vectorial font may return a strikefont is a bug nest.
No idea. To me it looks like a huge patch. I do not know. I have the impression that LogicalFontManager is better.
No thank you in advance :)
|
In reply to this post by Nicolai Hess
Le 15/6/15 10:48, Nicolai Hess a
écrit :
Did you see the notes I was taking when I enter this part of the junggle for the first time? This is in pharo roadmap and if you take action I will make sure that all the changes get integrated fast so that you do not lose time with lag. Stef |
Free forum by Nabble | Edit this page |