KDEPrint code cleanup

Michael Goffioul goffioul at imec.be
Fri Aug 1 10:47:05 BST 2003

> In KBarcode I use the header kdepint/kmmanager.h and the classes KMManager and 
> KMPrinter. As the header was installed as default, I thought it was part of 
> the public API and I could use it. If you rename KMManager this would break 
> KBarcode. So I object therefore. 
> Both above mentioned classes are needed in KBarcode so that the user can 
> specify a printer name as commandline option and KBarcode can print to it. 
> Maybe this can also be done without using this classes, but I have no idea how 
> to do it.

Indeed, those classes are not intended to be used outside KDEPrint.
They have been installed for the only purpose to split KDEPrint's
code into pieces (in kdelibs and kdebase). That's why they are not
documented as KPrinter and KPrintDialog are.

Just a dumb question then: why don't you use the regular mechanism
for printer selection using the print dialog?


Michael Goffioul		IMEC-DESICS-MIRA
e-mail: goffioul at imec.be	(Mixed-Signal and RF Applications)
Tel:    +32/16/28-8510		Kapeldreef, 75
Fax:    +32/16/28-1515		3001 HEVERLEE, BELGIUM
This e-mail and/or its attachments may contain confidential
information.  It is intended solely for the intended addressee(s).
Any use of the information contained herein by other persons is
prohibited.  IMEC vzw does not accept any liability for the contents
of this e-mail and/or its attachments.

More information about the kde-core-devel mailing list