Re: New release of libart/freetype-backend

[Alexander Malmberg]

> > GSSet(Stroke,Fill)(Color,Colorspace)
> > aren't implemented since I don't know what they're supposed to do. None
> > of the other backends implement them, and gui never uses them. Why do
> > they exist?
> 
> That's for Quartz compatibilty. Quartz defines different colors for
> stroking and filling, mostly for convienience I suppose. Also see some
> of the GS functions in the Text section. I think some of this can be
> implemented in gsc, but I haven't gotten around to it yet.

I'll get the pdf reference manual and see if I can figure out how
they're supposed to work.

> > c.
> > What exactly am I supposed to do about view flipping? Does it belong in
> > the backend at all? Currently I just flip the y axis when drawing text
> > if viewIsFlipped is YES, and this seems to work.
> 
> I've always thought that was a big hack, but I'm not sure how to remove
> it. But yes, that's pretty much what you're supposed to do.

Couldn't NSStringDrawing handle it completely? It already takes care of
moving the current point to the right place, so it could do
PSscale(1.0,-1.0) before and after the PSshow() too.

> > d.
> > How sophisticated should my font rendering be? Should I do kerning and
> > stuff in DPSshow:?
> >
> > e.
[snip]
> > glyph for a character (with different fallback fonts for different fonts
> > and stuff like that), or should it leave all that to -gui?
> >
> 
> Well my current grand scheme ;-) is to have gui use Pango for text
> layout and rendering. The more I look at it the more it seems to fit
> right in and solve many many problems. Pango would do all this stuff.

My original plan was to start out by using freetype and switching to
pango when I had a working version, ie. now, but when I started looking
closer at that I noticed that Pango requires glib 2.0 :/. Having gnustep
depend on glib seems wrong.

- Alexander Malmberg