KPE Print and LPRng

[Till Kamppeter]

I forward this to the LPRng mailing list as a suggestion to the LPRng 
developers and contributers.

    Till

Goffioul Michael wrote:
> IMHO, what's really missing in LPRng to build a decent support
> in KDEPrint is an API and a library. Any command/operation has
> to be made by executing a program and parsing its output, so this
> heavily relies on a specific syntax. This is a pain from the
> client programmer point of view. That's why CUPS support is much
> more developed in KDEPrint: it provides a full API.
> Another problem with LPRng is the *wide* variety of driver
> systems existing out there, each one using its own files, setup,
> DB syntax or whatever. Again here, CUPS is more easy to use:
> you can request the server for the driver file, and it's always
> a PPD file. Presenting print options is then quite easy.
> LPRng is probably a wonderful print spooler for the command-line,
> but it's really difficult to build a modern GUI on top of it.
> The first thing I would expect from LPRng is an API.
> 
> Michael.
> 
> 
>>-----Original Message-----
>>From: Patrick Powell [mailto:papowell at astart.com]
>>Sent: Saturday, November 22, 2003 04:45
>>To: Till Kamppeter
>>Cc: For users and developers of KDEPrint, the KDE printing 
>>architecture
>>Subject: Re: HELP WANTED: kdeprint with GNUlpr
>>
>>I actually did some work on this a while ago.
>>
>>-- 
>>Patrick Powell                 Astart Technologies
>>papowell at astart.com            6741 Convoy Court
>>Network and System             San Diego, CA 92111
>>  Consulting                   858-874-6543 FAX 858-751-2435
>>LPRng - Print Spooler (http://www.lprng.com)
> 
> _______________________________________________
> kde-print mailing list
> kde-print at kde.org
> https://mail.kde.org/mailman/listinfo/kde-print
> 
>