KDE Printing API Request (Was: [REMINDER] KDE Dev Platform FROZEN)

Simon Hausmann hausmann at kde.org
Tue Oct 9 08:13:17 BST 2007


On Sunday 07 October 2007 23:24:54 David Faure wrote:
> On Saturday 06 October 2007, Alex Merry wrote:
> > On Saturday 06 Oct 2007, Allen Winter wrote:
> > > PS.  KSSL and printing stuff still needs work.  We can still accept
> > > code that improves those areas at any time. :)
> >
> > Hopefully the last API bit for printing, bar removing libkdeprint:
> >
> > Is this patch OK to commit?  It doesn't do anything interesting at the
> > moment, but provides the API for getting a customised QPrintDialog.
> >
> > The methods return a QAbstractPrintDialog *, but in actual fact it's a
> > QPrintDialog *.  Does this cause problems for deleting (the caller
> > takes ownership)?
>
> No, it doesn't cause problems, since the destructor is virtual in all
> QObjects [as it should be in any class with virtual methods, anyway].

I still suggest to return a QPrintDialog instead of a QAbstractPrintDialog. 
The latter is a useless class, it does not provide any abstraction. I don't 
recommend its use in the public API.


Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071009/86ed2778/attachment.sig>


More information about the kde-core-devel mailing list