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

List:       koffice-devel
Subject:    Re: Explanation on WP vs DTP modes in KWord (Re: Kde-cvs-digest request for information)
From:       Nicolas Goutte <nicog () snafu ! de>
Date:       2002-11-30 16:26:01
[Download RAW message or body]

I think the problem is that we need more control at print level. As long as we 
do not have it, I do not think that abandonning QPainter makes much sense, as 
you need it again for printing.

(But do not forget: we need to use QPicture in a way or another for 
compactibility to KWord/KPresenter 1.1. That makes it pretty hard to discard 
QPainter.)

Have a nice day/evening/night!

On Saturday 30 November 2002 15:43, Dirk Schönberger wrote:
> > a) Scribus uses completely different drivers for his printing output than
> > KOffice
> >     Therefore it would be impossible to get the high quality output of
>
> Scribus
>
> >     when it's run as a part of KOffice.
> >
> > If a) is (still) true then perhaps it'd be worth investigating the
> > Scribus printing code (by someone who knows what they're looking at of
> > course,
>
> i.e.
>
> > "not me"[tm] ;-)
>
> Do you think it would be worthwhile to work for a better imaging model in
> KOffice?
> For purely graphical elements (vector paths) the code in koffice/karbon
> could be used, but I think the text functionality is not quite up to par of
> e.g. KoText.
> IMHO this would mean KOffice specific graphics code, so that the current
> QPainter based graphics should be abandoned.
> Instead a more powerful imaging model should be supported, similar to
> things like
> Postscipt/PDF/SVG, Java2D or gnome-print.
>
> Regards
> Dirk
>
>
>
>
>
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@mail.kde.org
> http://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]