KDE4 printing: results of IRC meeting

[Kevin Krammer]

On Saturday 15 September 2007, Kurt Pfeifle wrote:

>  Disadvantages:
>   - the PDF generating backend needs to run as root in order to be
>     able to write resulting files into a user-private directory

It could just use a little suid helper.
However, if such a CUPS option would be available, I would expect it to 
transfer the generated data via socket/IPP to the client.
This would even make it work with a remote CUPS server.

>   - needs CUPS in the first place, needs a *working* CUPS, and
>     needs cupsd running

Given the rise of Unix on the desktop (including proprietary like Mac OS X), 
it IMHO makes perfect sense to delegete jobs to shared infrastructure instead 
of providing it ourselves.
There are enough places where this shared infrastructure does either not 
exists yet or is not good enough for our needs so we have to do it ourselves.

> I have to add now to the disadvantage side:
>   - doesn't work with KDE KIO

If the file is available to the client which requested it, it can always do 
the KIO transfer after the "printing".
AFAIK no difference to the KDE3 PDF creation chain, or does it output to the 
KIO location directly?

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- 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/20070915/27b86404/attachment.sig>