> > Well, but this does not solve the problem, I am dealing with (or
> > does it? - I am really dumb with KDE). I want sodipodi to pick up
> > whatever native printing subsystem (libgnomeprint under gnome,
> > KDE print under KDE, Windows GDI under win32) - either compile-time
> > or better yet, as loadable module. Not sure about KDE, but neither
> > libgnomeprint nor windows GDI accept postscript input - so I have
> > to implement custom output code anyways.

> QT does not allow PostScript input either. (That is one of our biggest
> problems in KOffice.)

I think the real problem is that KPrinter and friends not allowing custom
Postscript generators.
If this wasn't so, you could plugin your own Postscript generator.
This alone would rather make WYSIWIG work rather problematic, because your
print output would become more capable than your screen output, because
screen could only handley by QPainter.
KPainter tries to solve this problem by making a more capable API available
for screen and print.

Rgeard
Dirk


 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<