[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: QPainter and multi-component beziers
From:       "Dirk Schönberger" <dirk.schoenberger () sz-online ! de>
Date:       2003-03-10 15:54:15
[Download RAW message or body]


> Hmmm... my serious suggestion is - do not try to invent single API,
> covering onscreen and printer rendering. IMHO Windows, Qt, StarOffice
> and probably many other have shot themselves to leg by trying to
> do that.
> There can be common frontend, of course, for apps with simpler needs,
> but keeping separate specialized rendering API-s IMHO deserves
> extra effort.

QPainterPaintDevice is supposed to be a real short term solution.
I think you need a common API for screen output and print output.
But it should be more printer oriented than oriented to putting pixels to
screen. A nice API is something like Display Postscript or MacOS X's Quartz
API, instead of, like X core API, GDI or the like.

The paint device pattern allows you to introduce device specific methods
where they are needed, instead of in some over complex superclass. Device
specific features for PS printers could be things like PPD support, the
supported Postscript level, pagination and the like.

> Other than that, if I'll find a little spare time, I'll try to
> write down my ideas about text API. This got halfway implemented in
> gnome-print, but AFAIK no application ever used it. But I still
> believe it is The Right Thing to do ;-)

This would be interesting.

Regards
Dirk
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]