Re: [Freetype] WIN CE Port and Usage ?

[Ed Keith]

Hi Jeremy,

Doesn't WinCE provide TrueType support directly like other Windows OS's,  or 
are you looking to use FreeType for low-level graphics to support paths and 
bezier curves?

If WinCE native fonts are not TrueType, they are most likely pre-rendered 
bitmap fonts (what is the font file extension? .fon, .fnt?).  If pre-rendered 
WinCE bitmap fonts are already "*very* slow", I doubt FreeType will help since 
rasterization to character bitmaps is an additional added overhead that isn't 
needed with bitmap fonts.  Though fixed in terms of given sizes, pre-rendered 
bitmap fonts should be the fastest to draw.

Best Regards,
Ed


At 06:01 PM 12/16/01, you wrote:
>Hi,
>
>I am developing a graphics application for WINCE.  WINCE as you may know is
>very limited in its graphics ability, specifically paths and bezier curves.
>I have had to replace a significant part of the CE graphics API with my own
>code and now have a hybrid API that provides nearly all the graphics
>elements I need.
>
>CE fonts are still a problem as they are *very* slow.  I was wondering if
>freetype would help with that, so I guess my questions are :
>
>1. Has freetype been ported to CE successfully ? (I have an EVC++ project
>that compiles the library O.K. but I have not tried it out yet)
>
>2. Can I access the path information for individual glyphs as a complex
>polygon (ie after bezier reduction but before rendering to a bitmap)
>
>3. How do I continue to use the WINCE native fonts but render them with the
>freetype engine?
>
>4. Is freetype any faster than WINCE?
>
>Thanks
>
>Jeremy