Le 15/6/15 10:48, Nicolai Hess a écrit :
2015-05-17 19:01 GMT+02:00 Nicolai Hess <nicolaihess@web.de <mailto:nicolaihess@web.de>>:
I am about to fix some issues related to TextMorphs and fonts:
15402 <https://pharo.fogbugz.com/default.asp?15402> wrong choose list from TextMorph editor halo
15552 <https://pharo.fogbugz.com/default.asp?15552> chooseStyle halo from TextMorph lists only one StrikeFont 15553 <https://pharo.fogbugz.com/default.asp?15553> 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?
Anyone?
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