On 22/4/14 14:19, Tudor Girba wrote:
I do not see what this has to do with anything.
Right now we are offering the possibility to not be able to load
FreeType fonts and this leads to buggy behavior when the user starts
playing with that toggle.
In fact this is buggy even without that. The system reports strike and
freetype fonts when we are in ft mode :(
I fail to see why we need the option in the first place. All I am
saying is that we should remove the option from the settings browser
and simply have the freetype fonts enable all the time. This means
that you will still be able to load the bitmap fonts without problems
just like before.
And it is our (as builders of Pharo) responsibilities to design. The
user can say if he likes it or not and in our case can even try to
contribute. But, this does not take the design responsibility from our
shoulders.
Doru
On Tue, Apr 22, 2014 at 1:48 PM, Sergi Reyner <sergi.rey...@gmail.com
<mailto:sergi.rey...@gmail.com>> wrote:
2014-04-22 8:21 GMT+01:00 Tudor Girba <tu...@tudorgirba.com
<mailto:tu...@tudorgirba.com>>:
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?
Well, look at it this way: who should be able to have the final
word on what side of the speed/prettiness dichotomy Pharo should
be: the user or the system?
Cheers,
Sergi
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
