Index: [thread] [date] [subject] [author]

  From: BERNARD Sebastien <sebastien.bernard@cegetel.fr>
  To  : 'ggi-develop@eskimo.com' <ggi-develop@eskimo.com>
  Date: Wed, 19 May 1999 10:14:11 +0200

RE: Some precision about raster operation (Was RE: some though ab out raster operations)

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BEA1CF.9C3886D0
Content-Type: text/plain



> For an extension this is no problem. And if it is done as I have in mind, 
> one could even avoid having to link the base extension lib with freetype,
> but only a plugin rendering lib.
	[BERNARD Sebastien]  I agree, the freetype stuff was there as an
example. I had in mind something more generic. Load a font, generate the
bitmap, use the bitmap on the visual. Behind could be something like :
		1 - bitmap - X11 fonts, amiga, atari and so on - (preload
the bitmap as it were rendered)
		2 - truetype (use freetype)
		3 - Type1 (use the t1lib)
		4 - Speedo ? (maybe the same as 3)
		5 - new stuff from adobe (forgot the name - something like
fontmaster)
		5 - anything I'm not aware of... :)
	With a special extension for each of them (like the displays I
think). The front extension could be used to manage the memory (caching the
glyphs, the outlines), performs mapping between fonts required and real name
of the font file, decision about which kind of fonts are the best, etc... I
wanna play with the T1lib too before thinking about a global api.

------_=_NextPart_001_01BEA1CF.9C3886D0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>RE: Some precision about raster operation (Was RE: some though =
ab out  raster operations)</TITLE>
</HEAD>
<BODY>
<BR>
<BR>
<UL>
<P><FONT SIZE=3D2 FACE=3D"Arial">For an extension this is no problem. =
And if it is done as I have in mind, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">one could even avoid having to link =
the base extension lib with freetype,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">but only a plugin rendering =
lib.</FONT>
<BR><B><I><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">[BERNARD =
Sebastien]</FONT></I></B><I></I> <FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial"> I agree, the freetype stuff was there as an example. I =
had in mind something more generic. Load a font, generate the bitmap, =
use the bitmap on the visual. Behind could be something like =
:</FONT></P>

<P>        <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">1 - bitmap - X11 fonts, amiga, atari and so on =
- (preload the bitmap as it were rendered)</FONT>
<BR>        <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">2 - truetype (use freetype)</FONT>
<BR>        <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">3 - Type1 (use the t1lib)</FONT>
<BR>        <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">4 - Speedo ? (maybe the same as 3)</FONT>
<BR>        <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">5 - new stuff from adobe (forgot the name - =
something like fontmaster)</FONT>
<BR>        <FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Arial">5 - anything I'm not aware of... :)</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">With a special =
extension for each of them (like the displays I think). The front =
extension could be used to manage the memory (caching the glyphs, the =
outlines), performs mapping between fonts required and real name of the =
font file, decision about which kind of fonts are the best, etc... I =
wanna play with the T1lib too before thinking about a global =
api.</FONT></P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01BEA1CF.9C3886D0--

Index: [thread] [date] [subject] [author]