Index: [thread] [date] [subject] [author]
  From: BERNARD Sebastien <sebastien.bernard@cegetel.fr>
  To  : 'ggi-develop@eskimo.com' <ggi-develop@eskimo.com>
  Date: Tue, 18 May 1999 10:06:04 +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_01BEA105.49638970
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



> -----Message d'origine-----
> De:	Andreas Beck [SMTP:becka@rz.uni-duesseldorf.de]
> Date:	lundi 17 mai 1999 21:56
> =C0:	ggi-develop@eskimo.com
> Objet:	Re: Some precision about raster operation (Was RE: some
> though ab out  raster operations)
>=20
> > BS] I wanted to do some font
> > drawing, but to display something are simple as a truetype font=20
>=20
> As simple as a truetype font ???
	[BERNARD Sebastien]  Yes, the rendering engine take everything in
charge. Just give it a bitmap or a raster then let him work. This is =
device
independant so has nothing to do with GGI. Seeing from application, we =
gets
a pixmap that we must copy to the main target (with a ggiCrossBlit). =
For the
GGI specific part it is not more difficult than a=20

> Show me a graphics lib other than Win GDI or the Apple stuff it was
> derived from that includes this. Actually try this in X without using =

> an external fontserver.
	[BERNARD Sebastien]  Of course, X do it. I am not talking about the
rendering stuff. But have a look to the GCFunction attribute of the XGC =
in X
window. I am just saying that the logic combinaison of 2 images (from =
the
same or different format) belongs to the core functions. Without this
functions you cannot process image through the API functions. You have =
to
peek and poke into the directbuffer (which is a bad thing in an
application). Effectively font rendering belongs to some high level
extension, not bit planes manipulation.

> > I have to load a lot of extension. I tought it was core service =
(low
> level).
>=20
> Rendering fonts is IMHO about as lowlevel as OpenGL.
>=20
> And what do you mean with "a lot of" ?
	[BERNARD Sebastien]  (one :))) the overhead to open one extension is
90% of the code to load n extension :-) The libggi2d. The stuff is not =
ready
yet, and is not distributed. There is a lot of work to  do on it. The =
fact
that the libraries are distributed into different packages implies that =
all
packages must be self-contained. The separation ggi/gii is obvious. The
separation ggi/ggi2d is not. In my mind (troubled / brain-damaged ?), =
the
ggi2d was high-level stuff (was a dependance relation between ggi2d -> =
ggi
like gtk->gdk). You are rather thinking about it like ggi2.

> Loading an extension is as simple as adding a #include, an
> extInit()/Exit()
> and an ExtAttach()/Detach() pair to the app.
>=20
> CU, ANdy
>=20
> --=20
> =3D Andreas Beck                    |  Email :
> <andreas.beck@ggi-project.org> =3D

------_=_NextPart_001_01BEA105.49638970
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<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=3D1 FACE=3D"Arial">-----Message d'origine-----</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">De:    </FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">Andreas Beck [SMTP:becka@rz.uni-duesseldorf.de]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Date:  </FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">lundi 17 mai 1999 21:56</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">=C0:     </FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">ggi-develop@eskimo.com</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Objet: </FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Re: Some precision about raster operation (Was =
RE: some though ab out  raster operations)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">> BS] I wanted to do some =
font</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">> drawing, but to display =
something are simple as a truetype font </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">As simple as a truetype font =
???</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"> Yes, the rendering engine take everything in charge. =
Just give it a bitmap or a raster then let him work. This is device =
independant so has nothing to do with GGI. Seeing from application, we =
gets a pixmap that we must copy to the main target (with a =
ggiCrossBlit). For the GGI specific part it is not more difficult than =
a</FONT> </P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Show me a graphics lib other than Win =
GDI or the Apple stuff it was</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">derived from that includes this. =
Actually try this in X without using </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">an external fontserver.</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"> Of course, X do it. I am not talking about the =
rendering stuff. But have a look to the GCFunction attribute of the XGC =
in X window. I am just saying that the logic combinaison of 2 images =
(from the same or different format) belongs to the core functions. =
Without this functions you cannot process image through the API =
functions. You have to peek and poke into the directbuffer (which is a =
bad thing in an application). Effectively font rendering belongs to =
some high level extension, not bit planes manipulation.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">> I have to load a lot of =
extension. I tought it was core service (low level).</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Rendering fonts is IMHO about as =
lowlevel as OpenGL.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">And what do you mean with "a lot =
of" ?</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"> (one :))) the overhead to open one extension is 90% of =
the code to load n extension :-) The libggi2d. The stuff is not ready =
yet, and is not distributed. There is a lot of work to  do on it. =
The fact that the libraries are distributed into different packages =
implies that all packages must be self-contained. The separation =
ggi/gii is obvious. The separation ggi/ggi2d is not. In my mind =
(troubled / brain-damaged ?), the ggi2d was high-level stuff (was a =
dependance relation between ggi2d -> ggi like gtk->gdk). You are =
rather thinking about it like ggi2.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Loading an extension is as simple as =
adding a #include, an extInit()/Exit()</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">and an ExtAttach()/Detach() pair to =
the app.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">CU, ANdy</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">-- </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">=3D Andreas =
Beck           &n=
bsp;        |  Email :  =
<andreas.beck@ggi-project.org> =3D</FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01BEA105.49638970--

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