> My method (direct insertion into a sparse array) is almost certainly
> better when there is enough memory to create an array with a slot
> for every pixel in the bitmap, but if not, it falls back on
> quicksort.
Hmm. What about adding your algorithm, falling back to the stuff what
FreeType has currently implemented (i.e., the linked list)?
> I am also aware that FreeType's sole purpose is to rasterize glyphs,
> while mine is also to rasterize large arbitrary shapes.
> Nevertheless, these aims tend to converge as display resolution
> improves; at modern resolutions of around 200dpi, 18pt glyphs are as
> large as 50 x 50 pixels.
I would like to see the library as generic as possible, of course
without sacrificing good performance for its main purpose, rasterizing
of glyphs. Thus any improvement is highly welcomed.
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
