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

List:       kde-devel
Subject:    Re: long hair developers :) ... and printdialog
From:       Stephan Heigl <stephan () heigl-gmbh ! de>
Date:       2000-03-21 19:43:13
[Download RAW message or body]

Am Tue, 21 Mar 2000 schrieb Gavriel State:
>>.....
> Our libAPS (Application Printing Services) is designed to work with 
> both CUPS and standard lpr/lprng.  It abstracts the back-end printing
> system from the app (be it a printer admin app, like KUPS, or an 
> application level print dialog).  Right now, interfacing with CUPS is
> done via the lpr transport, but we have a partially completed CUPS
> transport that could be further extended to provide CUPS specific 
> functionality.  
> 
> We've already done a ton of work on the admin/setup app side that's being
> released in Corel Linux 1.1 in a few days.  Of course, that work is 
> still KDE 1.1 based, and will have to be ported to  KDE 2.0.  
> 
> We're also using libAPS in WINE to implement the Windows print spooling 
> APIs, print dialogs, etc.
> 
> -Gav
> 
> -- 
> Gavriel State
> Engineering Architect - Linux Development
> Corel Corp
> gavriels@corel.com
> -- 
>....

Hi,

have also done a printdialog for corel linux? I used libAPS first in my
printdialog, but now switched to cups native.... if cups transport is finished
i go on with libAPS again.......

Another thing....
QPrinter first opens a QPrintDialog let the user select the options and then
renders the stuff and sends it to lpr.
What about changing this so that QPrintDialog creates a temporary ps file and
then load that file with a printdialog (perhaps with an "extern" printdialog
plugin .. which i favour....)?
I havenīt got much knowledge about QT2.1īs license.....may i copy code from
qprinter_x11.cpp and create an new QPrinter::cmd method?

regards

stephan

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