In reply to Lee Brown <[EMAIL PROTECTED]>
>
>> first bringing the happines of anti-aliased truetype/postscript
>> fonts
>
>Maybe you would like to try my libft for this. I understand you
>probably have your own subroutines but nevertheless you may like it.
>It might serve GGI well as a whole to get your feedback.
your library seems quite nice, but for my purposes using freetype
directly is really simple enough... i guess what's really missing in
freetype is a good documented complete example. 'dviv' took care of
that, and the terminal emulator will be even better at that.
of course once you do it once, everything else is just repeated code,
and that's what libraries are for. me, i like fine-grained control
over everything i can throw a code at, so i guess i'll continue to use
freetype directly for a while. other people may not want to learn
about it and just want to `typeset the darn text.'
the only problem i see with libfnt is that in principle it is a
library for `generic font processing/rendering' that uses a library
for `generic font processing' itself. i see you can use X fonts, for
example; but wouldn't it be a lot better if, instead of handling X
fonts separately, you wrote a X font driver for freetype? i guess it
would. so here's my suggestion:
* write your library as a `renderer for freetype', not
a `generic font processor/renderer'. freetype already does half of
that job! your library would still be very useful to all people who
don't want to be involved with freetype internals, glyph caching,
etc etc.
* if you want support for file formats not yet available in freetype,
don't do it in your lib. that's exactly the kind of work freetype
tries to eliminate, so in a way you are using freetype the wrong
way. the right way is to write a new freetype driver for the format
you want to support. this way everybody gets happy --- you
contribute to your library and to everybody else who uses freetype.
(i for one would get happy because i could use x fonts in my
emulator.)
--
Cesar Augusto Rorato Crusius __o __o __o __o __o
Stanford University _`\<, _`\<, _`\<, _`\<, _`\<,
e-mail:[EMAIL PROTECTED] (_)/(_) (_)/(_) (_)/(_) (_)/(_) (_)/(_)
www.stanford.edu/~crusius
o _ _ _
__o __o __o __o /\_ _ \\o (_)\__/o (_)
_`\<, _`\<, _`\<, _`\<, _>(_) (_)/<_ \_| \ _|/' \/
(_)/(_) (_)/(_) (_)/(_) (_)/(_) (_) (_) (_) (_)' _\o_
He who sacrifices functionality for ease of use
Loses both and deserves neither
